Sharepoint Iis Moss Wss

Introduction

In a corporate environment, managing access to internal web applications effectively is crucial. For many, using Microsoft Internet Information Services (IIS) for hosting applications like SharePoint is common. But what happens when you want to provide access via an alternative hostname without enforcing an SSL connection? This is a common challenge faced by SharePoint administrators.

In this blog post, we’ll discuss how to set up an alternative hostname for your IIS web site that is intended for internal access only, using Windows 2003 Server. We will guide you through the steps necessary to configure this setup appropriately through SharePoint Central Administration.

Understanding the Problem

You have a SharePoint intranet, which is already set up to handle external requests using the host header portal.mycompany.com with an enforced SSL requirement. However, your team needs an internal access option using a different hostname, such as http://internalportal/, that does not require SSL.

While IIS does allow for various configurations, the integration with SharePoint needs to be handled correctly to ensure smooth functioning. Let’s break down how to achieve this:

Solution Overview

Extending the Existing Application

  1. Access SharePoint Central Administration:

    • Open your SharePoint Central Administration interface. This is the primary portal for managing SharePoint settings and configurations.

  2. Create or Extend a Web Application:

    • In the Central Administration dashboard, look for the option related to managing web applications. You will find options to create a new web application or extend an existing one.

  3. Choose Extend an Existing Application:

    • Here, you’re going to select the option to extend an existing application. This will allow you to replicate your existing SharePoint web application settings under a new hostname.

Configuring the New IIS Website

  1. Specify the New Host Header:

    • During the extension process, you will be prompted to specify a new host header for the web application. Input internalportal or any internal URL that your team will use.

  2. Set Authentication Mechanisms:

    • Since this internal site does not need to enforce SSL, you can select the appropriate authentication method that aligns with your organization’s security policies.

  3. Finalize the Setup:

    • Complete the setup by confirming the settings. SharePoint will handle the necessary configurations in IIS for you, making sure everything is compatible.

Important Considerations

  • Always Prefer SharePoint:

    • A significant takeaway here is that if SharePoint offers a way to configure a feature, it is best to use that method instead of making changes directly in IIS. This ensures better compatibility and support from Microsoft.

  • Testing:

    • After setting up the alternative hostname, it’s crucial to perform thorough testing to ensure that the internal portal is accessible as expected, without SSL and functionality as required.

Conclusion

Setting up an alternative hostname for internal access to your SharePoint intranet using IIS is a practical solution for organizations looking to streamline internal communication without unnecessary restrictions like SSL. By utilizing SharePoint Central Administration, you can manage this configuration effectively and ensure it integrates well with your existing setup. If you follow these steps carefully, you will have a robust internal portal that meets your team’s needs.

For more related tutorials and tips, stay tuned to our blog. If you have additional questions or need further assistance, feel free to leave a comment below!