Finalize Deployment Tasks

Article
06/29/2011

Getting Started with Outlook on the Web Use this checklist to help you perform tasks to finalize your deployment after you install Exchange Server 2010. The tasks in this topic are required to complete the deployment of your Exchange organization. The tasks apply to features that are enabled by default but require additional configuration.

For guidance about optional tasks that you may want to perform after installing Exchange 2010, see Additional Post-Installation Tasks and End-to-End Scenario Tasks,

All Server Roles

Done?	Task
	Enter the product key for Exchange 2010. For more information, see Enter Product Key. You can also enter the product key by using the Set-ExchangeServer cmdlet.
	We recommend that you protect your Exchange servers from viruses, worms, and other malicious software. For more information, see Forefront Protection 2010 for Exchange Server.
	To enable Exchange Search to index Microsoft Office 2007 file formats, you must register the installed IFilters for Exchange 2010 by modifying the registry. You must perform this step after you have installed Exchange 2010 on the server. For more information, see Register Filter Pack IFilters with Exchange 2010.
	In Microsoft Exchange Server 2003 and earlier versions, LDAP filtering syntax is used to create custom address lists, global address lists (GALs), e-mail address policies, and distribution groups. Using the OPATH filtering syntax allows you to create filters directly in Exchange Management Shell commands by using the -RecipientFilter parameter. For more information, see Upgrade Custom LDAP Filters to OPATH Filters.

Mailbox Server Role

Done?	Task
	Configure offline address book (OAB) distribution for Outlook clients. For more information, see Create an Offline Address Book and Configure Offline Address Book Properties.
	Configure high availability, backup, and disaster recovery. For more information, see High Availability and Site Resilience.

Client Access Server Role

Done?	Task
	Configure secure access for your Client Access server. For more information, see Understanding Client Access Security.
	Configure Microsoft Exchange ActiveSync. By default, when you install the Client Access server role on a computer that is running Exchange 2010, Exchange ActiveSync is enabled. However, we recommend that you configure security, authentication, and policy settings if you plan to use ActiveSync in your environment. For more information, see Managing Exchange ActiveSync.

Hub Transport Server Role

Done?	Task
	Configure domains for which you will accept e-mail messages. For more information, see Transport Server Post-Deployment Tasks.
	Configure Internet mail flow. By default, a Hub Transport server isn't configured for Internet mail flow. If you don't subscribe an Edge Transport server to your Exchange organization, you must use one of the following methods to configure Internet mail flow to and from your Exchange organization: Deploy an Edge Transport server and manually configure the Send connectors and Receive connectors that are required for Internet mail flow This method doesn't establish any replication of recipient and configuration information from Active Directory Domain Services to the Edge Transport server. For more information, see Configure Mail Flow Between an Edge Transport Server and Hub Transport Servers Without Using EdgeSync. Manually configure Internet mail flow between your Exchange 2010 organization and Microsoft Exchange Hosted Services or other external SMTP gateway servers This method requires you to create the Send connectors and Receive connectors on one or more Hub Transport servers in your organization that are assigned to communicate with Exchange Hosted Services or the external SMTP gateway servers. For more information see Configure Internet Mail Flow Through Exchange Hosted Services or an External SMTP Gateway. Configure the Hub Transport server for direct mail flow with the Internet This method requires you to create the Send connectors and Receive connectors on one or more Hub Transport servers in your organization that are assigned to connect to the Internet. For more information, see Configure Internet Mail Flow Through Exchange Hosted Services or an External SMTP Gateway.
	Configure an external postmaster recipient to receive e-mail messages. The external postmaster address is used as the sender for system-generated messages and notifications that are sent to message senders that exist outside the Exchange 2010 organization. According to RFC 2821, every domain must be able to receive mail that is sent to the postmaster address. By default, no mailbox or other recipient object is configured to receive messages that are sent to the postmaster address for any accepted domains that are defined in the Exchange organization. For more information, see Configure the External Postmaster Address.

Configure domains for which you will accept e-mail messages. For more information, see Transport Server Post-Deployment Tasks.

Configure Internet mail flow. By default, a Hub Transport server isn't configured for Internet mail flow. If you don't subscribe an Edge Transport server to your Exchange organization, you must use one of the following methods to configure Internet mail flow to and from your Exchange organization:

Deploy an Edge Transport server and manually configure the Send connectors and Receive connectors that are required for Internet mail flow
This method doesn't establish any replication of recipient and configuration information from Active Directory Domain Services to the Edge Transport server. For more information, see Configure Mail Flow Between an Edge Transport Server and Hub Transport Servers Without Using EdgeSync.
Manually configure Internet mail flow between your Exchange 2010 organization and Microsoft Exchange Hosted Services or other external SMTP gateway servers
This method requires you to create the Send connectors and Receive connectors on one or more Hub Transport servers in your organization that are assigned to communicate with Exchange Hosted Services or the external SMTP gateway servers. For more information see Configure Internet Mail Flow Through Exchange Hosted Services or an External SMTP Gateway.
Configure the Hub Transport server for direct mail flow with the Internet
This method requires you to create the Send connectors and Receive connectors on one or more Hub Transport servers in your organization that are assigned to connect to the Internet. For more information, see Configure Internet Mail Flow Through Exchange Hosted Services or an External SMTP Gateway.

Configure an external postmaster recipient to receive e-mail messages. The external postmaster address is used as the sender for system-generated messages and notifications that are sent to message senders that exist outside the Exchange 2010 organization. According to RFC 2821, every domain must be able to receive mail that is sent to the postmaster address. By default, no mailbox or other recipient object is configured to receive messages that are sent to the postmaster address for any accepted domains that are defined in the Exchange organization. For more information, see Configure the External Postmaster Address.

Unified Messaging Server Role

Done?	Task
	Configure Unified Messaging (UM). For more information see the following topics: Create a UM Dial Plan Create a UM IP Gateway Add a UM Server to a Dial Plan Enable a User for Unified Messaging Note These tasks are required to configure the first UM server in your organization, or the first UM server in a new dial plan. To configure an additional UM server for an existing dial plan, you only need to complete the steps in Add a UM Server to a Dial Plan.
	Configure UM and Office Communication Server integration. For more information, see the following topics: Checklist: Deploying Office Communications Server 2007 and Exchange Unified Messaging Enterprise Voice and Unified Communications

Configure Unified Messaging (UM). For more information see the following topics:

Note These tasks are required to configure the first UM server in your organization, or the first UM server in a new dial plan. To configure an additional UM server for an existing dial plan, you only need to complete the steps in Add a UM Server to a Dial Plan.

Configure UM and Office Communication Server integration. For more information, see the following topics:

Edge Transport Server Role

Done?	Task
	Subscribe the Edge Transport server. For more information, see Configure Internet Mail Flow Through a Subscribed Edge Transport Server. Note To subscribe the Edge Transport server manually instead of using the Edge Subscription process, see Configure Mail Flow Between an Edge Transport Server and Hub Transport Servers Without Using EdgeSync.
	Configure an external postmaster recipient to receive e-mail messages. The external postmaster address is used as the sender for system-generated messages and notifications that are sent to message senders that exist outside the Exchange 2010 organization. According to RFC 2821, every domain must be able to receive mail that is sent to the postmaster address. By default, no mailbox or other recipient object is configured to receive messages that are sent to the postmaster address for any accepted domains that are defined in the Exchange organization. If you haven't subscribed this Edge Transport server to your Exchange organization, the value of the external postmaster address is postmaster@[Edge Transport server FQDN]. After you subscribe the Edge Transport server to the Exchange organization, the value of the external postmaster address is postmaster@[default accepted domain]. If you specify a custom value for the external postmaster address on the Hub Transport servers in your Exchange organization, you must manually configure the external postmaster address on the Edge Transport server. For more information, see Configure the External Postmaster Address.
	Configure Domain Name System (DNS). The Edge Transport server must be configured for internal DNS lookups within the Exchange organization and external DNS lookups for external recipients. Public DNS records must also be configured for this server to send or receive mail from the Internet. For more information, see Configure Edge Transport Server Properties.

Subscribe the Edge Transport server. For more information, see Configure Internet Mail Flow Through a Subscribed Edge Transport Server.

Note To subscribe the Edge Transport server manually instead of using the Edge Subscription process, see Configure Mail Flow Between an Edge Transport Server and Hub Transport Servers Without Using EdgeSync.

If you haven't subscribed this Edge Transport server to your Exchange organization, the value of the external postmaster address is postmaster@[Edge Transport server FQDN]. After you subscribe the Edge Transport server to the Exchange organization, the value of the external postmaster address is postmaster@[default accepted domain]. If you specify a custom value for the external postmaster address on the Hub Transport servers in your Exchange organization, you must manually configure the external postmaster address on the Edge Transport server. For more information, see Configure the External Postmaster Address.

Configure Domain Name System (DNS). The Edge Transport server must be configured for internal DNS lookups within the Exchange organization and external DNS lookups for external recipients. Public DNS records must also be configured for this server to send or receive mail from the Internet. For more information, see Configure Edge Transport Server Properties.

Share via