Export (0) Print
Expand All

How to Install the Active Clustered Mailbox Role in a Single Copy Cluster on Windows Server 2003

 

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

Topic Last Modified: 2009-03-05

This topic explains how to install the Mailbox server role and create a clustered Mailbox server (CMS) on the active node in a single copy cluster (SCC) running on Windows Server 2003. For detailed steps about how to install the Mailbox server role and create a CMS in an SCC environment on the active node in a failover cluster running on Windows Server 2008, see How to Install the Active Clustered Mailbox Role in a Single Copy Cluster on Windows Server 2008.

You can install the Mailbox server role and create a CMS by using the command-line version of Setup (Setup.com) or by using the Microsoft Exchange Server 2007 Service Pack 1 (SP1) Setup wizard (Setup.exe). This topic contains procedures for both interfaces.

noteNote:
The physical disk resources must be configured in their default cluster group, and they must not be moved to the Clustered Mailbox Server cluster group before Exchange Server 2007 is installed.
noteNote:
The default cluster groups may not exist if you have an existing installation of Exchange 2007. To install a new instance of Exchange 2007 in this scenario, move the storage group to a temporary group, and then move the temporary group to the node where Setup will run. After Exchange 2007 is installed, move the storage group to the new instance of the storage group, and then update the dependencies.

Prior to performing any of the following procedures, a Windows Server 2003 failover cluster must be formed and configured correctly. For detailed steps about how to create and configure a failover cluster for an SCC on Windows Server 2003, see How to Create a Windows Server 2008 Failover Cluster for a Single Copy Cluster. In addition, shared storage must be configured and present in the cluster. Also, the physical disk resource that will contain the default storage group and database must be owned by the node on which you are running Setup.

To perform the following procedures, the account you use must be delegated membership in 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.

importantImportant:
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 1 of the first procedure with the correct IP address and name.
noteNote:
CMS names must be 15 characters or less.

  1. Verify that the active node owns the disk group that contains the disk resource that will host the default storage group and database. To verify ownership of the disk resource group, open a Command Prompt window, and run the following command:

    Cluster group
    

    If the group containing the physical disk resource that will host the default storage group is not owned by the node on which you are performing this procedure, you must move the group to this node by running the following command:

    Cluster group "GroupName" /move:<NodeName>
    
  2. After you verify that the active node owns the physical disk resource that will host the default storage group and database, navigate to the folder containing the Exchange 2007 SP1 installation files, and run the following command.

    Setup.com /m:install /roles:mailbox /newcms /cmsname:<NameofClusteredMailboxServer> /cmsipaddress:<IPAddressofClusteredMailboxServer> /cmssharedstorage /cmsdatapath:<SharedStoragePathForDatabase>
    
    noteNote:
    The path you specify for /cmsdatapath must be created before you run Setup. 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 do specify a path, before you run Setup, the path must be created on a local drive and not shared storage, and it must match the path used by the passive node.
    noteNote:
    If the Passive Clustered Mailbox role has already been installed, you can use the following command to make a passive node an active node:
    Setup.com /newcms /cmsname:<NameofClusteredMailboxServer> /cmsipaddress:<IPAddressofClusteredMailboxServer> /cmssharedstorage
    
  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 the Command Prompt window, and then restart the node.

  5. During the restart, if a passive node exists in the cluster, all cluster groups move from the node being restarted to the passive node. After the node is restarted, the CMS group is moved back to the active node, but all other groups remain on the passive node and must be manually moved back to the active node before proceeding. In a newly formed Windows Server 2003 failover cluster, at least two groups are present. One is the default Cluster Group, and the other groups contain the physical disk resources that were detected during cluster formation. The additional groups are named Group X, where X is the group number. There is one group for each physical disk resource detected during cluster formation (for example, Group 0, Group 1, and so on). Move each group that contains a physical disk resource from the passive node to the active node by running the following command for each group.

    Cluster group "Group X" /move:<NodeName>
    
  6. Next, move the physical disk resources for the CMS from the default disk groups to the CMS group. You can move the disks from each additional group to the group containing the CMS, and then delete the empty groups by running the following commands for each disk resource and group:

    Cluster res "Disk X:" /move:CMSName
    Cluster group "Group X" /delete
    
  7. Next, configure the physical disk resource dependencies, by making the appropriate disk resource a dependency item for the Microsoft Exchange Database Instance resource by running the following command:

    Cluster res "First Storage Group/Mailbox Database (CMSName)" /AddDep:"Disk X:"
    

    Repeat this command for each additional disk that will be used by the storage group or database.

  8. After the physical disk resource dependencies are properly configured, the Affect the Group setting must be disabled for the disk resources used by the CMS by running the following command for each disk resource in the CMS group:

    Cluster res "Disk X:" /prop RestartAction=1
    

    Repeat this command for each additional disk that will be used by the storage group or database.

  9. After the Affect the Group setting is disabled for the disk resources, use the Exchange management tools to start the CMS by running the following command in the Exchange Management Shell on the active node:

    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 Single Copy Cluster.

    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 Single Copy Cluster on Windows Server 2003.

  1. Verify that the active node owns the disk group that contains the disk resource that will host the default storage group and database. To verify ownership of the disk resource group, open a Command Prompt window, and run the following command:

    Cluster group
    

    If the group containing the physical disk resource that will host the default storage group is not owned by the node on which you are performing this procedure, you must move the group to this node by running the following command:

    Cluster group "GroupName" /move:<NodeName>
    
  2. After you verify that the active node owns the physical disk resource that will host the default storage group and database, navigate to the folder containing the Exchange 2007 SP1 installation files, and 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.
  3. On the Introduction page, review the information, and then click Next.

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

  5. On the Error Reporting page, review the information and make your selection. Click Next.

  6. 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 be on a local drive and not shared storage, and it must match the installation path used on all passive nodes. Click Next.

  7. On the Server Role Selection page, select Active Clustered Mailbox Role. This will automatically select the Management Tools role, and the other roles will be unavailable. Optionally, change the location for the Exchange program files. If you specify a path, it must be on a local drive and not shared storage, and it must match the installation path used on all passive nodes. Click Next.

  8. On the Cluster Settings page, select Single Copy Cluster, and then enter the CMS name in the Clustered Mailbox Server Name field.

  9. Change the location for the CMS database files to a location on the shared storage by clicking Browse, and then selecting a location on a drive that is represented by a physical disk resource in the group containing the CMS. After the path for the CMS database files has been changed to a shared storage path, click Next.

    noteNote:
    The shared storage path you use must not be the root directory of a volume.
  10. On the Cluster IP Address Configuration page, enter a static Internet Protocol version 4 (IPv4) address, and then click Next.

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

  12. The Progress page shows the steps that will be performed. Progress is shown as each step is processed and completion status is provided as each step completes. When all steps complete successfully, clear the check box for Finalize installation using the Exchange Management Console, and then click Finish.

  13. After Setup has completed successfully, a message appears indicating that a restart is required. Click OK.

  14. After installation and configuration are complete, you are brought back to the initial Setup page to download Exchange updates and complete the setup. 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.

  15. 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
    
  16. After the CMS is stopped (offline), close the Exchange Management Shell and the Command Prompt window, and then restart the node.

  17. During the restart, if a passive node exists in the cluster, all cluster groups move from the node being restarted to the passive node. After the node is restarted, the CMS group is moved back to the active node, but all other groups remain on the passive node, and must be manually moved back to the active node before proceeding. In a newly formed Windows Server 2003 failover cluster, at least two groups are present. One group is the default Cluster Group, and the other groups contain the physical disk resources that are detected during cluster formation. The additional groups are named Group X, where X is the group number. There is one group for each physical disk resource detected during cluster formation (for example, Group 0, Group 1, and so on). Move each group that contains a physical disk resource from the passive node to the active node by running the following command for each group:

    Cluster group "Group X" /move:<NodeName>
    
  18. Next, move the physical disk resources for the CMS from the default disk groups to the CMS group. You can move the disks from each additional group to the group containing the CMS, and then delete the empty groups by running the following commands for each disk resource and group:

    Cluster res "Disk X:" /move:CMSName
    Cluster group "Group X" /delete
    
  19. Next, configure the physical disk resource dependencies, by making the appropriate disk resource a dependency item for the Microsoft Exchange Database Instance resource by running the following command:

    Cluster res "First Storage Group/Mailbox Database (CMSName)" /AddDep:"Disk X:"
    

    Repeat this command for each additional disk that will be used by the storage group or database.

  20. After the physical disk resource dependencies are properly configured, the Affect the Group setting must be disabled for the disk resources used by the CMS by running the following command for each disk resource in the CMS group:

    Cluster res "Disk X:" /prop RestartAction=1
    

    Repeat this command for each additional disk that will be used by the storage group or database.

  21. After the Affect the Group setting is disabled for the disk resources, use the Exchange management tools to start the CMS by running the following command in the Exchange Management Shell on the active node:

    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 Single Copy Cluster.

    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 Single Copy Cluster on Windows Server 2003.

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

Community Additions

ADD
Show:
© 2014 Microsoft