Preparing Servers for MS Exchange Hosting

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 MSXML4 from http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en on Server 2.

3. Install IIS (WWW, FTP, SMTP, NNNT) 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 SP4 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.5 media from https://members.microsoft.com/serviceproviders/webhosting/hostedmessaging/default.mspx (documenation at https://members.microsoft.com/serviceproviders/webhosting/hostedmessagingdocs/main.aspx)

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 (first configure a Server2 to use of new DNS on server1).

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 Service Provisioning\DeploymentTool

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

      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 the 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.

   8. Restart winbox after MPS (Microsoft Provisioning Service) deployment tool has been installed.

3. Create an MPS SQL Service Account for MPS Interaction with SQL-based Servers

   Procedure DWSPV.11: To create a SQL service account on the domain controller

   1. Log on to \\Server1 using an account that is a member of the domain administrators group.

   2. On the taskbar, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.

   3. Expand fabrikam.com (domain).

   4. Right-click Users, point to New, and then click User.

   5. In the New Object-User dialog box, type MPSSQLService as the First name and the User logon name, and then click Next.

   6. In the next New Object - User dialog box, clear the User must change password at next logon check box. Enter the password (twice), and then select Password never expires.

   7. Click Next. Verify the information you have entered, and then click Finish.

4. Add MPSSQLService to the Local Administrators Group

   Procedure DWSPV.12: To add MPSSQLService to the local administrators group

   1. Log on to \\Server2 as a member of the domain administrators group.

   2. On the taskbar, click Start, point to All Programs, then to Administrative Tools, and then click Computer Management.

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

   4. Double-click Administrators.

   5. Click Add, and then type MPSSQLService. Click Check Names to make sure that the name resolves, and then click OK.

   6. Click OK to close the Administrator Properties window.

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

   Procedure DWSPV.20: To deploy the Core Platform

   1. Log on to \\server2 as a member of the enterprise administrators group. Set your screen resolution to 1024 x 768 to properly display the Provisioning Deployment Tool interface when you start it.

   2. On the \\server2 desktop, double-click the shortcut to the MPS Deployment Tool.

   3. Click the Servers tab, and then, under SQL Servers, click Add.

   4. In the Add SQL Server dialog box, type <Server 2 name>, and then click OK.

   5. Under MPS Servers, click Add.

   6. In the Add Server dialog box, type the name of the MPF Engine server as <Server 2 name>, and then click OK.

   7. In the Requirements Status pane, expand Core Platform, expand Initialize Active Directory, right-click Native Mode, and then select Confirm irreversible Native Mode conversion. In the Active Directory /Native Mode dialog box, click OK. Right-click Native Mode and then select Install.

   8. Under the Initialize Active Directory component, right-click List Object Mode, and then select Install.

   9. In the Requirements Status pane, expand Core MPF Install, right-click the MPF Engine component, select Install on Server, and then click <Server 2 name>. The icon next to the MPF Engine component changes to a silver disk to indicate that you have scheduled the installation of this component.

   10. In the Requirements Status pane,under Core MPF Install, expand MPF Config Database. Right-click SQL not assigned, select Install on SQL Instance, and then click <Server 2 name>.

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

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

   12. In the Requirements Status pane, under Core MPF Install, right-click the MPF Audit and Recovery component, point to Install on Server, and then click Add New Server.

   13. Right-click the MPF Audit and Recovery component, point to Install on Server, and then click Add New Server.

   14. In the Requirements Status pane, right-click Core Platform, and select Install all in this group.

   15. If prompted with the Confirm Install on Dependents dialog box, review the list of actions to be performed, and click OK.

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

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

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

   19. Close the Provisioning Deployment Tool.

6. Install the Plans Database

   Procedure DWSPV.21: To deploy the Hosting Platform

   1. In the MPS Deployment Tool, in the Requirements Status pane, expand Hosting Platform, expand Hosted PlansDatabase, then expand Plans Database.

   2. Right-click Server not assigned, click Install on Server, then click <Server 2 name>.

   3. Under Plans Database, right-click <Server 2 name> and click Select SQL instance.

   4. In the Select SQL Server dialog box, type <Server 2 name> and then click OK.

   5. In the Requirements Status pane, below Hosting Platform, expand Initialize Default Services.

   6. Right-click Initialize Active Directory for Hosting, then select Set procedure parameters.

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

   8. In the Requirements Status pane, right-click Hosting Platform, and select Install all in this group.

   9. Click Start Deployment to start the installation of the Plans Database and Hosting Platform Service Components.

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

7. 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. Under Business Web Service-><Server 2 name>, right-click on 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.

   4. Click Start Deployment.

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

8. Install Resource Manager Web Client on Server 2

   1. Run the MPS Deployment Tool.

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

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

   4. Click Start Deployment.

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

9. Initialize Hosted Exchange Provisioning Namespaces

   1. Run the MPS Deployment Tool.

   2. In the Requirements Status pane, expand Hosted Exchange.

   3. Expand Exchange Platform.

   4. Right-click Hosted Exchange Namespace, and then click Execute. Initialize Hosted Exchange Namespace. Make sure to check if Exchange organization is being set correctly.

   5. Click Start Deployment.

10. 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.

    5. Initialize Hosted Exchange Provisioning Platform.

    6. In this procedure you will initialize your environment for Hosted Exchange provisioning.

11. Configure the Microsoft Provisioning System Server for Hosted Exchange

    Procedure DP.3: To initialize Hosted Exchange provisioning namespaces

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

    2. Run the MPS Deployment Tool.

    3. Expand Hosted Exchange.

    4. Expand Exchange Platform.

    5. Right-click Native Mode, and then click "Confirm irreversible Native Mode conversion".

    6. At the Microsoft Exchange/Native Mode dialog box, click OK.

    7. Right-click Exchange Platform, and then select Install all in this group.

    8. Click Start Deployment.

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

12. 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.

13. 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.

14. Add the MPSExchangeAccts Group to Local Administrators Group

15. Create Mailbox Stores for Hosted Exchange (only fro enterprise 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.

16. Initialize Resource Management

    1. Restat IIS on server2

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

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

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

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

    6. Add Business Mailstore resources.

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

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

    8. Under Publicstores, click Add New Resource.

    9. Add Public Store resources (Server  and Public Store names you can find in Exchange System Manager).

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

    11. Under OAB Servers, click Add New Resource.

    12. Add OAB Server resources.

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

18. 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"/>
        example test.ts.com Value="DC=test,DC=ts,DC=com"

19. 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.