By having an installation guide, Company_Name can guarantee standardization across the enterprise, reduce Total Cost of Ownership, and ease troubleshooting steps.

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

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

This document assumes that Windows Server 2008 x64 Edition is installed according to company baseline regulations. This includes the latest approved service pack and hotfixes.

This document assumes that forest and domain preparation steps were finished as described in the Exchange 2007 Online Help topic How to Prepare Active Directory and Domains.

This document assumes that Exchange 2007 and Windows Server 2008 are secured as described in the following best practices documents:

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

Important:
Follow the procedures in this document sequentially. Unexpected results may occur if changes are made out of sequence.

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

Because clustered Mailbox servers in a CCR environment replicate data asynchronously, there is data loss during a lossy failover. To help reduce the effect of this, the Hub Transport server role has a feature that temporarily keeps mail that was recently delivered to a CCR server. This feature is known as the transport dumpster. If there is 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 the last log generated.) The transport dumpster is for clustered Mailbox servers in a CCR environment only.

The transport dumpster is an organizational setting and, therefore, should be configured appropriately to handle all clustered Mailbox servers in a CCR environment within the organization. Additionally, be aware that the transport dumpster is configured per storage group and per clustered Mailbox server in an Active Directory directory service site.

By default, the transport dumpster is enabled to support environments that deploy CCR and that have the following settings:

• MaxDumpsterSizePerStorageGroup – 18 megabytes (MB)
  
• MaxDumpsterTime – 7 days
  

We recommend that you configure the MaxDumpsterSizePerStorageGroup parameter. This 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 use 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 through Remote Desktop, and then log on by using an account that has local administrative access and that is 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. For more information, see the Microsoft Network Monitor Web site.
   

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Click Start, click Administrative Tools, and then select Computer Management.
   
3. Expand Storage, and then click Disk Management.
   
4. 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. The following table describes the 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

All hotfixes are installed by using a batch file. For a complete list of hotfixes that are installed, see the Contoso server build DVD hotfix list. A sample hotfix list is available at Server Build DVD - Sample Hotfix List.

1. Connect to the server through Remote Desktop, and then log on by using an account that has local administrative access and that is delegated local Administrator access.
   
2. Insert the Exchange 2007 Configuration DVD.
   
3. Move to the \W2K8-HotFix folder, and then double-click W2K8-hotfix.bat.
   
4. Click Yes if a Digital Signature not Found dialog box appears.
   

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

5. Wait for the files to copy, and then restart the server.
   

For the private network, make sure 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. For more information, see Microsoft Knowledge Base article 254101, Network adapter teaming and server clustering.

1. Connect to what will become the first node in the cluster through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Click Start, click Control Panel, and then double-click Network and Sharing Center.
   
3. Click Manage network connections.
   
4. Locate the connection for the internal network, and then rename the connection with an appropriate name.
   
5. Right-click the connection, and then click Properties.
   
6. In the network connection properties, on the General tab, verify that the Client for Microsoft Networks, Internet Protocol Version 4 (TCP/IPv4) and File and Printer Sharing for Microsoft Networks check boxes are selected in the This connection uses the following items area.
   
7. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
   
8. In Internet Protocol Version 4 (TCP/IPv4) Properties, click Advanced.
   
9. On the DNS tab, verify the following information in Advanced TCP/IP Settings:
   
   1. Make sure that addresses are not listed in the DNS server addresses, in order of use area if this is a private network.
      
   2. Make sure that the Register this connection's addresses in DNS check box is cleared.
      
10. On the WINS tab, make sure that Disable NetBIOS over TCP/IP is not selected.
    
11. Click OK two times to save the changes, and then click Close to exit Properties.
    

Make sure that the IP address scheme for the public network is not using the same subnet or network as any private network adapters. Instead, the public network must use the subnet or network that is used to route network traffic within your intranet.

Teaming can be used on the public network in redundancy mode, but it cannot be used in load balancing mode. However, if problems or issues occur that are related to teaming, Microsoft Customer Support Services will require you to disable teaming. If this resolves the issue, you must seek assistance from the hardware manufacturer. For more information about teaming, see Microsoft Knowledge Base article 254101, Network adapter teaming and server clustering.

1. Connect to what will become the first node in the cluster through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Click Start, click Control Panel, and then double-click Network and Sharing Center.
   
3. Click Manage network connections.
   
4. Locate the connection for the internal network, and then rename the connection with an appropriate name.
   
5. Right-click the connection, and then select Properties.
   
6. In the network connection's properties on the General tab, make sure that the Client for Microsoft Networks, Internet Protocol Version 4 (TCP/IPv4) and File and Printer Sharing for Microsoft Networks check boxes are selected in the This connection uses the following items area.
   
7. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
   
8. In Internet Protocol Version 4 (TCP/IPv4) Properties, click Advanced.
   
9. In Advanced TCP/IP Settings, verify the following information on the DNS tab:
   
   1. Make sure that all the required addresses are listed in the DNS server addresses, in order of use area.
      
   2. Make sure that the correct suffixes are listed in the Append these DNS suffixes (in order) area.
      
10. On the WINS tab, make sure that Disable NetBIOS over TCP/IP is not selected.
    
11. Click OK two times to save the changes, and then click Close to exit Properties.
    

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Click Start, right-click Computer, and then click Properties.
   
3. In the Computer Name, domain, and workgroup settings area, click Change Settings.
   
4. In System Properties, click Change.
   
5. In the Member of area, click Domain, and then type the appropriate domain name.
   
6. Enter the appropriate credentials.
   
7. Click OK two times, and then close System Properties.
   
8. Restart the server.
   

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Verify that the following accounts are members of the local administrators group on this server. Add the accounts if they are not already there.
   

   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 the account you are using is a member of a group that is a member of the local administrators group on the Windows Server 2008-based server. If it is not, log on by using an account that is a member of the local administrators group before continuing.
   

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

This section installs several tools that will help with Exchange administration and with troubleshooting support issues.

Note   Debugging Tools for Windows help administrators to debug processes that are affecting service. For more information, see Install Debugging Tools for Windows 64-bit Version.

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Insert the Exchange 2007 Configuration DVD.
   
3. Open a command prompt, and then move to the \Support folder on the DVD.
   
4. Run the following command, where <DVDROM-Drive> is the DVD drive letter:
   

W2K8Toolsinstall.cmd <DVDROM-Drive> 

1. Right-click the C:\Tools folder, and then click Properties.
   
2. On the Security tab, click Advanced.
   
3. Click to clear the Include inheritable permissions from this object's parent check box, and then click Edit.
   
4. In the Permission entries list, click Everyone, and then click Remove. Also remove the Authenticated Users security principal if it is listed in this list.
   
5. Click Add, and then add the following groups, and grant each group FULL CONTROL permission:
   
   • SYSTEM
     
   • The local Administrators group
     
   • Creator Owner
     

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Click Start, right-click Computer, and then click Properties.
   
3. Click Advanced system settings.
   
4. In the Startup and Recovery area, click Settings.
   
5. In the Write Debugging Information area, select Kernel Memory Dump in the list, and then click OK.
   
6. In the Performance area, click Settings.
   
7. On the Advanced tab, in the Virtual Memory area, click Change.
   
8. On servers that have a dedicated page file drive, follow these steps:
   
   1. In the Drive list, click C:, and then click Custom size.
      
   2. For the C: drive, set the Initial Size (MB) value to a minimum of 200 MB. (Windows requires between 150 MB and 2 GB page file space, depending on server load and 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.)
      
   3. For the C: drive, set the Maximum Size (MB) value to that of the Initial Size.
      
   4. In the Drive list, select the page file drive (for example, the P: drive), and then click Custom size.
      
   5. In the Initial Size (MB) box, type the result of one of the following calculations:
      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.
      
   6. In the Maximum Size (MB) box, type the same amount that you typed in the Initial Size box.
      
   7. Delete all other page files.
      
   8. Click OK.
      
9. On servers that do not have a dedicated page file drive, follow these steps:
   
   1. In the Drive list, click C:, and then click Custom size.
      
   2. For the C: drive, in the Initial Size (MB) box, type the result of one of the following calculations:
      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.
      
   3. Delete all other page files.
      
   4. Click OK.
      
10. Click OK two times to close the System Properties dialog box.
    
11. Click No if prompted to restart the system.
    

    Note:

    For more information on Page File recommendations, see the following articles: Configuring paging files for optimization and recovery in Windows Server 2003, in Windows 2000, and in Windows NT; 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.

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Click Start, and then click Computer.
   
3. Right-click the D Drive, and then click Properties.
   
4. On the Security tab, click Edit.
   
5. Grant the following rights as outlined in the following table. Click Add, and then select the local server from Locations to add accounts that are listed in the table, but are not listed in the Group or user names list.
   

   Drive permissions

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

6. Click OK to return to D Drive Properties.
   
7. On the Security tab, click Advanced.
   
8. On the Permissions tab, click Edit.
   
9. In the Permission entries table, click CREATOR OWNER, and then click Edit.
   
10. In the Apply to list, click Subfolders and files only.
    
11. Click OK three times.
    
12. Click OK to close the drive properties.
    
13. Repeat steps 3 through 12 for each additional drive (other than drive C).
    

Submit a change request and have the computer object moved to the appropriate organizational unit (OU). If you are following the recommendations in the Exchange 2007 Security Guide, the OU will be \Member Servers\Exchange Backend Servers\Exchange Mailbox Servers.

Verify that the server is in the correct domain and Active Directory site. 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 site. To verify that the domain and Active Directory site are correct, follow these steps:

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Open a command prompt, and then type the following command:
   
   NLTEST /server:%COMPUTERNAME% /dsgetsite

The name of the Active Directory site to which the server belongs is displayed.

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Open a command prompt, and then change paths to drive C.
   
3. Type the following command:
   
   dcdiag /s:<Domain Controller> /f:c:\dcdiag.log

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

4. Review the output of the C:\Dcdiag.log file, and then 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 credentials, 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.

1. Use Remote Desktop to connect to a server in the environment that has the Exchange Server Best Practices Analyzer or the Exchange 2007 Management tools installed. Then, use an account that has local administrative access to log on. Depending on the configuration, do one of the following:
   
   1. Click Start, click All Programs, click Microsoft Exchange, and then click Best Practices Analyzer.
      
   2. Click Start, click All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Console.
      
2. Click Toolbox.
   
3. Double-click Best Practices Analyzer.
   
4. Click Download the latest updates to apply any updates for the Best Practices Analyzer engine.
   
5. Provide the appropriate information to connect to Active Directory, and then click Connect to the Active Directory server.
   
6. On the Start a New Best Practices Scan page, in the Select the type of scan to perform area, click Exchange 2007 Readiness Check, and then click Start Scanning.
   
7. Review the report. Following the resolution articles that are provided and take action on any errors or warnings that are reported by the Best Practices Analyzer.
   

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

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Open an administrative Command Prompt window.
   
3. Type the following command where <path> references the E2K7 CONFIG DVD \E2K7-PreReqs folder:
   
   ServerManagerCmd -ip <path>\Exchange-Base.XML

4. Type the following command where <path> references the E2K7 CONFIG DVD \E2K7-PreReqs folder, and <Exchange-role> references the appropriate role XML file:
   
   ServerManagerCmd -ip <path>\<Exchange-role>.XML

5. Restart the server if it is required.
   

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Follow the procedures outlined in the "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 2008 Failover Cluster for Cluster Continuous Replication.
   

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Follow the procedures from the Exchange 2007 Online Help topic How to Configure Cluster Networks for a Failover Cluster.
   

All hotfixes are installed by using a batch file. For a complete list of hotfixes that are installed, see the Contoso server build DVD hotfix list. A sample hotfix list is available at Server Build DVD - Sample Hotfix List.

1. Connect to the server through Remote Desktop, and then log on by using an account that has local administrative access and that is delegated local Administrator access.
   
2. Insert the Exchange 2007 Configuration DVD.
   
3. Move to the \W2K8-HotFix folder, and then double-click W2K8-clus-hotfix.bat.
   
4. Click Yes if a Digital Signature not Found dialog box appears.
   

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

5. Wait for the files to copy, and then restart the server. Repeat the process on all remaining nodes within the cluster.
   

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

1. Connect to one of the cluster nodes through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Follow the procedures from the Exchange 2007 Online Help topic How to Configure the Node and File Share Majority Quorum.
   

In Windows Server 2008, the way that clusters are qualified has changed significantly with the introduction of the Validate a Configuration Wizard. This wizard is a new feature that is integrated into failover clustering in Windows Server 2008. With the cluster validation wizard, you can run a set of focused tests on a collection of servers that you intend to use as nodes in a cluster. This cluster validation process tests the underlying hardware and software to obtain an accurate assessment of how well failover clustering can be supported on a given configuration. In fact, a cluster validation report is required by Microsoft Customer Support Services (CSS) as a condition of Microsoft supporting a given configuration. For more information about the validation process, see the Windows Server 2008 Online Help topic, Failover Cluster Step-by-Step Guide: Validating Hardware for a Failover Cluster.

1. Connect to one of the cluster nodes by using Remote Desktop, and then log on with an account that has local administrative access.
   
2. Follow the procedures in the Exchange 2007 Online Help topic, How to Validate a Windows Server 2008 Failover Cluster Configuration.
   

1. Connect to one of the cluster nodes through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Open an administrative Command Prompt window.
   
3. Type the following command, where <Cluster Name Object> references the cluster network name:
   
   cluster <Cluster Name Object> group "Cluster Group" /move

4. Verify that the return response indicates that the Cluster Group is online.
   

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

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

In Exchange 2007, moving resources between nodes should be handled by using the Exchange Management Shell instead of the Cluster Administrator program or the Cluster.exe program.

1. Connect to an Exchange 2007 server through Remote Desktop, and then log on by using an account that has been delegated the Exchange Server Administrator role (or higher).
   
2. Click Start, click All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell.
   
3. Move the clustered Mailbox server. To do this, run the following command in the Exchange Management Shell, where <CMSName> is the name of the clustered Mailbox server and <ServerNode2> is the name of the passive node in the cluster:
   
   Move-ClusteredMailboxServer <CMSName> -TargetMachine <ServerNode2> -MoveComment "Handoff test"

4. Verify that the clustered mailbox server is online and ready. To do this, run the following command:
   
   Get-ClusteredMailboxServerStatus <CMSName>

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

Install all hotfixes that are released since Exchange Server 2007 Service Pack 1 (SP1). All hotfixes are installed by using a batch file. To view a sample hotfix list, see the Exchange Help topic Server Build DVD - Sample Hotfix List.

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Insert the Exchange 2007 Configuration DVD in the DVD drive.
   
3. Move to the E2K7-PostSP1 folder, and then double-click E2K7-postsp1.bat.
   
4. Click Yes if any Digital Signature not Found dialog boxes open.
   

   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 then restart the server.
   
6. Repeat steps 1 through 5 on the passive node.
   

1. Connect to the server through Remote Desktop, and then use an account that has local administrative access to log on.
   
2. Follow the procedures from the Exchange 2007 Online Help topic How to Configure the DNS TTL Value for a Clustered Mailbox Server Network Name Resource.
   

Use the following table to obtain the information that is needed for the commands.

Important:
The values in the following table are sample values and are not recommended. Update these values to reflect the actual values for your organization.

First storage group information

1. Connect to the server through Remote Desktop, and then log on by using an account that has local administrative access and that has been delegated the Exchange Server Administrator role (or higher).
   
2. Click Start, click All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell.
   
3. In Exchange Management Shell, run the following command to suspend replication, where <CMSName> is the name of the clustered Mailbox server:
   
   Suspend-StorageGroupCopy "<CMSName>\First Storage Group"

4. Run the following command to unmount the database, where <CMSName> is the name of the clustered mailbox server:
   
   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:
   
   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:
   
   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:
   
   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:
   
   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 files) to their new locations on both the active node and the passive node.
   
10. To mount the database, run the following command:
    
    Mount-Database "<CMSName>\<New SG Name>\<New DB Name>" -DomainController <DCName>

11. To restart replication, run the following command:
    
    Resume-StorageGroupCopy "<CMSName>\<New SG Name>"

1. Connect to the server through Remote Desktop, and then log on by using an account that has local administrative access and that is delegated the Exchange Organization Administrator role.
   
2. Follow the procedure that is 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 then use an account that has local administrative access to log on.
   
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 2007 optimizes the server’s memory management for programs. Follow these steps to configure 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 then use an account that has local administrative access to log on.
   
2. Click Start, right-click Computer, and then click Properties.
   
3. Click Advanced system settings.
   
4. On the Advanced tab, under Performance, click Settings.
   
5. On the Advanced tab, verify that the Processor scheduling is set to Background services.
   
6. Verify that the Memory Usage is set to System Cache.
   
7. Click OK.
   
8. 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 AutoDatabaseMountDial attribute has the following three possible values: Lossless, Good Availability, and Best Availability.

• Lossless
  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 the logs that can be accessed, and they must not be corrupted. After the failure, the passive node is made active, and the Information Store is brought online. It checks whether the databases can be mounted without any data loss. If they can, the databases are mounted. If the databases cannot be mounted without any data loss, the system periodically tries to copy the logs. If the server returns and its logs are intact, the databases will mount. If the server returns and its logs are not intact, the remaining logs will not be available, and the affected databases will not mount.
  
• Good Availability
  When the attribute is set to Good Availability, full automatic recovery is provided when replication is operating correctly and it is replicating logs at the rate that they are being generated.
  
• Best Availability
  By default, the value is set to Best Availability. Best Availability operates similarly to Good Availability. However, it enables automatic recovery when the replication experiences slightly more latency. Therefore, the new active node might be slightly further behind the state of the old active node after the failover. This increases the possibility that database divergence occurs, and requires a full re-seed to correct.
  Note   By default, CCR is configured to use Best Availability. Typically, this setting should not be changed. Therefore, this section may be skipped.
  

Several of the diagnostics tasks that are 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 then log on by using an account that has local administrative access and that is delegated the Exchange Server Administrator role (or higher).
   
2. Click Start, click All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell.
   
3. In Exchange Management Shell, change the directory path to <Exchange Server Install Path>\Scripts.
   
4. Type New-TestCasConnectivityUser.ps1, and then press ENTER.
   
5. Enter a temporary password, and then follow the prompts to create the test mailboxes.
   

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 then log on by using an account that has local administrative access and that is delegated the Exchange Server Administrator role (or higher).
   
2. Click Start, click All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell.
   
3. To enable the managed folder assistant, run the following command in the Exchange Management Shell, where <ServerName> is the name of the mailbox server and <DCName> is the name of a domain controller:
   
   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 topic to obtain the information that you must have to run 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 then log on by using an account that has local administrative access and that was delegated the Exchange Server Administrator role (or higher).
   
2. Click Start, click All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell.
   
3. To configure message tracking settings, run the following command in the Exchange Management Shell, where <ServerName> is the name of the Mailbox server and <DCName> is the name of a domain controller:
   
   Set-MailboxServer <ServerName> -MessageTrackingLogPath <LogPath> -MessageTrackingLogMaxAge <MaxAge> -MessageTrackingLogMaxDirectorySize <LogDirSize> -MessageTrackingLogMaxFileSize <LogFileSize> -MessageTrackingLogSubjectLoggingEnabled <SubjectLogEnabled> -DomainController <DCName>

Note:
Use the appropriate table from the Server Configuration Appendix at the end of this topic to obtain the information that you must have to run the commands.

1. Connect to an Exchange 2007 server through Remote Desktop, and then log on by using an account that has local administrative access and that is delegated the Exchange Server Administrator role (or higher).
   
2. Click Start, click All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell.
   
3. Use the appropriate table from the Database / Log LUN Appendix and Database Configuration Appendix at the end of this topic to obtain the information that you must have to run the commands.
   
4. To create the Storage Group, run the following command in the Exchange Management Shell, where <CMSName> is the name of the clustered mailbox server and <DCName> is the name of a domain controller:
   
   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:
   
   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:
   
   Mount-Database "<CMSName>\<SG>\<Database Name>" -DomainController <DCName>

7. Repeat steps 3 through 6 for each database that must be created.
   

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

Important:
The values in the following table are sample values, not recommended values. Update these values to reflect the actual values for your organization.

Records management configuration

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

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

Message tracking configuration

When you use continuous replication, you do not have to perform daily full backups because the storage group copy provides the first line of defense against corruption and data loss. Therefore, there are two approaches 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 rest.
  
• Use Volume Shadow Copy Service (VSS) to perform backups.
  

Because of the backup methodology selected, the LUN layout has to be altered.

When you use streaming backups, we recommend that you separate streaming I/O (source and target) so that multiple storage groups that are 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 that is unique to each hardware solution. You may have to isolate some storage groups from one another to maximize the number of concurrent backup operations, to increase throughput, and 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 one another. The backup jobs should complete on the first storage group on each LUN before the second storage group begins the back up process, 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 adding all 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 benefits of this strategy include the following:

• Simplified storage administration and fewer LUNs to manage.
  
• A potential reduction in the number of backup jobs.
  

Some concerns with this strategy include the following:

• It limits the ability to take hardware-based VSS backup and restores.
  
• The 2-terabyte limit on a master boot record (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

The Volume Shadow Copy Service (VSS) in Windows Server 2008 is used by applications to back up and restore Exchange 2007. VSS provides an infrastructure that enables third-party storage management programs, business programs, and hardware providers to cooperate in creating and managing shadow copies. Solutions based on this infrastructure can use shadow, or mirrored, copies to back up and restore one or more Exchange 2007 databases.

VSS coordinates communication between Requestors (backup applications), Writers (applications in Windows, such as Exchange 2007), and Providers (system components, software components, or hardware components that create the shadow copies). To use VSS to back up Exchange 2007, a backup program must include an Exchange 2007-aware VSS Requestor. The Windows Server Backup program that is part of Windows Server 2008 does not include an Exchange -aware VSS Requestor. Therefore, you must use a third-party backup program to back up Exchange 2007 on a Windows Server 2008-based computer.

Note:
The Windows Server Backup program also does not support the Exchange 2007 Extensible Storage Engine streaming APIs. Therefore, you cannot use Windows Server Backup to back up Exchange 2007.

For more information about VSS and Exchange 2007, see the Exchange Online Help topic Exchange 2007 Data Backup and Volume Shadow Copy Services.

When you use continuous replication, Exchange 2007 can run a software VSS snapshot not just on the active copy but also on the passive copy. Taking a VSS snapshot on the passive copy offloads the disk I/O from the active LUN during both the checksum integrity (ESEUTIL) and during the subsequent copy to tape or disk. This feature 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 on 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 put each storage group on its own transaction log LUN and database LUN. Because doing this will exceed the number of available drive letters, you must use volume mount points.

Some benefits of this strategy include the following:

• 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 concerns with this strategy include the following:

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

Note:
In the following table, MP represents Mount Point.

VSS approach LUN design

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

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

Database configuration