Contents

Confirm prerequisites are met for new install of Exchange 2010 .................................................. 3 Install the Exchange 2010 Client Access server role .................................................................... 4 Configure OAB and Web Services virtual directories.................................................................... 8 Configure settings on virtual directories ....................................................................................... 8 Install the Hub Transport server role .......................................................................................... 10 Install the Mailbox server role .................................................................................................... 14 Post-installation tasks ................................................................................................................ 17 Checklist complete .................................................................................................................... 19

Confirm prerequisites are met for new install of Exchange 2010

Before you go any further with the Exchange Deployment Assistant, make sure that your organization's operating system, hardware, software, clients, and other elements meet the requirements for Exchange 2010. If they don't, you won't be able to complete the steps in the Deployment Assistant and you won't be able to deploy Exchange 2010. Learn more at: Understanding Exchange 2010 Install Prerequisites To successfully install Exchange 2010, the following components are required.

Directory Servers
Schema master The 32-bit or 64-bit edition of the Windows Server 2003 SP1 Standard or Enterprise operating system or later, or the 32-bit or 64-bit edition of the Windows Server 2008 Standard or Enterprise operating system or later, or the Windows Server 2008 R2 Standard or Enterprise operating system. Global catalog server In every Active Directory site where you plan to install Exchange 2010, you must have at least one global catalog server that is either the 32-bit or 64-bit edition of Windows Server 2003 SP1 Standard or Enterprise or later, or the 32-bit or 64-bit edition of Windows Server 2008 Standard or Enterprise, or the Windows Server 2008 R2 Standard or Enterprise. Active Directory Forest The Active Directory forest must be Windows Server 2003 forest functional mode. Domain Controller You must have the 32-bit or 64-bit Windows Server 2003 Standard Edition or Enterprise Edition SP1 operating system, or the 32-bit or 64-bit edition of the Windows Server 2008 Standard or Enterprise RTM or later operating system or the Windows Server 2008 R2 Standard or Enterprise RTM or later operating system.

Operating Systems
64-bit edition of Windows Server 2008 Standard Service Pack 2 64-bit edition of Windows Server 2008 Enterprise Service Pack 2 64-bit edition of Windows Server 2008 Standard R2 64-bit edition of Windows Server 2008 Enterprise R2

Operating System Components

.NET Framework 3.5 SP1 Internet Information Services (IIS)

Windows Management Framework

Windows PowerShell V2.0 Windows Remote Management V2.0

Install the Exchange 2010 Client Access server role

Estimated time to complete: 45 minutes The Client Access role is one of five server roles in Exchange 2010. It's also the first server role that must be installed. The Client Access role enables access to mailbox data through a variety of clients, such as Microsoft Office Outlook, Outlook Anywhere, Outlook Web App, POP3, and IMAP4, and it also hosts Exchange Web services, such as the Autodiscover service and the Availability service. Learn more at: Understanding the Client Access Server Role We recommend installing the latest update rollup for Exchange 2010 on all your servers. Although you can install update rollups on a server after Exchange 2010 has been installed, it's also possible and less time-consuming to incorporate the update rollup into the install server installation process. To do this, copy the contents of the Exchange 2010 DVD to the file system, and then copy or move the downloaded update rollup file to the Updates folder in the installation tree. When you perform the procedure below, the update rollup will be installed as part of the initial installation process. To download the latest update rollup for Exchange 2010, visit: Microsoft Download Center Important: When you upgrade your organization to the RTM version of Exchange 2010, your clients running Outlook 2003 dont use RPC encryption, and RPC Client Access requires it by default. This can cause connection issues between Exchange 2010 and Outlook 2003. In Exchange 2010 SP1, RPC Client Access doesn't require RPC encryption by default. If you have Outlook 2003 clients within your organization, we recommend that you install Exchange 2010 SP1 to avoid connection issues between Exchange 2010 SP1 and Outlook 2003. For more information, see Understanding RPC Client Access.

How do I do this?
You'll use the Exchange Server 2010 Setup wizard to install the Client Access role. Important: When you install the first Exchange 2010 server role, Exchange 2010 prepares your Windows schema and forest before the installing the server role. The amount of time that forest preparation and replication takes depends on your Active Directory site topology.

1. Insert the Exchange 2010 DVD into the DVD drive. When the AutoPlay dialog appears, click Run Setup.exe under Install or run program. If the AutoPlay dialog doesn't appear, navigate to the root of the DVD and double-click Setup.exe. Alternatively, browse to the location of your Exchange 2010 installation files and double-click Setup.exe. 2. TheExchange Server 2010 Setup welcome screen appears. In the Install section, the software listed for Step 1: Install .NET Framework 3.5 SP1 and Step 2: Install Windows PowerShell v2 was installed with the Exchange 2010 prerequisites. However, if these prerequisites aren't already installed, click the appropriate step to install them. 3. When Steps 1 and 2 are listed as Installed, click Step 3: Choose Exchange language option to expand the Exchange language options, and then choose the appropriate option: a. Install all languages from the language bundle This option installs all the Exchange 2010 languages from an Exchange 2010 language bundle. You can connect to the Internet to download the latest applicable language bundle or to use a previously downloaded language bundle on a local drive or network share. Internet connectivity is required for Exchange Setup to download the language pack bundle. b. Install only languages from the DVD This option installs only the languages included with the Setup DVD. The installation of additional languages support requires installing the languages from the language bundle. 4. After Step 3 is complete, click Step 4: Install Microsoft Exchange. Note: After your installation is complete, you can return to Step 5: Get critical updates for Microsoft Exchange. 5. On the Introduction page, click Next. 6. On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement, and click Next. 7. On the Error Reporting page, select Yes or No to enable the Exchange Error Reporting feature, and click Next. 8. On the Installation Type page, select Custom Exchange Server Installation. You can select to automatically install all required Windows roles and features for this server. To optionally change the installation path for Exchange 2010, click Browse, locate the appropriate folder in the folder tree, and then click OK. Click Next. 9. On the Server Role Selection page, select the Client Access Role, and click Next. The Management Tools option, which installs the Exchange Management Console and the Exchange Management Shell, will also be selected and installed.

10. Use the Configure Client Access Serverexternal domain page to configure an external fully-qualified domain name (FQDN). This is the FQDN that you give to Microsoft Office Outlook Web App, Outlook Anywhere, and Exchange ActiveSync users to connect to Exchange 2010. Select the check box, enter your FQDN, and then click Next. 11. On the Customer Experience Improvement Program page, optionally join in the Exchange Customer Experience Improvement Program (CEIP). The CEIP collects anonymous information about how you use Exchange 2010 and any problems that you encounter. To join the CEIP, select Join the Customer Experience Improvement Program, choose the industry that best represents your organization, and then click Next. 12. On the Readiness Checks page, review the Summary to determine if the system and server are ready for the Client Access role to be installed. If all prerequisite checks completed successfully, click Install. If any of the prerequisite checks failed, you must resolve the displayed error before you can proceed with installing the Client Access role. In many cases, you don't need to exit Setup while you're fixing issues. After you resolve an error, click Retry to run the prerequisite check again. Also, be sure to review any warnings that are reported.

13. The Progress page displays the progress and elapsed time for each phase of the installation. As each phase ends, it's marked completed and the next phase proceeds. If any errors are encountered, the phase will end as incomplete and unsuccessful. If that happens, you must exit Setup, resolve any errors, and then restart Setup. 14. When all phases have finished, the Completion page displays. Review the results, and verify that each phase completed successfully. Clear the check box for Finalize this installation using the Exchange Management Console, and then click Finish to exit Setup. 15. When you're returned to the Setup welcome screen, click Close. On the Confirm Exit prompt, click Yes. 16. Restart the computer to complete the installation of the Client Access role.

Create a Client Access Server Array

If you're installing multiple Client Access servers in one Active Directory site, you can create a Client Access server array. This is a load-balanced group of Client Access server computers that can be accessed through a single URL. Creating a Client Access array reduces the number of fully qualified domain names (FQDN) you need to have on your certificate, and it allows all users in one Active Directory site to access Exchange 2010 through a single URL. After you've completed the installation of your first Client Access server computer, you can start building your Client Access server array. To create a new Client Access server array, run the following command using the Exchange Management Shell. New-ClientAccessArray -FQDN ClientArray.contoso.com -Site "YourSite" Name "clientarray.contoso.com" There can only be one Client Access array per Active Directory site. After you've created the array, you can manage which Client Access server computers are part of the array through your load balancer configuration. If you're unfamiliar with the Shell, learn more at: Overview of Exchange Management Shell

How do I know this worked?

The successful completion of the Exchange Setup wizard will be your first indication that the installation process worked as expected. To further verify that the Client Access server role installed successfully, you can run Get-ExchangeServer <server name> in the Exchange Management Shell, which can be launched from the Exchange Server 2010 program group on the Windows Start menu. This cmdlet outputs a list of the Exchange 2010 server roles that are installed on the specified server. You can also check the Exchange setup log (ExchangeSetup.log), located in <system drive>\ExchangeSetupLogs to verify that the Client Access role was installed as expected. Learn more at: Verify an Exchange 2010 Installation

Configure OAB and Web Services virtual directories

Estimated time to complete: 10 minutes To enable Outlook Anywhere clients to discover and automatically connect to Exchange 2010, you must configure the offline address book (OAB) and Exchange Web Services virtual directories. This step is only necessary if you'll be using Exchange Web Services, Outlook Anywhere, or the offline address book. If you haven't enabled Outlook Anywhere, and you don't plan on using Exchange Web Services for programmatic access to Exchange mailbox information, you can skip this step. Learn more at: Understanding Offline Address Books and Configure External Client Access Namespaces

How do I do this?
You must use the Exchange Management Shell to configure OAB and Exchange Web Services virtual directory settings. If you're unfamiliar with the Shell, learn more at: Overview of Exchange Management Shell 1. Configure the external URL for the offline address book using the following syntax. Set-OABVirtualDirectory -Identity "CAS01\OAB (Default Web Site)" ExternalUrl https://mail.contoso.com/OAB -RequireSSL:$true 2. Configure the external URL for Exchange Web Services using the following syntax. Set-WebServicesVirtualDirectory -Identity "CAS01\EWS (Default Web Site)" -ExternalUrl https://mail.contoso.com/EWS/Exchange.asmx BasicAuthentication:$True

How do I know this worked?

To verify that these steps were completed successfully, run the following commands to verify the ExternalURL property is set correctly on both virtual directories. Get-OABVirtualDirectory -Identity "CAS01\OAB (Default Web Site)" ExternalURL Get-WebServicesVirtualDirectory -Identity "CAS01\EWS (Default Web Site)"

Configure settings on virtual directories

Estimated time to complete: 15 minutes

During the installation of the Client Access server role, virtual directories are created for the Autodiscover service, Exchange ActiveSync, Outlook Web App, the Exchange Control Panel, PowerShell, Exchange Web Services, and public folders. Legacy virtual directories are also created for coexistence. You can configure a variety of settings on those virtual directories, including authentication and SSL. For Active Directory sites that are accessible from outside an external firewall such as Internet Security and Acceleration Server (ISA), you'll also need to configure publishing rules for the various virtual directories that are accessible from the Internet, including the Exchange ActiveSync virtual directory, the Autodiscover service virtual directory, and the Outlook Web App virtual directory. Learn more at: Understanding Virtual Directories

How do I do this?
Perform the following steps from the computer that has the Exchange 2010 Client Access server role installed. 1. In the Console tree, navigate to Server Configuration > Client Access. 2. In the Result pane, select the Client Access server you want to configure. 3. In the Work pane, click the tab that corresponds to the virtual directory whose settings you want to configure (Outlook Web App, Exchange Control Panel, Exchange ActiveSync), and then click the virtual directory. 4. In the Actions pane, under the virtual directory name, click Properties. 5. Edit any of the settings on the tabs. (If you need more information about the settings, click F1 while you're on a tab.) Common settings to be configured are: a. External URL This is the URL used to access the Web site from the Internet. The value for this URL should have been set during installation of the Client Access server role. b. Authentication You can specify a variety of authentication options, as well as specify the sign-in format and sign-in domain. c. Direct File Access For Outlook Web App, you can configure direct file access settings for public and private computers.

d. Private Computer File Access For Outlook Web App, you can configure direct file access settings for users who choose the private option when logging in. 6. Click OK to confirm your changes. Note: To configure publishing rules for external access to virtual directories, see: Configure External Client Access Namespaces 7. Configure the Exchange2003URL parameter This parameter is only necessary when you have users with mailboxes on Exchange 2003 at the same time as users with mailboxes on Exchange 2010. In that case, set this parameter to the legacy DNS endpoint, for example, http://legacy.contoso.com. This parameter can be set with the following code.

Set-OWAVirtualDirectory -Identity "CASServer\owa (Default Web Site)" -Exchange2003URL https://legacymail.contoso.com/exchange This parameter must be configured in the Exchange Management Shell. For more information about the Shell, see Overview of Exchange Management Shell

How do I know this worked?

How you confirm whether your settings were applied varies by the setting. To verify that the external URL has been configured correctly for Exchange ActiveSync or Outlook Web App, you can use the Exchange Remote Connectivity Analyzer (ExRCA), a free Web-based tool provided by Microsoft. You can find ExRCA at https://www.testexchangeconnectivity.com To verify that authentication has been configured correctly for Exchange ActiveSync or Outlook Web App, you can also use ExRCA. To verify that direct file access has been configured correctly for Outlook Web App, log on as a user to Outlook Web App using the public computer option and then try to access and save a file attached to an e-mail message.

Install the Hub Transport server role

Estimated time to complete: 20 minutes The Hub Transport server role is responsible for internal mail flow for the Exchange organization. It handles all mail flow inside the organization, applies transport rules, applies journaling policies, and delivers messages to recipient mailboxes. Learn more at: Overview of the Hub Transport Server Role You can install the Hub Transport server role on dedicated hardware, or you can install it on the same server where you installed the Client Access server role. We recommend installing the latest update rollup for Exchange 2010 on all your servers. Although you can install update rollups on a server after Exchange 2010 has been installed, it's also possible and less time-consuming to incorporate the update rollup into the install server installation process. To do this, copy the contents of the Exchange 2010 DVD to the file system, and then copy or move the downloaded update rollup file to the Updates folder in the installation tree. When you perform the procedure below, the update rollup will be installed as part of the initial installation process. To download the latest update rollup for Exchange 2010, visit: Microsoft Download Center

How do I install the Hub Transport server role on dedicated hardware?

The Exchange Server 2010 Setup wizard helps you install the Hub Transport role:

10

1. Insert the Exchange 2010 DVD into the DVD drive. When the AutoPlay dialog appears, click Run Setup.exe under Install or run program. If the AutoPlay dialog doesn't appear, navigate to the root of the DVD and double-click Setup.exe. Alternatively, browse to the location of your Exchange 2010 installation files and double-click Setup.exe. 2. TheExchange Server 2010 Setup welcome screen appears. In the Install section, the software listed for Step 1: Install .NET Framework 3.5 SP1 and Step 2: Install Windows PowerShell v2 was installed with the Exchange 2010 prerequisites. If these prerequisites are not already installed, click on the appropriate step to install them. 3. When Step 1 and Step 2 are listed as Installed, click Step 3: Choose Exchange language option to expand the Exchange language options, and then choose the appropriate option: a. Install all languages from the language bundle This option installs all the Exchange 2010 languages from an Exchange 2010 language bundle. You can connect to the Internet to download the latest applicable language bundle or to use a previously downloaded language bundle on a local drive or network share. Internet connectivity is required for Exchange Setup to download the language pack bundle. b. Install only languages from the DVD This option installs only the languages included with the Setup DVD. The installation of additional languages support requires installing the languages from the language bundle. 4. After Step 3 is complete, click Step 4: Install Microsoft Exchange. Note: After your installation is complete, you can return to Step 5: Get critical updates for Microsoft Exchange. 5. On the Introduction page, click Next. 6. On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement, and click Next. 7. On the Error Reporting page, select Yes or No to enable the Exchange Error Reporting feature, and click Next. 8. On the Installation Type page, select Custom Exchange Server Installation. For Exchange 2010 SP1, you can select to automatically install all required Windows roles and features for this server. To optionally change the installation path for Exchange 2010, click Browse, locate the appropriate folder in the folder tree, and then click OK. Click Next. 9. On the Server Role Selection page, select the Hub Transport Role, and click Next. The Management Tools option, which installs the Exchange Management Console and the Exchange Management Shell, will also be selected and installed.

11

10. On the Readiness Checks page, review the Summary to determine if the system and server are ready for the Hub Transport role to be installed. If all prerequisite checks completed successfully, click Install. If any of the prerequisite checks failed, you must resolve the displayed error before you can proceed with installing the Hub Transport role. In many cases, you don't need to exit Setup while you're fixing issues. After you resolve an error, click Retry to run the prerequisite check again. Also, be sure to review any warnings that are reported. 11. The Progress page displays the progress and elapsed time for each phase of the installation. As each phase ends, it's marked completed and the next phase proceeds. If any errors are encountered, the phase will end as incomplete and unsuccessful. If that happens, you must exit Setup, resolve any errors, and then restart Setup. 12. When all phases have finished, the Completion page displays. Review the results, and verify that each phase completed successfully. Clear the check box for Finalize this installation using the Exchange Management Console, and then click Finish to exit Setup. 13. When you're returned to the Setup welcome screen, click Close. On the Confirm Exit prompt, click Yes. 14. Restart the computer to complete the installation of the Hub Transport role.

12

How do I add the Hub Transport server role to my Client Access server?
You can also use the Exchange Server 2010 Setup wizard to add the Hub Transport role to your existing Client Access server. 1. In Control Panel, start Programs and Features. 2. Select Microsoft Exchange Server 2010 from the list of installed programs, and then click Change. 3. The Exchange Server 2010 Setup wizard starts in Exchange Maintenance Mode. Click Next. 4. On the Server Role Selection page, select the check box for Hub Transport Role and then click Next. 5. On the Readiness Checks page, review the Summary to determine if the system and server are ready for the Hub Transport role to be installed. If all prerequisite checks completed successfully, click Install. If any of the prerequisite checks failed, you must resolve the displayed error before you can proceed with installing the Hub Transport role. In many cases, you don't need to exit Setup while you're fixing issues. After you resolve an error, click Retry to run the prerequisite check again. Also, be sure to review any warnings that are reported. 6. The Progress page will display the progress and elapsed time for each phase of the installation. As each phase ends, it will be marked completed and the next phase will proceed. If any errors are encountered, the phase will end as incomplete and unsuccessful. In this event, you must exit Setup, resolve any errors, and then restart Setup in Maintenance Mode. 7. When all phases have finished, the Completion page will be displayed. Review the results and verify that each phase completed successfully. Click Finish to exit Setup. 8. Restart the computer to complete the installation of the Hub Transport role.

How do I know this worked?

The successful completion of the Exchange Setup wizard will be your first indication that the installation process worked as expected. To further verify that the Hub Transport server role installed successfully, you can run Get-ExchangeServer <server name> in the Exchange Management Shell, which can be launched from the Exchange Server 2010 program group on the Windows Start Menu. This cmdlet outputs a list of the Exchange 2010 server roles that are installed on the specified server. You can also review the contents of the Exchange setup log file (ExchangeSetup.log), located in <system drive>\ExchangeSetupLogs to verify that the Hub Transport role was installed as expected. Learn more at: Verify an Exchange 2010 Installation

13

Install the Mailbox server role

Estimated time to complete: 20 minutes The Mailbox server role hosts mailbox and public folder databases, and it generates the offline address book (OAB). Mailbox servers also provide services that enforce e-mail address policies and managed folders. Learn more at: Overview of the Mailbox Server Role You can install the Mailbox server role on dedicated hardware, or you can install it on a server that is already running Exchange 2010. We recommend installing the latest update rollup for Exchange 2010 on all your servers. Although you can install update rollups on a server after Exchange 2010 has been installed, it's also possible and less time-consuming to incorporate the update rollup into the install server installation process. To do this, copy the contents of the Exchange 2010 DVD to the file system, and then copy or move the downloaded update rollup file to the Updates folder in the installation tree. When you perform the procedure below, the update rollup will be installed as part of the initial installation process. To download the latest update rollup for Exchange 2010, visit: Microsoft Download Center

How do I install the Mailbox server role on dedicated hardware?

The Exchange Server 2010 Setup wizard helps you install the Mailbox role. 1. Insert the Exchange Server 2010 DVD into the DVD drive. When the AutoPlay dialog appears, click Run Setup.exe under Install or run program. If the AutoPlay dialog doesn't appear, navigate to the root of the DVD and double-click Setup.exe. Alternatively, browse to the location of your Exchange 2010 installation files and double-click Setup.exe. 2. TheExchange Server 2010 Setup welcome screen appears. In the Install section, the software listed for Step 1: Install .NET Framework 3.5 SP1 and Step 2: Install Windows PowerShell v2 was installed with the Exchange 2010 prerequisites. If these prerequisites are not already installed, click the appropriate step to install them. 3. When Step1 and Step2 are listed as Installed, click Step 3: Choose Exchange language option to expand the Exchange language options, and then choose the appropriate option: a. Install all languages from the language bundle This option installs all the Exchange 2010 languages from an Exchange 2010 language bundle. You can connect to the Internet to download the latest applicable language bundle or to use a previously downloaded language bundle on a local drive or network share. Internet connectivity is required for Exchange Setup to download the language pack bundle. b. Install only languages from the DVD This option installs only the languages included with the Setup DVD. The installation of additional languages support requires installing the languages from the language bundle. 4. After Step 3 is complete, click Step 4: Install Microsoft Exchange.

14

Note: After your installation is complete, you can return to Step 5: Get critical updates for Microsoft Exchange. 5. On the Introduction page, click Next. 6. On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement, and click Next. 7. On the Error Reporting page, select Yes or No to enable the Exchange Error Reporting feature, and click Next. 8. On the Installation Type page, select Custom Exchange Server Installation. For Exchange 2010 SP1, you can select to automatically install all required Windows roles and features for this server. To optionally change the installation path for Exchange 2010, click Browse, locate the appropriate folder in the folder tree, and then click OK. Click Next. 9. On the Server Role Selection page, select the Mailbox Role, and click Next. The Management Tools option, which installs the Exchange Management Console and the Exchange Management Shell, will also be selected and installed.

10. On the Client Settings page, select Yes if your organization has client computers running either Microsoft Outlook 2003 or Microsoft Entourage 2004 or earlier. Select No if you don't. 11. On the Readiness Checks page, review the Summary to determine if the system and server are ready for the Mailbox role to be installed. If all prerequisite checks completed successfully, click Install. If any of the prerequisite checks failed, you must resolve the

15

displayed error before you can proceed with installing the Mailbox role. In many cases, you don't need to exit Setup while you're fixing issues. After you resolve an error, click Retry to run the prerequisite check again. Also, be sure to review any warnings that are reported. 12. The Progress page displays the progress and elapsed time for each phase of the installation. As each phase ends, it's marked completed and the next phase proceeds. If any errors are encountered, the phase will end as incomplete and unsuccessful. If that happens, you must exit Setup, resolve any errors, and then restart Setup. 13. When all phases have finished, the Completion page displays. Review the results, and verify that each phase completed successfully. Clear the check box for Finalize this installation using the Exchange Management Console, and then click Finish to exit Setup. 14. When you are returned to the Setup welcome screen, click Close. On the Confirm Exit prompt, click Yes. 15. Restart the computer to complete the installation of the Mailbox role.

How do I add the Mailbox server role to an existing Exchange 2010 server?
You can also use the Exchange Server 2010 Setup wizard to add the Mailbox role to an existing Exchange 2010 server. 1. In Control Panel, start Programs and Features. 2. Select Microsoft Exchange Server 2010 from the list of installed programs, and then click Change. 3. The Exchange Server 2010 Setup wizard starts in Exchange Maintenance Mode. Click Next. 4. On the Server Role Selection page, select the check box for Mailbox Role and then click Next. 5. On the Readiness Checks page, review the Summary to determine if the system and server are ready for the Mailbox role to be installed. If all prerequisite checks completed successfully, click Install. If any of the prerequisite checks failed, you must resolve the displayed error before you can proceed with installing the Mailbox role. In many cases, you don't need to exit Setup while you're fixing issues. After you resolve an error, click Retry to run the prerequisite check again. Also, be sure to review any warnings that are reported. 6. The Progress page will display the progress and elapsed time for each phase of the installation. As each phase ends, it will be marked completed and the next phase will proceed. If any errors are encountered, the phase will end as incomplete and unsuccessful. In this event, you must exit Setup, resolve any errors, and then restart Setup in Maintenance Mode. 7. When all phases have finished, the Completion page will be displayed. Review the results and verify that each phase completed successfully. Click Finish to exit Setup. 8. Restart the computer to complete the installation of the Mailbox role.

16

How do I know this worked?

The successful completion of the Exchange Setup wizard will be your first indication that the installation process worked as expected. To further verify that the Mailbox server role installed successfully, you can run Get-ExchangeServer <server name> in the Exchange Management Shell, which can be launched from the Exchange Server 2010 program group on the Windows Start Menu. This cmdlet outputs a list of the Exchange 2010 server roles that are installed on the specified server. You can also review the contents of the Exchange setup log file (ExchangeSetup.log), located in <system drive>\ExchangeSetupLogs to verify that the Mailbox role was installed as expected. Learn more at: Verify an Exchange 2010 Installation

Post-installation tasks
After you complete a new installation of Exchange 2010 or after you add an additional Exchange 2010 server role to an existing Exchange 2010 server, you should complete the post-installation tasks. The post-installation tasks will help you verify the installation and configure the components that you have just installed.

Tasks to complete on all server roles

For all server roles, we recommend that you verify the installation immediately after you install Exchange 2010. If you install the Hub Transport or Edge Transport server roles, you should also verify the agent configuration. For more information, see the following topics: Verify an Exchange 2010 Installation Enter Product Key Transport Server Post-Deployment Tasks Finalize Deployment Tasks End-to-End Scenario Tasks Additional Post-Installation Tasks

If you're upgrading from an Exchange 2003 or a mixed Exchange 2003 and Exchange 2007 organization, see: Upgrade Custom LDAP Filters to OPATH Filters

Optional tasks to complete on the Mailbox server role

After deploying and verifying the successful installation of at least two Mailbox servers, you can configure your Mailbox servers and mailbox databases for high availability and site resilience. Exchange 2010 uses the concept of incremental deployment, which is the ability to configure high availability and site resilience for Mailbox servers after the servers have been deployed. Service

17

and data redundancy is achieved by using new features in Exchange 2010 such as database availability groups and database copies. For more information about configuring your Mailbox servers for high availability or site resilience, see: Managing High Availability and Site Resilience

Optional tasks to complete on the Hub Transport server role

After deploying and verifying the installation of the Hub Transport server role, you might be interested in enabling anti-spam functionality on your Hub Transport server. In some small organizations, it may make sense to run Exchange 2010 anti-spam features on Hub Transport servers. For example, some organizations may not have enough e-mail volume to justify the cost of installing and maintaining a full perimeter network together with an Edge Transport server. Learn more at: Enable Anti-Spam Functionality on a Hub Transport Server

Optional tasks to complete on the Unified Messaging server role

After deploying and verifying the installation of your Unified Messaging (UM) server(s), you might be interested in integrating UM services with Microsoft Office Communications Server (OCS) 2007 R2. Exchange 2010 UM combines voice messaging and e-mail messaging into a single messaging infrastructure. Enterprise Voice in OCS 2007 R2 makes use of the UM infrastructure to provide call answering, subscriber access, call notification, and auto attendant services. Implementing these services requires integrating Exchange UM and OCS in a shared Active Directory topology, careful planning, and a clear understanding of the technologies involved, the features you want to enable, and important configuration details that you must be aware of to successfully complete your deployment. For more information about integrating UM with OCS, see: Enterprise Voice and Unified Communications

Permissions configuration
For the purposes of the Exchange Deployment Assistant, your administrator account was granted permissions that you might not need going forward. You should verify that this account doesn't have more permissions than required to configure and manage your Exchange 2010 environment. Role Based Access Control (RBAC), the new permissions model in Exchange 2010, is extremely flexible. The built-in role groups are probably sufficient to manage most of your Exchange 2010 organization. You can simply add and remove members from the existing role groups to control permissions. The following topics will provide more information and help you configure the appropriate permissions for your Exchange 2010 tasks: Understanding Permissions

18

Understanding Role Based Access Control Understanding Management Role Groups Understanding Management Role Scopes Built-in Role Groups Built-in Management Roles Understanding Permissions Coexistence with Exchange 2003

Remove legacy Exchange versions

After you have completed deploying Exchange 2010 into your organization, you may be ready to remove previous versions of Exchange. For more information about removing legacy Exchange servers, see the following topics: How to Uninstall Exchange Server 2003 How to remove Exchange Server 2003 from your computer How to Completely Remove Exchange 2007 from a Server

Checklist complete
Congratulations on successfully completing your checklist in the Exchange Deployment Assistant!

Tools you can use

To determine the overall health of your Exchange servers and topology, you can use the Microsoft Exchange Best Practices Analyzer (ExBPA). The tool scans Exchange servers and identifies items that don't conform to Microsoft best practices. After the data is collected, ExBPA compares what it finds on your system with Exchange best practice rules and then provides a detailed report. The report lists recommendations that you can consider to achieve greater performance, scalability, and uptime. You can find ExBPA in the Toolbox in the Exchange Management Console. The Exchange Remote Connectivity Analyzer Tool is a Web-based tool that helps you troubleshoot connectivity issues. The tool simulates several client logon and mail flow scenarios. When a test fails, many of the errors have troubleshooting tips to assist you in correcting the problem. Take a look at: Exchange Remote Connectivity Analyzer Tool And, for more information about Exchange planning and deployment, you can always review the related content in the Exchange TechCenter Library. Find it all at: Planning and Deployment

19

Give us feedback please

We would really appreciate your feedback about the Exchange Deployment Assistant. What worked for you? What could we have done better? What do you recommend we change for the next version? Tell us what you think at: Feedback: Exchange 2010 Deployment Assistant

20