By having an installation guide, Contoso will be able to ensure standardization across the enterprise, reducing Total Cost of Ownership, and easing troubleshooting steps.

The scope of this document is limited to installation of an Exchange 2007 server in a CCR environment for Contoso on the Windows Server 2003 Enterprise x64 Edition operating system platform.

The operator should have working knowledge of Windows Server 2003 Enterprise x64 Edition concepts, Exchange Server 2007 concepts, the Exchange Management Console and Exchange Management Shell, the command line, and various system utilities. This document does not elaborate on the details of any system utility except as necessary to complete the tasks within.

This document assumes that Windows Server 2003 Enterprise x64 Edition is installed per company baseline regulations which include the latest approved service pack and hotfixes. The current service pack level is Windows Server 2003 Service Pack 2 for x64 Editions.

It is also assumed that the following are installed:

• Windows Server 2003 Service Pack 2 32-bit Support Tools are installed on the server as the tools are useful for troubleshooting.
  
  
• Windows Server 2003 Resource Kit Tools are installed on the server as the tools are useful for troubleshooting.
  
  

This document assumes that forest and domain preparation steps have been performed per How to Prepare Active Directory and Domains topic in the Exchange 2007 Online Help.

This document assumes that both Exchange 2007 and Windows Server 2003 will be secured following the best practices found in:

• Exchange Server 2007: Security and Protection
  
  
• Windows Server 2003: Windows Server 2003 Security Guide
  
  

  Important:
  The procedures within this document should be followed sequentially. If changes are made out of sequence, unexpected results may occur.

Review the Planning for Cluster Continuous Replication topic in the Exchange 2007 Online Help before implementing the cluster.

The cluster service account requires membership in the local Administrators security group, as well as the following user rights to function properly on both nodes in the cluster. The Cluster Configuration Wizard grants the following permissions automatically:

• Act as part of the operating system
  
  
• Adjust memory quotas for a process
  
  
• Back up files and directories
  
  
• Increase scheduling priority
  
  
• Log on as a service
  
  
• Restore files and directories
  
  

If group policies are deployed against the nodes in the cluster, then verify that the cluster service account rights will not be overwritten, or modify the group policy so that the cluster service account has the above rights.

Note:
For more information, see the following Microsoft Knowledge Base article How to manually re-create the Cluster service account.

Since clustered mailbox servers in a CCR environment replicate data asynchronously, there is data loss during a lossy failover. To help mitigate this, the Hub Transport server role has a feature that temporarily retains mail that was recently delivered to a CCR server. This feature is known as the transport dumpster. In the event of a lossy failover, the transport dumpster is used by clustered mailbox servers in a CCR environment to re-deliver mail to each storage group for a specific timeframe (the timeframe is based on the last log inspected and last log generated) in the event of a lossy failover. The transport dumpster is for clustered mailbox servers in a CCR environment only.

The transport dumpster is an organizational setting and thus should be configured appropriately to handle all clustered mailbox servers in a CCR environment within the organization. In addition, it should be noted that the transport dumpster is configured per storage group and per clustered mailbox server within an Active Directory site.

The transport dumpster is enabled by default to support environments that deploy CCR and has the following settings:

• MaxDumpsterSizePerStorageGroup – 18 MB
  
  
• MaxDumpsterTime – 7 days
  
  

We recommend that you configure the MaxDumpsterSizePerStorageGroup parameter, which specifies the maximum size of the transport dumpster queue for each storage group, to a size that is 1.5 times the size of the maximum message that can be sent. For organizations that do not utilize a maximum message size, the formula should be 1.5 times the average size for all messages sent in the organization.

Connect to an Exchange 2007 server via Remote Desktop and log on with an account that has local administrative access and has been delegated the Exchange Organization Administrator role.

Follow the procedures in the Exchange 2007 Online Help topic How to Configure the Transport Dumpster.

1. Verify that Remote Desktop is enabled.
   
   
2. As an optional process, install Microsoft Network Monitor.
   
   

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Open the Disk Management Microsoft Management Console (MMC) and format, rename, and assign the appropriate Drive Letters so that the volumes and DVD drive match the appropriate server configuration. At the very least, there should be a D drive for the Exchange binaries and the DVD drive should be configured as the Z drive. Refer to the Database Log logical unit number (LUN) Appendix at the end of this document for the actual drive configuration that should be used.
   
   

   Drive configuration

   LUN	Drive letter	Usage
   1	C	Operating system
   2	D	Exchange binaries, tracking logs
   3	Z	DVD drive

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Insert the Windows Server 2003 Enterprise x64 Edition media.
   
   
3. Click Start, Control Panel and then double-click Add or Remove Programs.
   
   
4. Click Add/Remove Windows Components.
   
   
5. Click Application Server and select Details.
   
   
6. Click Internet Information Services and then click Details.
   
   

   Note:
   Enabled network COM+ access will be enabled also.

   1. Verify the World Wide Web service is selected.
      
      
   2. Click OK.
      
      
7. Click OK.
   
   
8. Click Next.
   
   
9. Click Finish.
   
   

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Insert the Exchange 2007 Configuration DVD.
   
   
3. Browse to \IE7\ and double-click IE7-install.bat.
   
   
4. Click Yes for any Digital Signature not Found dialog boxes that may appear.
   
   

   Note:
   These dialog boxes will not appear in environments that have not deployed the Windows Security templates.

5. Wait for all file copies to complete and restart the server.
   
   

All hotfixes are installed through a batch file. For a complete list of hotfixes that are installed, see Contoso server build DVD hotfix list. A sample hotfix list can be seen at Server Build DVD - Sample Hotfix List.

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access and was delegated local Administrator access.
   
   
2. Insert the Exchange 2007 Configuration DVD.
   
   
3. Browse to \W2K3-PostSP2\ and double-click W2K3-post-sp2.bat.
   
   
4. Click Yes for any Digital Signature not Found dialog boxes that may appear.
   
   

   Note:
   These dialog boxes will not appear in environments that have not deployed the Windows Security templates.

5. Wait for all file copies to complete and restart the server.
   
   

For the private network, ensure that the IP address scheme is not using the same subnet or network as any of the public network adapters.

Never use teaming for the private network. To ensure redundancy for your heartbeat connection, dedicate a private network for heartbeat communication and on the public network, configure it to use mixed communication. Then configure the network priority within the Cluster Administrator such that the private network has priority for sending heartbeat notifications.

For more information about the private network configuration in a non-MNS cluster, see the following Microsoft Knowledge Base articles: Recommended private "Heartbeat" configuration on a cluster server and Network adapter teaming and server clustering.

1. Connect to what will become the first node in the cluster via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures outlined in the section To configure the private network connections for a clustered mailbox server in the Exchange 2007 Online Help topic How to Configure Network Connections for Cluster Continuous Replication.
   
   

For the public network, ensure that the IP address scheme is not using the same subnet or network as any of the private network adapters, but is using the subnet or network used to route within your intranet.

Using teaming on the public network is acceptable in redundancy mode, but not in load balancing mode. However, if problems or issues seem to be related to teaming, Microsoft Product Support Services will require that teaming be disabled. If this resolves the issue, you must seek assistance from the hardware manufacturer.

1. Connect to what will become the first node in the cluster via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures outlined in the section To configure the public network connections for a clustered mailbox server from the Exchange 2007 Help Online topic How to Configure Network Connections for Cluster Continuous Replication.
   
   

1. Connect to what will become the first node in the cluster via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures outlined in the section To configure the network connection order for a clustered mailbox server from the Exchange 2007 Online Help article How to Configure Network Connections for Cluster Continuous Replication.
   
   

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Click Start, right-click My Computer and select Properties.
   
   
3. Click the Computer Name tab.
   
   
4. Click Change.
   
   
5. Choose the Domain option button and enter the appropriate domain name.
   
   
6. Enter the appropriate credentials.
   
   
7. Click OK and OK.
   
   
8. Click OK to close the System Properties.
   
   
9. Restart the server.
   
   

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Verify (or add if not already there) that the following accounts are members of the local administrators group on this server.
   
   

   Local administrators

   Item	Account	Description	Role
   1	Domain Admins	Domain Administrative Global Group	Administrator
   2	Root Domain\Exchange Organization Administrators	Exchange Administrators	Administrator

3. Verify that your user account is a member of a group which is a member of the local administrators group on the Windows Server 2003 server. If it is not, use an account that is a member of the local administrators group before continuing.
   
   

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Click Start, right-click My Computer and select Manage.
   
   
3. Expand to Local Users and Groups\Users.
   
   
4. Right-click Administrator and select Set Password. Change the password so that it meets strong complexity requirements.
   
   
5. Optional: Right-click Administrator and select Rename. Rename the account according to company regulations.
   
   

This section installs several useful tools that will aid administrators in Exchange administration and in troubleshooting support issues.

Note:
Debugging Tools for Windows will allow administrators to debug processes that are affecting service and determine root cause. For more information, please see Debugging Tools for Windows - Overview.

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Insert the Exchange 2007 Configuration DVD.
   
   
3. Open a command prompt and browse to the \Support folder.
   
   
4. Run the following command where DVDROM-Drive is the DVD drive: E2K7Toolsinstall.cmd DVDROM-Drive (ex: E2K7Toolsinstall.cmd Z:).
   
   
5. Right-click the c:\Tools folder and select Properties.
   
   
6. Click the Security tab.
   
   
7. Click the Advanced button.
   
   
8. Clear Inheritance and copy the permissions.
   
   
9. Remove the Everyone (and if listed, the Authenticated Users) security principal.
   
   
10. Add the following groups, granting FULL CONTROL:
    
    
    1. SYSTEM
       
       
    2. The local Administrators group
       
       
    3. Creator Owner
       
       

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Click Start, right-click My Computer and select Properties.
   
   
3. Select the Advanced tab.
   
   
4. Under Startup and Recovery, click the Settings button.
   
   
   1. Under Write Debugging Information, change the memory dump drop-down list to Kernel Memory Dump.
      
      
   2. Click OK.
      
      
5. Under Performance, click the Settings button.
   
   
6. Click the Advanced tab.
   
   
7. Under Virtual Memory, click the Change button.
   
   
8. On servers that have a dedicated page file drive, follow these steps:
   
   
   1. For the C: drive, set the Initial Size (MB) value to a minimum of 200 MB. (Windows requires between 150 MB and 2 GB of page file space. The amount depends on server load and on the amount of physical RAM that is available for page file space on the boot volume when Windows is configured for a kernel memory dump. Therefore, you may be required to increase the size.)
      
      
   2. For the C: drive, set Maximum Size (MB) to the value of Initial Size.
      
      
   3. For the P: drive, type the result of one of the following calculations in the Initial Size (MB) box:
      
      - If the server has less than 8 GB of RAM, multiply the amount of RAM times 1.5.
      
      - If the server has 8 GB of RAM or more, add the amount of RAM plus 10 MB.
      
      
   4. For the P: drive, set Maximum Size (MB) to the value of Initial Size.
      
      
   5. Delete any other page files.
      
      
   6. Click OK.
      
      
9. On servers that do not have a dedicated page file drive, follow these steps:
   
   
   1. For the C: drive, type the result of one of the following calculations in the Initial Size (MB) box:
      
      - If the server has less than 8 GB of RAM, multiply the amount of RAM times 1.5.
      
      - If the server has 8 GB of RAM or more, add the amount of RAM plus 10 MB.
      
      
   2. For the C: drive, set Maximum Size (MB) to the value of Initial Size.
      
      
   3. Delete any other page files.
      
      
   4. Click OK.
      
      
10. Click OK to close the System Properties dialog box.
    
    
11. Click No if you are prompted to restart the system.
    
    

    Note:
    For more information on Page File recommendations, see the following articles: How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP; and Overview of memory dump file options for Windows Vista, Windows Server 2008, Windows Server 2003, Windows XP, and Windows 2000. For systems with more than 2 GB of RAM, a complete memory dump cannot be used.

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Click Start and select My Computer.
   
   
3. Right-click the D Drive and select Properties.
   
   
4. Click the Security tab.
   
   
5. Select the Everyone group and then click Remove.
   
   
6. Select Users and then click Remove.
   
   
7. Click Add and select the local server from Locations.
   
   
8. Grant the following rights as outlined in the following table.
   
   

   Drive permissions

   Account	Permissions
   Administrators	Full Control
   SYSTEM	Full Control
   Authenticated Users	Read and Execute, List, Read
   CREATOR OWNER	Full Control

9. Click the Advanced button.
   
   
10. Select the CREATOR OWNER permission entry and then click View/Edit.
    
    
11. Select Subfolders and Files Only from the drop-down list.
    
    
12. Click OK two times.
    
    
13. Click OK to close the drive properties.
    
    
14. Repeat Steps 3-10 for each additional drive (other than the C Drive).
    
    

1. Submit a change request and have the computer object moved to the appropriate organizational unit (OU). If following the recommendations in the Exchange 2007 Security Guide, the OU will be \Member Servers\Exchange Backend Servers\Exchange Cluster Nodes.
   
   
2. Repeat step 1 for the second node that will exist in the cluster.
   
   

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Open a command prompt.
   
   
3. Verify that the server is in the correct domain and Active Directory site. At the command line run the following command:
   
   

   	Copy Code
   NLTEST /server:%COMPUTERNAME% /dsgetsite

4. The name of the Active Directory site to which the server belongs will be displayed. If the server is not in the correct Active Directory site, submit a change request to the appropriate operations group and have the server moved to the appropriate Active Directory site.
   
   
5. Repeat steps 1 through 4 for the second node that will exist in the cluster.
   
   

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Open a command prompt and change paths to the C drive.
   
   
3. Run the following command:
   
   

   	Copy Code
   dcdiag /s:<Domain Controller> /f:c:\dcdiag.log

   Note:
   Change <domain Controller> to a domain controller contained within the same Active Directory site as the Exchange server.

4. Review the output of C:\dcdiag.log file and verify that there are no connectivity issues with the local domain controller.
   
   
5. Repeat steps 3 and 4 for each domain controller in the local Active Directory site.
   
   

   Note:

   Domain Controller Diagnostics (DCDiag) is a Windows support tool that tests network connectivity and DNS resolution for domain controllers. If the account being used does not have administrative rights, several tests under the Doing primary tests heading may not pass. These tests can be ignored if the connectivity tests pass. In addition, the log file may report that some service validation tests did not pass. These messages can be ignored if the services do not exist on the domain controller.

Network Diagnostics (NETDIAG) is a Windows support tool that tests network connectivity and DNS resolution for workstations and servers. Look for tests that failed and messages designated as "FATAL," and use this information to isolate network and connectivity problems.

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Open a command prompt and change paths to the C drive.
   
   
3. Run the following command: netdiag /Q /L.
   
   
4. Review the output of C:\netdiag.log file and verify that there are no network or connectivity issues with the Exchange Server.
   
   
5. Repeat steps 1 through 4 for the second node that will exist in the cluster.
   
   

Connect to a server in the environment that either has the Exchange Best Practices Analyzer installed or the Exchange 2007 Management tools installed through Remote Desktop and log on with an account that has local administrative access. Depending on the configuration, do the following:

1. Click Start, All Programs, Microsoft Exchange and select Best Practices Analyzer.
   
   
2. Click Start, All Programs, Microsoft Exchange Server 2007 and select Exchange Management Console.
   
   
3. Click Toolbox.
   
   
4. Double-click Best Practices Analyzer.
   
   
5. Check and apply any updates for the Best Practices Analyzer engine.
   
   
6. Provide the appropriate information to connect to Active Directory and then click Connect to the Active Directory server.
   
   
7. In the Start a New Best Practices Scan, select Exchange 2007 Readiness Check and then click Start Scanning.
   
   
8. Review the report and take action on any errors or warnings that are reported by following the resolution articles that are provided within the Best Practices Analyzer.
   
   

   Note:
   The Microsoft Exchange Analyzers help Microsoft Exchange Server administrators troubleshoot various operational support issues.

1. Connect to the first cluster node via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures outlined in the section To use the New Server Cluster wizard to create a new cluster from the Exchange 2007 Online Help topic How to Create a Windows Server 2003 Failover Cluster for Cluster Continuous Replication.
   
   

1. Connect to the second cluster node via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures outlined in the section To use Cluster.exe to install a second node in a cluster from the Exchange 2007 Online Help topic How to Create a Windows Server 2003 Failover Cluster for Cluster Continuous Replication.
   
   

At a high level, the steps outlined here will create, secure, and enable the file share witness resource for the cluster.

1. Connect to one of the cluster nodes via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures from the Exchange 2007 Online Help topic How to Configure the File Share Witness.
   
   

1. Connect to one of the cluster nodes via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures from the Exchange 2007 Online Help topic How to Configure the Cluster Networking Components and Priority.
   
   

The configurable cluster heartbeats feature enables you to configure cluster heartbeat parameters. This may help avoid unnecessary cluster failovers. These failovers occur because of a temporary network problem that may cause packets to be dropped or delayed. The configurable cluster heartbeats feature may help in an environment where cluster nodes are geographically dispersed. For more information about the tolerance settings for missed cluster heartbeats, see An update is available that adds a file share witness feature and a configurable cluster heartbeats feature to Windows Server 2003 Service Pack 1-based server clusters.

1. Connect to one of the cluster nodes via Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures from the Exchange 2007 Online Help topic How to Configure Tolerance Settings for Missed Cluster Heartbeats.
   
   

The following prerequisites will be installed through a batch file.

(This note should be updated to list the appropriate list of hotfixes for your environment.)

• Microsoft .NET Framework Version 2.0 Redistributable Package (x64).
  
  
• MMC 3.0 update is available for Windows Server 2003 and for Windows XP.
  
  
• .NET FW 2.0 Hotfix.
  
  
• Windows PowerShell 1.0 English Language Installation Packages for Windows Server 2003 and for Windows XP.
  
  

The installation steps are as follows:

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Insert the Exchange 2007 Configuration DVD.
   
   
3. Browse to \E2K7-PreReqs\ and double-click E2K7-prereqs.bat.
   
   
4. Click Yes for any Digital Signature not Found dialog boxes that may appear.
   
   

   Note:
   These dialog boxes will not appear in environments that have not deployed the Windows Security templates.

5. Wait for all file copies to complete and restart the server.
   
   
6. Install the Microsoft Filter Pack. For more information, see 2007 Office System Converter: Microsoft Filter Pack.
   
   
7. Repeat steps 1 through 5 on the second node in the cluster.
   
   

1. Connect to the first node in the cluster via Remote Desktop and log on with an account that has local administrative access and has been delegated the Exchange Server Administrator role (or higher).
   
   
2. Follow the procedure of choice (command line, or setup GUI) from the Exchange 2007 Online Help topic How to Install the Active Clustered Mailbox Role in a CCR Environment on Windows Server 2003.
   
   

1. Connect to the second node in the cluster via Remote Desktop and log on with an account that has local administrative access and has been delegated the Exchange Server Administrator role (or higher).
   
   
2. Follow the procedure of choice (command line, or setup GUI) from the Exchange 2007 Online Help topic How to Install the Passive Clustered Mailbox Role in a CCR Environment on Windows Server 2003.
   
   

All hotfixes are installed through a batch file. For a complete list of hotfixes that are installed, see the Contoso server build DVD hotfix list.

A sample hotfix list can be seen at Server Build DVD - Sample Hotfix List.

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access and was delegated local Administrator access.
   
   
2. Insert the Exchange 2007 Configuration DVD.
   
   
3. Browse to \E2K7-PostSP1\ and double-click E2K7-postsp1.bat.
   
   
4. Click Yes for any Digital Signature not Found dialog boxes that may appear.
   
   

   Note:
   These dialog boxes will not appear in environments that have not deployed the Windows Security templates.

5. Wait for all file copies to complete and restart the server.
   
   
6. Repeat steps 1 through 5 on the passive node.
   
   

1. Connect to the server through Remote Desktop, and then log on by using an account that has local administrative access.
   
   
2. Follow the instructions that are in How to Register IFilters 2.0 with Exchange 2007 and Exchange 2010.
   
   
3. If you want to search through PDF files, install the Adobe PDF iFilter 9 for 64-bit platforms, and then follow the instructions that are mentioned in the Adobe document Configuring PDF iFilter for MS Exchange Server 2007.
   
   
4. The third-party Web site information in this topic is provided to help you find the technical information you need. The URLs are subject to change without notice.
   
   

1. Connect to the server via Remote Desktop and log on with an account that has local administrative access and has been delegated the Exchange Server Administrator role (or higher).
   
   
2. Click Start, All Programs, Microsoft Exchange Server 2007 and select Exchange Management Shell. Use the following table for information needed for the commands.
   
   

   Important:
   The values in the table below are example values, not recommended values. These values must be updated to reflect the actual values for your organization.

   First storage group information

   	Old	New example
   Storage Group Name	First Storage Group	SG1
   Database Name	Mailbox Database	<CMSName> MBX Store 1
   Storage Group Path	<Exchange Install Path>\Mailbox\First Storage Group	L:\LOG01
   Database Path	<Exchange Install Path>\Mailbox\First Storage Group	E:\MDB01
   Database Filename	Mailbox database.edb	Priv01.edb

3. Suspend replication running the following command where <CMSName> is the name of the clustered mailbox server using the following command:
   
   

   	Copy Code
   Suspend-StorageGroupCopy "<CMSName>\First Storage Group"

4. Dismount the database running the following command where <CMSName> is the name of the clustered mailbox server:
   
   

   	Copy Code
   Dismount-Database "<CMSName>\First Storage Group\Mailbox Database"

5. To change the Storage Group name from “First Storage Group” to “SG1” run the following command where <DCName> is the name of a domain controller:
   
   

   	Copy Code
   Set-StorageGroup "<CMSName>\<Old SG Name>" -Name <New SG Name> -DomainController <DCName>

6. To change the mailbox database name from “Mailbox Database” to “<CMSName> MBX Store 1” run the following command:
   
   

   	Copy Code
   Set-MailboxDatabase "<CMSName>\<New SG Name>\<Old DB Name>" -Name "<New DB Name>" -DomainController <DCName>

7. To change the location of the storage group’s transaction logs, run the following command:
   
   

   	Copy Code
   Move-StorageGroupPath "<CMSName>\<New SG Name>" -LogFolderPath:<New SG Location> -SystemFolderPath:<New SG Path> -DomainController <DCName> -ConfigurationOnly

8. To change the location of the mailbox database, run the following command:
   
   

   	Copy Code
   Move-DatabasePath "<CMSName>\<New SG Name>\<New DB Name>" -EdbFilePath:<New DB Path\New DB FileName> -DomainController <DCName> -ConfigurationOnly

9. Move the files (database, logs, and checkpoint file) to their new locations on both the active and passive node.
   
   
10. To mount the database, run the following command:
    
    

    	Copy Code
    Mount-Database "<CMSName>\<New SG Name>\<New DB Name>" -DomainController <DCName>

11. Restart replication run the following command:
    
    

    	Copy Code
    Resume-StorageGroupCopy "<CMSName>\<New SG Name>"

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access and was delegated the Exchange Organization Administrator role.
   
   
2. Follow the procedure outlined in the Exchange 2007 Online Help topic How to Enter the Product Key.
   
   

This section is optional and may be skipped.

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Follow the procedures from the Exchange 2007 Online Help topic How to Install the Security Configuration Wizard to install the Security Configuration Wizard.
   
   
3. Follow the procedures from the Exchange 2007 Online Help topic How to Register Exchange Server Role SCW Extensions to register the Exchange 2007 Edge Transport server SCW extension.
   
   
4. Follow the procedures from the Exchange 2007 Online Help topic How to Create a New Exchange Server Role SCW Policy to configure and apply the policy.
   
   

By default, Exchange Server 2007 optimizes the server’s memory management for programs, which configures the server’s system cache as the default size. Mailbox servers will benefit from this configuration.

1. Connect to the server through Remote Desktop and log on with an account that has local administrative access.
   
   
2. Click Start, right-click My Computer and select Properties.
   
   
3. Select the Advanced tab.
   
   
4. Under Performance, click the Settings button.
   
   
   1. Click the Advanced tab.
      
      
   2. Verify that the Processor Scheduling is set to Background Services.
      
      
   3. Verify that the Memory Usage is set to System Cache.
      
      
5. Click OK.
   
   
6. Repeat steps 1 through 5 on the second node in the cluster.
   
   

CCR provides an attribute for Mailbox servers that you can use to control unscheduled outage recovery behavior. The attribute, AutoDatabaseMountDial, has three possible values: Lossless, Good availability, and Best availability.

• When the attribute is set to Lossless, the system waits for the failed node to come back online before databases are mounted. Even then the failed system must return with all logs accessible and not corrupted. After the failure, the passive node is made active, and the Information Store is brought online. It checks to see if the databases can be mounted without any data loss. If they can, the databases are mounted. If not, the system periodically attempts to copy the logs. If the server returns with its logs intact, this attempt will eventually succeed, and the databases will mount. If the server returns without its logs intact, the remaining logs will not be available, and the affected databases will not mount.
  
  
• Good availability provides fully automatic recovery when replication is operating normally and replicating logs at the rate they are being generated.
  
  
• Best availability, which is the default setting, operates similarly to Good availability, but it allows automatic recovery when the replication experiences slightly more latency. Thus, the new active node might be slightly farther behind the state of the old active node after the failover, thereby increasing the likelihood that database divergence occurs, which requires a full re-seed to correct.
  
  

  Note:
  By default CCR is configured to use Best Availability. Normally this setting should not be changed. Therefore, this section may be skipped.

Several of the diagnostics tasks used to monitor Exchange require test mailboxes to be created on the Mailbox servers. For more information about how to use the Test script to create the test mailboxes, see the Monitoring for Agentless Servers topic in the Exchange 2007 Online Help.

1. Connect to the Exchange 2007 Mailbox server through Remote Desktop and log on with an account that has local administrative access and was delegated the Exchange Server Administrator role (or higher).
   
   
2. Click Start, All Programs, Microsoft Exchange Server 2007 and select Exchange Management Shell.
   
   
3. Change the directory path to <Exchange Server Install Path>\Scripts.
   
   
4. Type New-TestCasConnectivityUser.ps1 and press Enter.
   
   
5. Enter a temporary password and follow the prompts to create the test mailboxes.
   
   

In Exchange 2007, moving resources between nodes should be handled through the Exchange Management Shell and not through the Cluster Administrator program or cluster.exe.

1. Connect to an Exchange 2007 server via Remote Desktop and log on with an account that has local administrative access and has been delegated the Exchange Server Administrator role (or higher).
   
   
2. Click Start, All Programs, Microsoft Exchange Server 2007 and select Exchange Management Shell.
   
   
3. Run the following command to move the clustered mailbox server where <CMSName> is the name of the clustered mailbox server and <ServerNode2> is the name of the passive node in the cluster:
   
   

   	Copy Code
   Move-ClusteredMailboxServer <CMSName> -TargetMachine <ServerNode2> -MoveComment "Handoff test"

4. Verify that the clustered mailbox server is online and ready by runing the following command:
   
   

   	Copy Code
   Get-ClusteredMailboxServerStatus <CMSName>

5. Repeat steps 3-4 to move the resources back to the active node (now the passive node).
   
   

This section can be skipped if messaging records management (MRM) will not be enabled in the environment. For more information about how to deploy MRM, see the Deploying Messaging Records Management topic in the Exchange 2007 Online Help.

1. Connect to an Exchange 2007 server through Remote Desktop and log on with an account that has local administrative access and was delegated the Exchange Server Administrator role (or higher).
   
   
2. Click Start, All Programs, Microsoft Exchange Server 2007 and select Exchange Management Shell.
   
   
3. To enable the managed folder assistant, run the following command where <ServerName> is the name of the mailbox server and <DCName> is the name of a domain controller:
   
   

   Copy Code

   Set-MailboxServer <ServerName> -LogPathForManagedFolders <LogPath> -ManagedFolderAssistantSchedule <AssistantSchedule> -LogFileAgeLimitForManagedFolders <LogFileAgeLimit> -LogDirectorySizeLimitForManagedFolders <LogDirSizeLimit> -LogFileSizeLimitForManagedFolders <LogFileSizeLimit> -FolderLogForManagedFoldersEnabled <LogFolderEnabled> -SubjectLogForManagedFoldersEnabled <SubjectLogEnabled> -RetentionLogForManagedFoldersEnabled <RetentionLogEnabled> -JournalingLogForManagedFoldersEnabled <JournalLogEnabled> -DomainController <DCName>

Note:
Use the appropriate table from Server Configuration Appendix at the end of this document for information that you need for the commands.

This section can be skipped if the default Message Tracking parameters are appropriate for the environment.

1. Connect to an Exchange 2007 server through Remote Desktop and log on with an account that has local administrative access and was delegated the Exchange Server Administrator role (or higher).
   
   
2. Click Start, All Programs, Microsoft Exchange Server 2007 and select Exchange Management Shell.
   
   
3. To configure message tracking settings, run the following command where <ServerName> is the name of the mailbox server and <DCName> is the name of a domain controller:
   
   

   	Copy Code
   Set-MailboxServer <ServerName> -MessageTrackingLogPath <LogPath> -MessageTrackingLogMaxAge <MaxAge> -MessageTrackingLogMaxDirectorySize <LogDirSize> -MessageTrackingLogMaxFileSize <LogFileSize> -MessageTrackingLogSubjectLoggingEnabled <SubjectLogEnabled> -DomainController <DCName>

Note:
Use the appropriate table from Server Configuration Appendix at the end of this topic for information that you need for the commands.

1. Connect to an Exchange 2007 server via Remote Desktop and log on with an account that has local administrative access and has been delegated the Exchange Server Administrator role (or higher).
   
   
2. Click Start, All Programs, Microsoft Exchange Server 2007 and select Exchange Management Shell.
   
   
3. Use the appropriate table from Database / Log LUN Appendix and Database Configuration Appendix at the end of this topic for information needed for the commands.
   
   
4. To create the Storage Group, run the following command where <CMSName> is the name of the clustered mailbox server and <DCName> is the name of a domain controller:
   
   

   	Copy Code
   New-StorageGroup -Server <CMSName> -Name <SG> -LogFolderPath <Transaction Log Location> -SystemFolderPath <Transaction Log Location> -DomainController <DCName>

5. To create the database that resides within the storage group, run the following command:
   
   

   Copy Code

   New-MailboxDatabase -StorageGroup "<CMSName>\<SG Name>" -Name "<DB Name>" -DomainController <DCName> -OfflineAddressBook <OfflineAddressBook> -PublicFolderDatabase <PFDatabase> | Set-MailboxDatabase -IssueWarningQuota <WarningQuota> -ProhibitSendQuota <SendQuota> -ProhibitSendReceiveQuota <SendReceiveQuota> -MailboxRetention <dd.hh:mm:ss> -DeletedItemRetention <dd.hh:mm:ss> -MaintenanceSchedule <MaintenanceSchedule> -QuotaNotificationSchedule <QuotaSchedule> -RetainDeletedItemsUntilBackup <RetainDeletedItemsUntilBackup> -EdbFilePath:<FullPathIncludingDatabaseFileName>

6. To mount the database, run the following command:
   
   

   	Copy Code
   Mount-Database "<CMSName>\<SG>\<Database Name>" -DomainController <DCName>

7. Repeat steps 3-6 for each database that needs to be created.
   
   

The following table is an example configuration that can be applied to the mailbox server, depending on requirements.

Important:
The values in the following table are example values, not recommended values. These values must be updated to reflect the actual values for your organization.

The following table is an example configuration that can be applied to the Mailbox server, depending on requirements.

Important:
The values in the following table are example values, not recommended values. These values must be updated to reflect the actual values for your organization.

With continuous replication it is not necessary to perform daily full backups as the storage group copy provides the first line of defense against corruption and data loss. As a result, there are two approaches as to how backups can be performed in a continuous replication environment.

• Use streaming backup to perform a full backup of 1/7th of the databases, and incremental or differential backups for the remainder.
  
  
• Use Volume Shadow Copy Service (VSS) to perform backups.
  
  

As a result of the backup methodology selected, the LUN layout needs to be altered.

With streaming backups, it is recommended to separate streaming I/O (source and target) so that multiple storage groups being backed up concurrently do not compete for the same disk resources. Whether the target is disk or tape, there will be a throughput limit on the physical disks and controllers unique to each hardware solution. It may be necessary to isolate some storage groups from each other to maximize the number of concurrent backup operations, and throughput in order to minimize the size of the backup window.

You can run streaming backups concurrently, one from each LUN, if you isolate your storage group LUNs from each other. The backup jobs should complete on the first storage group on each LUN before the second storage group begins to back up, isolating the backup streams. Two streaming backup jobs on the same physical disks may not be twice as fast, but it should be faster than a single streaming backup job with regard to the megabytes per second.

A backup set is the number of databases that are fully backed up in a night. A solution that performs a full backup on 1/7th of the databases nightly could reduce complexity by placing all of the storage groups to be backed up on the same log and database LUN. This can reduce the number of LUNs on the server.

Some of the benefits of this strategy include:

• Simplified storage administration. Fewer LUNs to manage.
  
  
• Potentially reduce the number of backup jobs.
  
  

Some of the concerns with this strategy include:

• Limits the ability to take hardware-based VSS backup and restores.
  
  
• The 2 TB limit on an MBR partition would limit how far this would scale in capacity.
  
  
• A capacity or corruption problem on a single LUN could affect more than one storage group.
  
  

  1/7th approach LUN design

  SG Name	Database Name	Database Location	Database File Name	Transaction Log Location
  SG1	<CMSName> MBX Store 1	E:\MDB01	Priv01.edb	L:\LOG01
  SG2	<CMSName> MBX Store 2	E:\MDB02	Priv02.edb	L:\LOG02
  SG3	<CMSName> MBX Store 3	E:\MDB03	Priv03.edb	L:\LOG03
  SG4	<CMSName> MBX Store 4	E:\MDB04	Priv04.edb	L:\LOG04
  SG5	<CMSName> MBX Store 5	E:\MDB05	Priv05.edb	L:\LOG05
  SG6	<CMSName> MBX Store 6	E:\MDB06	Priv06.edb	L:\LOG06
  SG7	<CMSName> MBX Store 7	E:\MDB07	Priv07.edb	L:\LOG07
  SG8	<CMSName> MBX Store 8	F:\MDB08	Priv08.edb	M:\LOG08
  SG9	<CMSName> MBX Store 9	F:\MDB09	Priv09.edb	M:\LOG09
  SG10	<CMSName> MBX Store 10	F:\MDB10	Priv10.edb	M:\LOG10
  SG11	<CMSName> MBX Store 11	F:\MDB11	Priv11.edb	M:\LOG11
  SG12	<CMSName> MBX Store 12	F:\MDB12	Priv12.edb	M:\LOG12
  SG13	<CMSName> MBX Store 13	F:\MDB13	Priv13.edb	M:\LOG13
  SG14	<CMSName> MBX Store 14	F:\MDB14	Priv14.edb	M:\LOG14
  SG15	<CMSName> MBX Store 15	G:\MDB15	Priv15.edb	N:\LOG15
  SG16	<CMSName> MBX Store 16	G:\MDB16	Priv16.edb	N:\LOG16
  SG17	<CMSName> MBX Store 17	G:\MDB17	Priv17.edb	N:\LOG17
  SG18	<CMSName> MBX Store 18	G:\MDB18	Priv18.edb	N:\LOG18
  SG19	<CMSName> MBX Store 19	G:\MDB19	Priv19.edb	N:\LOG19
  SG20	<CMSName> MBX Store 20	G:\MDB20	Priv20.edb	N:\LOG20
  SG21	<CMSName> MBX Store 21	G:\MDB21	Priv21.edb	N:\LOG21
  SG22	<CMSName> MBX Store 22	H:\MDB22	Priv22.edb	O:\LOG22
  SG23	<CMSName> MBX Store 23	H:\MDB23	Priv23.edb	O:\LOG23
  SG24	<CMSName> MBX Store 24	H:\MDB24	Priv24.edb	O:\LOG24
  SG25	<CMSName> MBX Store 25	H:\MDB25	Priv25.edb	O:\LOG25
  SG26	<CMSName> MBX Store 26	H:\MDB26	Priv26.edb	O:\LOG26
  SG27	<CMSName> MBX Store 27	H:\MDB27	Priv27.edb	O:\LOG27
  SG28	<CMSName> MBX Store 28	H:\MDB28	Priv28.edb	O:\LOG28
  SG29	<CMSName> MBX Store 29	I:\MDB29	Priv29.edb	P:\LOG29
  SG30	<CMSName> MBX Store 30	I:\MDB30	Priv30.edb	P:\LOG30
  SG31	<CMSName> MBX Store 31	I:\MDB31	Priv31.edb	P:\LOG31
  SG32	<CMSName> MBX Store 32	I:\MDB32	Priv32.edb	P:\LOG32
  SG33	<CMSName> MBX Store 33	I:\MDB33	Priv33.edb	P:\LOG33
  SG34	<CMSName> MBX Store 34	I:\MDB34	Priv34.edb	P:\LOG34
  SG35	<CMSName> MBX Store 35	I:\MDB35	Priv35.edb	P:\LOG35
  SG36	<CMSName> MBX Store 36	J:\MDB36	Priv36.edb	Q:\LOG36
  SG37	<CMSName> MBX Store 37	J:\MDB37	Priv37.edb	Q:\LOG37
  SG38	<CMSName> MBX Store 38	J:\MDB38	Priv38.edb	Q:\LOG38
  SG39	<CMSName> MBX Store 39	J:\MDB39	Priv39.edb	Q:\LOG39
  SG40	<CMSName> MBX Store 40	J:\MDB40	Priv40.edb	Q:\LOG40
  SG41	<CMSName> MBX Store 41	J:\MDB41	Priv41.edb	Q:\LOG41
  SG42	<CMSName> MBX Store 42	J:\MDB42	Priv42.edb	Q:\LOG42
  SG43	<CMSName> MBX Store 43	K:\MDB43	Priv43.edb	R:\LOG43
  SG44	<CMSName> MBX Store 44	K:\MDB44	Priv44.edb	R:\LOG44
  SG45	<CMSName> MBX Store 45	K:\MDB45	Priv45.edb	R:\LOG45
  SG46	<CMSName> MBX Store 46	K:\MDB46	Priv46.edb	R:\LOG46
  SG47	<CMSName> MBX Store 47	K:\MDB47	Priv47.edb	R:\LOG47
  SG48	<CMSName> MBX Store 48	K:\MDB48	Priv48.edb	R:\LOG48
  SG49	<CMSName> MBX Store 49	K:\MDB49	Priv49.edb	R:\LOG49

Exchange 2007 uses VSS included in Windows 2003 to take volume shadow copies of Exchange Server 2007 databases and transaction log files. For the basics on VSS, including both clone and snapshot techniques, review the white paper, Best Practices for Using Volume Shadow Copy Service with Exchange Server 2003.

The new feature in Exchange Server 2007 when using continuous replication, is the ability to run software VSS snapshot not just on the active copy, but on the passive copy, as well. Taking a VSS snapshot on the passive copy offloads the disk I/O from the active LUN during both the checksum integrity (ESEUTIL), and subsequent copy to tape or disk. This also frees more time on the active LUNs to run online maintenance, MRM, and other tasks.

Creating two LUNs (log and database) for a storage group is the standard best practice for Exchange 2003. With Exchange 2007, in the maximum case of 50 storage groups, the number of LUNs you provision will depend upon your backup strategy. If your recovery time objective (RTO) is very small, or if you use VSS clones for fast recovery, it may be best to place each storage group on its own transaction log LUN and database LUN. Because doing this will exceed the number of available drive letters, volume mount points must be used.

Some of the benefits of this strategy include:

• Enables hardware-based VSS at a storage group level, providing single storage group backup and restore.
  
  
• Flexibility to isolate the performance between storage groups when not sharing spindles between LUNs.
  
  
• Increased reliability. A capacity or corruption problem on a single LUN will only affect one storage group.
  
  

Some of the concerns with this strategy include:

• 50 storage groups using continuous replication could require 200 LUNs which would exceed some storage array maximums. CCR solutions could have 100 LUNs on each node, while LCR could have all 200 LUNs presented to a single server.
  
  
• A separate LUN for each storage group causes more LUNs per server increasing the administrative costs and complexity.
  
  

  Note:
  In the following table, MP stands for Mount Point.

The following table is an example configuration that can be applied to each database that is created, or customized for each database on the server depending on requirements.

Important:
The values in the following table are example values, not recommended values. These values must be updated to reflect the actual values for your organization.