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 Mailbox server 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.

In addition, the operator should review the Planning for Mailbox Servers topic in the Exchange 2007 Online Help before they implement the server role.

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.

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

1. Log on to the server with an account that has at least local administrative access.
   
   
2. Click Start, Control Panel and right-click Network Connections. Then select Open.
   
   
3. Locate the connection for the internal network and rename it appropriately.
   
   
4. For the TCP/IP Protocol, add the following:
   
   
   1. Static IP Address, Subnet Mask, and Gateway
      
      
   2. DNS Server IP Addresses
      
      
   3. Check the box to Append parent suffixes of the primary DNS suffix
      
      
   4. WINS IP Addresses (if using WINS)
      
      

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.
   
   

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.
    
    For more information about 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
      
      
    • 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 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).
    
    

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 Mailbox Servers.

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 type:
   
   

   	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.
   
   

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

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.

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.
   
   

Though this document uses the command line method for installing the Exchange roles, the GUI can also be used. For more information about how to use the setup GUI to install an Exchange role, see the Exchange 2007 Online Help topic How to Perform a Custom Installation Using Exchange 2007.

Important:
If this is the first Mailbox server role being installed into a green-field Exchange 2007 organization, then you should specify the optional setup parameter /EnableLegacyOutlook if you will have client computers that are running Microsoft Office Outlook 2003 or earlier.

1. Connect to the 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) if the server was pre-created.
   
   
2. Follow the procedure from the Exchange 2007 Online Help topic How to Install Exchange 2007 in Unattended Mode. For example, setup.com /r:MB /t:d:\exchsrvr.
   
   

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.
   
   

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 mentioned 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, and then follow the instructions that are mentioned in the Adobe document Configuring PDF iFilter for MS Exchange Server 2007.
   
   

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

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.
   
   

1. Connect to the 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.
   
   

   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.

   First storage group information

   	Old	New example
   Storage Group Name	First Storage Group	SG1
   Database Name	Mailbox Database	<ServerName> MBX Store 1
   Storage Group Path	%Program Files%\Microsoft\Exchange Server\Mailbox\First Storage Group	L:\LOG01
   Database Path	%Program Files%\Microsoft\Exchange Server\Mailbox\First Storage Group	E:\MDB01
   Database Filename	Mailbox database.edb	Priv01.edb
   Copy Database Path	--	F:\COPYMDB01
   Copy Transaction Log Path	--	M:\COPYLOG01

3. To dismount the database, run the following command where <ServerName> is the name of the mailbox server:
   
   

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

4. 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 "<ServerName>\<Old SG Name>" -Name <New SG Name> -DomainController <DCName>

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

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

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

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

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

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

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

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

9. If local continuous replication (LCR) is required, run the following command to enable LCR for the database:
   
   

   	Copy Code
   Enable-DatabaseCopy "<ServerName>\<New SG Name>\<New DB Name>" -CopyEDBFilePath:<FullPathIncludingDatabaseFileName> -DomainController <DCName>

10. If LCR is required, run the following command to enable LCR for the storage group:
    
    

    	Copy Code
    Enable-StorageGroupCopy "<ServerName>\<New SG Name>" -CopyLogFolderPath:<FullPath> -CopySystemFolderPath:<FullPath> -DomainController <DCName>

If a public folder store was created during the installation of the Mailbox server role, then the public folder still will be placed in the Second Storage Group. If there is no Second Storage Group, this section can be skipped.

1. Connect to the 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.
   
   

   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.

   Second storage group information

   	Old	New example
   Storage Group Name	Second Storage Group	SG2
   Database Name	Public Folder Database	<ServerName> PUB Store 2
   Storage Group Path	%Program Files%\Microsoft\Exchange Server\Mailbox\Second Storage Group	L:\LOG02
   Database Path	%Program Files%\Microsoft\Exchange Server\Mailbox\Second Storage Group	E:\MDB02
   Database Filename	Public Folder database.edb	Pub02.edb

3. To unmount the database, run the following command where <ServerName> is the name of the mailbox server:
   
   

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

4. To change the Storage Group name from “Second Storage Group” to “SG2”, run the following command where <DCName> is the name of a domain controller:
   
   

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

5. To change the public folder database name from “Public Folder Database” to “<ServerName> PUB Store 2”, run the following command:
   
   

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

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

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

7. To change the location of the public folder database, run the following command:
   
   

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

8. To mount the database run the following command:
   
   

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

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 document for information that you need for the commands.

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. Use the appropriate table from Database / Log LUN Appendix and Database Configuration Appendix at the end of this document for information that you need for the commands.
   
   
4. To create the Storage Group, run one of the following commands as appropriate for your environment, where <ServerName> is the name of the mailbox server and <DCName> is the name of a domain controller:
   
   
   1. To create a storage group that does not use LCR, run the following command:
      
      

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

   1. To create a storage group using LCR, run the following command:
      
      

   	Copy Code
   New-StorageGroup -Server <ServerName> -Name <SG> -LogFolderPath <Transaction Log Location> -SystemFolderPath <Transaction Log Location> -DomainController <DCName> -HasLocalCopy:$true -CopyLogFolderPath <PathforLCRLogFiles> -CopySystemFolderPath <PathforLCRSystemFiles>

5. To create the database that resides within the storage group, run one of the following commands as appropriate for your environment:
   
   
   1. To create the database for use without LCR, run the following command:
      
      

   Copy Code

   New-MailboxDatabase -StorageGroup "<ServerName>\<SG Name>" -Name "<DB Name>" -DomainController <DCName> -EdbFilePath:<FullPathIncludingDatabaseFileName> -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>

   1. To create the database for use with LCR, run the following command:
      
      

   Copy Code

   New-MailboxDatabase -StorageGroup "<ServerName>\<SG Name>" -Name "<DB Name>" -DomainController <DCName> -HasLocalCopy:$true -EdbFilePath:<FullPathIncludingDatabaseFileName> -CopyEdbFilePath:<FullPathIncludingDatabaseFileName> -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>

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

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

7. Repeat steps 5a or 5b 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.

Records management configuration

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.

Message tracking configuration

With continuous replication, you do not have to perform daily full backups as 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.
  
  

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

Exchange 2007 uses VSS included in Windows Server 2003 to take volume shadow copies of Exchange 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 2007 when you use continuous replication is the ability to run a software VSS snapshot not only on the active copy, but on the passive copy also. 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 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 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 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:

• 50 storage groups using continuous replication could require 200 LUNs which would exceed some storage array maximums. Cluster continuous replication (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 increasing the administrative costs and complexity.
  
  

  Note:
  In the following table, the reference to MP stands for Mount Point. SG2 may contain either a mailbox database or a public folder database, depending on the configuration.

VSS approach LUN design

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.

Database configuration