Preparing Servers for MS Exchange Hosting

Last modified: 27 Dec 2007

This document is a rough version of MS Exchange hosting documentation. For all questions and feedback, please contact us.

Before you start using MS Exchange hosting, you need to prepare at least 2 servers, separately of H-Sphere, with the following software installed:

1. Server 1 (Primary Domain Controller): Windows 2003 SP1, Active Directory Domain Controller
2. Server 2 (MS Exchange Server): Windows 2003 SP1, MSSQL 2000 SP3, MS Exchange 2003 SP1, Hosted Messaging and Collaboration 3.0, WS Exchange Provider Adapter Namespace

To prepare Servers for MS Exchange Hosting:

1. Install Required Software On The Servers
2. Deploy Hosted Messaging and Collaboration
3. Install WS Exchange Provider Adapter Namespace
4. Create Reseller Organization Unit

1. Install Required Software On The Servers

1. Install Window 2003 SP1 on both servers with English language interface.

2. Install MDAC 2.8 on Server 2.

3. Install IIS and ASP.NET on Server 2:

   1. On the taskbar, click Start, click Control Panel, select Add or Remove Programs, and then click Add/Remove Windows Components.

   2. Select Application Server, and then click Details.

   3. Select Internet Information Services (IIS), and then click Details.

   4. Install the following components: Internet Information Services Manager, World Wide Web Services, Common Files, ASP.NET

   5. Click OK, click OK again, and then click Next.

   6. After the wizard completes, click Finish and close the Add or Remove Programs dialog box.

4. Install MSSQL Server 2000 on Server 2.

5. Install MSSQL Server 2000 SP3 on Server 2.

6. Enable Network DTC and COM+ Network Access

   1. On the taskbar, click Start, open Control Panel, and then click Add or Remove Programs.

   2. Click the Add/Remove Windows Components button.

   3. Highlight Application Server, and then click Details.

   4. Select EnableNetwork COM+ access.

   5. Select EnableNetwork DTC access. Click OK.

   6. Click Next. When the Windows Components Wizard completes, click Finish.

7. Enable Inbound and Outbound DTC Access on Server 2

   1. Click Start, point to All Programs, point to Administrative Tools, and then click Component Services.

   2. Click and expand Component Services, and then click and expand Computers.

   3. Right-click My Computer, and then select Properties.

   4. Select the MSDTC Tab.

   5. Click the Security Configuration button.

   6. Ensure that Network DTC Access is enabled. Then, ensure that the Allow Inbound and Allow Outbound options are selected in the Transaction Manager Communication section. Leave all other options as default.

   7. Click OK to save the settings. Select Yes if you are prompted to restart the service.

8. Obtain Hosted Messaging and Collaboration 3.0 media from Microsoft website

9. Install Active Directory Domain Controller on Server 1 using the dcpromo.exe tool in Windows root directory.

10. Join Server 2 to installed domain.

11. Log on to Server 2 as a member of the Domain Administrators group.

12. Install MS Exchange server 2003 on Server 2.

13. Install MS Exchange server 2003 SP1 on Server 2.

2. Deploy Hosted Messaging and Collaboration

1. Log on to Server 2 as a member of the Domain Administrators group.

2. Install the MPS (Microsoft Provisioning Service) deployment tool.

   1. Quit all running programs.

   2. Open command prompt, and change the directory to SolutionMedia\Service Provisioning\Deployment Tool.

   3. To install the Deployment Tool on Server 2, run the following from the command prompt: cscript initdeploymenttool.wsf.

      Note: If you are not installing from CD, you will be prompted to enter a path to the root directory of the solution media source files.

   4. When prompted for the server name for configuration files, enter \\<Server 2 name>, and then click OK.

   5. When prompted for the server name for installation files, enter \\<Server 2 name>, and then click OK.

   6. In the confirm configuration dialog box, click Yes if the settings are correct, or click No to cancel.

   7. In Do you want to install the deployment tool to the local computer? dialog box, click Yes. A shortcut for the Deployment Tool will be added to the desktop of Server 2.

3. Install the MPF (Microsoft Provisioning Framework) Engine and Database

   1. Run the MPS Deployment Tool, and then click the Servers tab.

   2. Under SQL Servers, click Add.

   3. Enter <Server 2 name>,and then click OK.

   4. Under MPS Servers, click Add.

   5. Enter the name of the MPF Engine server as <Server 2 name>, and then click OK.

   6. In the Requirements Status pane, expand the Active Directory component, right-click Native Mode, and then select User input on the contextual menu that appears. In the Active Directory Native Mode dialog box, click OK.

   7. Under the Active Directory component, right-click List Object Mode, and then select User Input on the contextual menu that appears. The Active Directory/list Object Mode dialog box appears and prompts you as to whether or not you want to proceed. Click OK.

   8. In the Requirements Status pane, right-click the MPF Engine component, select Install on Server, and then click <Server 2 name>.

   9. The icon next to the MPF Engine component changes to a silver disk to indicate that you have scheduled the installation of this component.

      Note: Because of inherent dependencies, when you configure the MPF Engine to be installed on Server 2, other core MPS components are also installed on Server 2, and the MPFServiceAcct is scheduled to be created in Active Directory.

   10. In the Requirements Status pane, right-click the MPF Config Database component, select Install on SQL Server, and then click <Server 2 name>.

   11. Repeat step 3.10 for each of the MPF database components:

       • Resource Manager Database
       • MPF Audit Database
       • MPF Transaction Database

   12. In the Requirements Status pane, right-click the Windows-based Hosting component, and then select Install this Group to install all the components. The Install This Group dialog box will display the list of items to be installed and actions to be performed. Click OK.

   13. Click Start Deployment to start the installation of the MPF Engine, databases, and namespaces/providers on the server.

   14. Monitor the deployment session on the Install Details tab.

   15. When the deployment is complete, on the Action History tab, click View Details to review events.

   16. Close the Provisioning Deployment Tool.

       Note: When deployment completes, you will see that the following Namespace Initialization procedures are displayed with a red X, and the Install Details pane displays an unable to create the credential error.

       Managed Helpers:InitializeNamespaceSecurity

       Managed Web Hosting:InitializeNamespaceSecurity

       Managed Sharepoint Hosting:InitializeNamespaceSecurity

       This is an expected error.

4. Verify the MPFClientAccts Group on Server 2

   1. Click Start, point to AllPrograms, point to AdministrativeTools, and then click Computer Management.

   2. Expand Local Users and Groups, and then click Groups.

   3. Double-click Distributed COM Users, and then click the Members tab.

   4. Verify that the <domain name>\MPFClientAccts group is member of Distributed COM Users group. Click OK.

   5. Click OK to close the Distributed COM Users Properties dialog box.

5. Add MPFServiceAccts to the Local Administrators Group

   1. On the taskbar, click Start, click All Programs, click Administrative Tools, and then click Computer Management.

   2. Expand Local Users and Groups, and then click Groups.

   3. Double-click the Administrators group.

   4. Click Add, and then enter MPFServiceAccts. Select the Check Names check box to make sure that the name resolves, and then click OK.

   5. Click OK to close the Administrator Properties window.

6. Reboot Server 2

7. Initialize Namespaces

   1. Run the MPS Deployment Tool.

   2. In the Requirements Status pane, expand the Namespace Initialization component. Right-click Managed Helpers:InitializeADforHosting, and then select User Input.

   3. When prompted for the name of the hosting organization, accept the default of Hosting, and then click OK.

   4. Right-click Managed Helpers:InitializeADforHosting, and then select Execute Initialization Procedure.

   5. In the Confirm Operation dialog box, click Yes.

   6. Right-click Managed Helpers:InitializeNamespaceSecurity, and then select Execute Initialization Procedure.

   7. In the Confirm Operation dialog box, click

   8. When the deployment completes, close the MPS Deployment Tool.

8. Install the Plans Database

   1. Run the MPS Deployment Tool.

   2. In the Requirements Status pane, right-click Plans Database, select Install on Server, and then select <Server 2 name>.

   3. Click Start Deployment.

   4. When deployment completes, close the MPS Deployment Tool.

   5. Run the MPS Deployment Tool.

   6. In the Requirements Status pane, expand Namespace Initialization.

   7. Right-click Managed Helpers: InitializePlanDatabase, and then select Execute Initialization Procedure.

   8. In the Confirm Operation dialog box, click Yes.

   9. When deployment completes, close the MPS Deployment Tool.

9. Install the MPS Web Services on Server 2

   1. Run the MPS Deployment Tool.

   2. In the Requirements Status pane, right-click Web Service, select Install on Server, and then select <Server 2 name>.

   3. Below Web Service, right-click <Server 2 name>, and then select User Input.

   4. In the New Virtual Directory box, enter MPSWS, and then click OK.

      Note: After you assign the Web service and input the virtual directory name, the MPF Client will automatically be assigned for installation on Server 2

   5. Click Start Deployment.

   6. When the deployment completes, click OK, and then quit the MPS Deployment Tool.

10. Install Resource Manager Web Client on Server 2

    1. Run the MPS Deployment Tool.

    2. In the Requirements Status pane, right-click Resource Manager Web Client, select Install on Server, and then select <Server 2 name>.

    3. Below Web Service, right-click <Server 2 name>, and then select User Input.

    4. In the New Virtual Directory box, enter ResourceManagerWebClient, and then click OK.

    5. Click Start Deployment.

    6. When the deployment completes, click OK, and then quit the MPS Deployment Tool.

11. Initialize Hosted Exchange Provisioning Namespaces

    1. Run the MPS Deployment Tool.

    2. Expand Namespace Initialization.

    3. Right-click Hosted Exchange: InitializeHostedExchange, and then select Execute Initialization Procedure. At the Confirm Operation dialog box, click Yes.

12. Configure the MPFServiceAccts Group As Exchange Full Administrator

    1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

    2. In the console tree, right-click the top node where the name of your Exchange organization is displayed, and then click Delegate control to start the wizard.

    3. Click Next, click Add, click Browse, select MPFServiceAccts from the list, and then click OK.

    4. On the drop-down menu, click Exchange Full Administrator, click OK, click Next, and then click Finish. If prompted with a security dialog box, click OK.

13. Configure the Microsoft Provisioning System Server for Hosted Exchange

    1. Run the MPS Provisioning Deployment Tool.

    2. Under Microsoft Exchange, right-click Delegate Exchange Administration, then select Force State. At the Force State dialog box, select the Verified radio button and click OK.

    3. Under Microsoft Exchange, right-click Disable Domain RUS, then select Install. The Confirm Operation dialog box appears and prompts you as to whether or not you want to proceed with an action that has an immediate effect. Click Yes.

    4. Under Microsoft Exchange, right-click Secure All Address Lists, then select Install. The Confirm Operation dialog box appears and prompts you as to whether or not you want to proceed with an action that has an immediate effect. Click Yes.

    5. Under Microsoft Exchange, right-click Native Mode, then select Install. The Confirm Operation dialog box appears and prompts you as to whether or not you want to proceed with an action that has an immediate effect. Click Yes.

       Check the log information at the bottom of the Configuration Wizard screen to verify that the configuration was successfully set.

14. Configure the MPSExchangeAccts Group As Exchange Full Administrator

    1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

    2. In the console tree, right-click the top node where the name of your Exchange organization is displayed, and then click Delegate control to start the wizard.

    3. Click Next, click Add, click Browse, select MPSExchangeAccts from the list, and then click OK.

    4. On the drop-down menu, click Exchange Full Administrator, click OK, click Next, and then click Finish. If prompted with a security dialog box, click OK.

15. Configure the All Address Lists Container

    1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

    2. In the console tree, click the Recipients node, expand the tree.

    3. Right-click the All Address Lists and select Properties.

    4. Click the Security tab, click Advanced, and then click Add under Permissions.

    5. In the Name text box, type MPSExchangeAccts, and then click OK.

    6. In the Apply onto list, select This object and subcontainers.

    7. In the Permissions list, click Full Control.

    8. Click OK three times.

16. Add the MPSExchangeAccts Group to Local Administrators Group

17. Create Mailbox Stores for Hosted Exchange

    1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

    2. In the console tree, expand Servers, then expand <Exchange Server>, and then expand First Storage Group.

    3. Create any appropriate mailbox stores will be used as a Business Mailstores.

18. Initialize Resource Management

    1. Launch Internet Explorer, and go to http://localhost/ResourceManagerWebClient/QueryResources.aspx.

    2. When prompted for Username and Password, log in as <domain name>\Administrator.

    3. Enter <Server 1 fullname> in the Preferred Domain Controller text box. Click Submit.

    4. In the left pane, click Exchange Resource Manager. Then, select the Business Mailstores tab.

    5. Add Business Mailstore resources.

       Important: The <shared> value should always be set to 1 for Business mail stores

    6. In the left pane, click Exchange Resource Manager. Then, select the Public Stores tab.

    7. Under Publicstores, click Add New Resource.

    8. Add Public Store resources

    9. In the left pane, click Exchange Resource Manager, and then, select the OAB Servers tab.

    10. Under OAB Servers, click Add New Resource.

    11. Add OAB Server resources.

19. Install the Hosted Exchange Offline Address Book (OAB) and Update Batch Application

20. Deploy the MPS Sample Web Client

    1. Run SetupMPSSampleWeb.msi from the Windows-based Hosting distribution media in the \Samples\Provisioning\MPSSampleWeb directory.

    2. On the MPPSSampleWeb Setup Wizard Welcome page, click Next.

    3. On the Select Installation Address page, accept the default Virtual Directory (MPSSampleWeb) and Port (80), and then click Next.

    4. On the Confirm Installation page, click Next.

    5. On the Installation Complete page, click Close.

    6. Open the Internet Information Services (IIS) Manager, and then expand the default Web site.

    7. Right-click MPSSampleWeb, and then select Properties.

    8. Click the Directory Security tab, and then, under Authentication and access control, click Edit.

    9. Clear the Enable anonymous access check box.

    10. Ensure that the Integrated Windows Authentication check box is cleared.

    11. Select the Basic authentication check box, and then, in the warning dialog box, click Yes.

    12. Enter a backslash “\” in the default domain field.

    13. Click OK, and then click OK again.

    14. Close the IIS Manager window.

    15. Edit the Web.Config file in the root directory of the MPS Sample Web Client (usually \inetpub\wwwroot\MPSSampleWeb). Set the following preferredDC and DefaultNamingContext key values to your preferred domain controller and default naming context. For example:

        <appSettings>
        <add key="preferredDC" value="Server_1_full_name>"/>
        <add key="DefaultNamingContext" Value="DC=domain_name_part1,DC=domain_name_part2"/>

21. Disable the EventSink:
1. Go to C:\Program Files\Microsoft Hosting\Provisioning\MPSWS\ and open file web.config.
2. Find the <add key="EnableEventSink" value="1"/> string and change value to 0 (<add key="EnableEventSink" value="0"/>)
3. Save changes.

It will allow creating Exchange Recipient Policy for new SMTP domains.

3. Install WS Exchange Provider Adapter Namespace

WS Exchange Provider Adapter Namespace (WS stands for "Web service") provides communication between H-Sphere and MS Exchange provider via HTTP in order to manage MS Exchange hosting in H-Sphere CP.

1. Download WS Exchange Provider Adapter Namespace installation.
2. Run the downloaded MSI file and follow the installation instructions.

4. Create Reseller Organization Unit

Create reseller organization unit under which H-Sphere users signed up for MS Exhange plans will be hosted. On Server 2:

1. In Internet Explorer, go to http://localhost/MPSSampleWeb

2. When prompted, log on as Domain Administrator.

3. Leave the Current Reseller and Current Customer fields empty.

4. Select the General tab.

5. In the left-hand pane, click Create a Reseller Organization.

6. Enter information about the organization in the appropriate boxes on the Create Reseller Org page

7. Click Submit Request.

8. When the request completes, you can review the XML response at the bottom of the page.

After that, you can proceed to configuring Microsoft Provisioning Framework in admin CP.

That's how the organization unit may look like when it is created and used for H-Sphere hosting:

In the above screenshot, Organization1 is the reseller organization unit, and its organization units like exchange are H-Sphere user accounts with emails and distribution lists.