Export (0) Print
Expand All

How to Install the Active Clustered Mailbox Role in a CCR Environment on Windows Server 2008

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1

Topic Last Modified: 2007-10-31

This topic explains how to install a Microsoft Exchange Server 2007 Service Pack 1 (SP1) clustered mailbox server (CMS) on the active node in a cluster continuous replication (CCR) environment that is running on the Windows Server 2008 operating system. For detailed steps about how to install CCR on Windows Server 2003, see Installing Cluster Continuous Replication on Windows Server 2003.

You can install the Mailbox server role on Windows Server 2008 and create a CMS using the command-line version of Setup (Setup.com) or by using the Exchange Server 2007 SP1 Setup wizard (Setup.exe).

Prior to performing this procedure, a Windows Server 2008 failover cluster must be formed and configured correctly. For detailed steps about how to create and configure a failover cluster for CCR on Windows Server 2008, see How to Create a Windows Server 2008 Failover Cluster for Cluster Continuous Replication.

In the Readiness Check phase of Setup, if you do not specify an alternate path for the default first storage group and database, and you intend to use the default path of %ProgramFiles%\Microsoft\Exchange Server\Mailbox, a warning may appear in the results list that states this path must be created. This warning can be safely ignored, because Setup will create the default path automatically. However, if you are not using the default path, the path you are using must be created before you run Setup.

To perform this procedure, the account you use must be delegated the Exchange Server Administrator role. For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

If you accidentally specify the cluster IP address as the IP address for the CMS, or if you accidentally specify the cluster name as the name for the CMS, you can complete the installation by performing Step 2 of the first procedure with the correct IP address and name.

Consider the following prior to performing the command-line (Setup.com) procedure that follows:

  • To select a non-default location for the first storage group, you can add /CMSDataPath:<PathToTheDatabase> to the command. The /CMSDataPath:<PathToTheDatabase> parameter can be omitted if you want the database to be located at the default location (%ProgramFiles%\Microsoft\Exchange Server\Mailbox). The string "First Storage Group" will be appended to the provided path. If you specify an alternate path, you must manually create the path before installing Exchange.

  • The command-line procedure uses the /CMSIPAddress option to specify a static Internet Protocol version 4 (IPv4) address. In a single subnet installation, you can use the following options to configure a Dynamic Host Configuration Protocol (DHCP) IPv4 address or an IPv6 address for the CMS:

    /CMSIPV4Networks:<PublicClusterNetworkName>
    /CMSIPV6Networks:<PublicClusterNetworkName>
    

    In a multiple subnet environment, /CMSIPV4Addresses can be used to configure the CMS, /CMSIPV4Networks can be used to configure the CMS with a dynamically assigned IPv4 address on the public cluster network, and /CMSIPV6Networks can be used to configure the CMS with a dynamically assigned IPv6 address on the public cluster network.

  1. Ensure that the Windows Firewall service is running. Windows Firewall does not need to be enabled, but the Windows Firewall service must be running.

  2. Open a Command Prompt window, navigate to the installation files, and then run the following command:

    Setup.com /roles:Mailbox /newcms /CMSname:<NameofClusteredMailboxServer> /CMSIPAddress:<ClusteredMailboxServerIPAddress>
    
    noteNote:
    If you need to place the program files in an alternate location, you can add /targetdir:<Path> to the command to specify the location. If you specify a path, it must match the path used by the passive node.
    noteNote:
    CMS names must be 15 characters or less.
    noteNote:
    If the Passive Clustered Mailbox role has already been installed, you can use the following command to make the passive node an active node, provided that an active node does not already exist in the cluster:
    Setup.com /newcms /cmsname:<NameofClusteredMailboxServer> /cmsipaddress:<IPAddressofClusteredMailboxServer>
    
  3. After Setup has completed successfully, a message appears indicating that a restart is required. Before you restart the node, stop the CMS. To stop the CMS, open the Exchange Management Shell from the Start menu (in the Microsoft Exchange Server 2007 program group) and run the following command:

    Stop-ClusteredMailboxServer <CMSName> -StopReason Setup -Confirm:$false
    
  4. After the CMS is stopped (offline), close the Exchange Management Shell and restart the node. During the restart, the CMS and any other cluster groups owned by the node being restarted is moved to another node in the cluster, if one is available, including a node that does not have Exchange installed. If the CMS group is moved to another node, it should be moved back to the active node after the restart. If the node that took ownership of the CMS during the restart has the same version of Exchange installed, you can use the following command in the Exchange Management Shell to move the CMS back to the node that was restarted.

    Move-ClusteredMailboxServer <CMSName> -TargetMachine <NodeName> -MoveComment Setup -Confirm:$false
    

    If the node that took ownership of the CMS during the restart does not have the same version of Exchange installed (or Exchange is not installed at all), you must use the cluster management tools (the Failover Cluster Management tool or Cluster.exe) to move the CMS group back to the node that was restarted. You can use the following command to do this:

    Cluster group <CMSName> /move:<NodeName>
    
  5. After the CMS is moved back to the active node, use the Exchange management tools on that node to start the CMS. You can run the following command in the Exchange Management Shell on the active node to start the CMS:

    Start-ClusteredMailboxServer <CMSName>
    

    You can also use the Manage Clustered Mailbox Server wizard in the Exchange Management Console to start the CMS. For detailed steps about how to start a CMS, see How to Start a Clustered Mailbox Server in a CCR Environment.

    After the CMS is started and all resources are online, the passive Mailbox server role can be installed on the second node in the failover cluster, if it is not already installed. For detailed steps about how to install the passive Mailbox server role in the failover cluster, see How to Install the Passive Clustered Mailbox Role in a CCR Environment on Windows Server 2008.

  1. Open Windows Explorer, navigate to the Exchange installation files, and then run the following command:

    Setup.exe
    
    noteNote:
    If you installed the necessary prerequisite packages, you can click Step 4: Install Microsoft Exchange Server 2007 SP1 to proceed with the installation.
  2. On the Introduction page, review the information, and then click Next.

  3. On the License Agreement page, review the license agreement. If you accept the terms, select I accept the terms in the license agreement, and then click Next.

  4. On the Error Reporting page, review the information, make your selection, and then click Next.

  5. On the Installation Type page, select Custom Exchange Server Installation. Optionally, change the location for the Exchange program files. If you specify a path, it must match the path used by the passive node. Click Next.

  6. On the Server Role Selection page, select Active Clustered Mailbox Role. This automatically selects the Management Tools role, and the other roles are unavailable. Optionally, change the location for the Exchange program files. If you specify a path, it must match the path used by the passive node. Click Next.

  7. On the Cluster Settings page, select Cluster Continuous Replication, and then enter the CMS name in the Clustered Mailbox Server Name field. Optionally, change the initial location for the CMS storage group and database files, and then click Next.

    noteNote:
    CMS names must be 15 characters or less.
  8. On the Cluster IP Address Configuration page, select from the following options under First Subnet:

    • IPv4 Network   Select this option if all public network interfaces in the cluster use IPv4 addresses. After you select this option, you must select a static IPv4 address or use DHCP:

      If you want to use a static IPv4 address for the CMS, select Use the following static IPv4 address, and enter the IP address in dotted decimal format in the field.

      If you want to use a dynamically assigned IP address for the CMS, select Use a dynamically assigned (DHCP) IPv4 address for the following network. Then, click the Browse button to select the public cluster network.

    • IPv6 Network   Select this option if all public network interfaces in the cluster also use IPv6 addresses. Then, click the Browse button to select the public cluster network.

  9. If you are installing CCR in a multiple subnet environment, select the Second Subnet check box, and then configure the network settings for the second subnet. If you are not installing CCR in a multiple subnet environment, leave the Second Subnet check box cleared.

  10. Click Next to initiate the checks and installation. On the Readiness Checks page, the status appears as the checks are performed. When the checks complete successfully, click Install. If any of the checks fail with errors, you must correct the issues that are identified, and then you can restart the installation.

  11. The Progress page shows the steps that Setup performs. When all steps have completed, clear the Finalize installation using the Exchange Management Console check box, and then click Finish.

  12. A message appears indicating a restart is required prior to placing the server in production. Click OK to acknowledge this message.

  13. After installation and configuration are complete, you are returned to the initial Setup page to download Exchange updates and complete the setup on this node. Optionally, click Step 5: Get Critical Updates for Microsoft Exchange to download any available updates. If you install updates and those updates require a restart, do not restart the node. Instead, continue this procedure.

  14. Click Close to exit Setup.exe, and if a prompt appears, click Yes to confirm.

  15. After Setup has completed, but before the node is restarted, stop the CMS. To stop the CMS, open the Exchange Management Shell from the Start menu (in the Microsoft Exchange Server 2007 program group) and run the following command:

    Stop-ClusteredMailboxServer <CMSName> -StopReason Setup -Confirm:$false
    
  16. After the CMS is stopped (offline), close the Exchange Management Shell and restart the node. During the restart, the CMS, and any other cluster groups owned by the node being restarted are moved to another node in the cluster, if one is available, including a node that does not have Exchange installed. If the CMS group is moved to another node, it should be moved back to the active node after the restart. If the node that took ownership of the CMS during the restart has the same version of Exchange installed, you can use the following command in the Exchange Management Shell to move the CMS back to the node that was restarted.

    Move-ClusteredMailboxServer <CMSName> -TargetMachine <NodeName> -MoveComment Setup -Confirm:$false
    

    If the node that took ownership of the CMS during the restart does not have the same version of Exchange installed (or Exchange is not installed at all), you must use the cluster management tools (the Failover Cluster Management tool or Cluster.exe) to move the CMS group back to the node that was restarted. You can use the following command to do this:

    Cluster group <CMSName> /move:<NodeName>
    
  17. After the CMS is moved back to the active node, use the Exchange management tools on that node to start the CMS. You can run the following command in the Exchange Management Shell on the active node to start the CMS:

    Start-ClusteredMailboxServer <CMSName>
    

    You can also use the Manage Clustered Mailbox Server wizard in the Exchange Management Console to start the CMS. For detailed steps about how to start a CMS, see How to Start a Clustered Mailbox Server in a CCR Environment.

    After the CMS is started and all resources are online, the passive Mailbox role can be installed on the second node in the failover cluster, if it is not already installed. For detailed steps about how to install the passive Mailbox role in the failover cluster, see How to Install the Passive Clustered Mailbox Role in a CCR Environment on Windows Server 2008.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft