Administrator's Guide

Shell, or additional addresses can be added later using the Set-AvailabilityGroup
PowerShell command.
• Witness server name. See http://technet.microsoft.com/en-us/library/dd351107.aspx
for information about special considerations if placing the suggested default witness server
on a domain controller.
• Witness directory. Specify the local path on the witness server.
• Name prefix. Use the suggested default name or enter a new name. The E5000 Exchange
Deployment Tool appends numbers to the name and verifies that the name is unique at
the organization level (an Exchange 2010 requirement).
• Client Access Server (CAS) is Internet facing. For more information, see http://
technet.microsoft.com/en-us/library/dd351198.aspx .
• New or Existing CAS array. If a new array, enter a name or select from the dropdown
list for existing arrays (if detected).
• Enter the name of your load-balanced CAS array that is set on the database property. If
no load-balanced CAS array is available, see:
◦ http://go.microsoft.com/?linkid=9738617
◦ http://go.microsoft.com/?linkid=9738618
• Enable Error Reporting. For more information, see http://go.microsoft.com/?
linkid=9738619.
• Create Public Folder database. To connect to Exchange 2010 Microsoft Entourage or
Outlook 2003, clients require a public folder database. The E5000 Exchange Deployment
Tool runs Exchange setup to create the public folder database for you. This option is
available only on the first Exchange 2010 Mailbox server being deployed. The public
folders on this system are designed primarily for Free-Busy usage and not large-scale
folder replicas or other applications. The database is created in
h:\ExchangeDatabases\PF\Exch2010PublicFolder.edb.
• Exchange 2003 bridgehead server. Use the parameter to specify an Exchange 2003
bridgehead server that is located in the routing group to which you plan to create the
initial routing group connector. A routing group connector is required for mail flow
between Exchange 2010 and Exchange 2003 when these Exchange server versions
coexist in the same organization.
• Customer Experience Improvement Program. See http://go.microsoft.com/?
linkid=9738620.
6. Click Deploy to start the tools deployment process. This process typically requires about 1
hour and 30 minutes.
The E5000 Exchange Deployment Tool displays the Deployment Status window (Figure 19
(page 31)).
30 Configuring the messaging system software