Release notes for Exchange Server Deployment Assistant

  • Article

 

Content for the Exchange Server Deployment Assistant is updated on an occasional basis.

In addition to English, the Deployment Assistant is also available in Chinese (Simplified), Chinese (Traditional), French, German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish.

February 2013 Content Update

Hybrid scenarios

  • All scenarios: Updated guidance and checklists to correspond to the release of Service Pack 3 of Exchange Server 2010. Changes include:

    • Removed qualifying question about existing Forefront Online Protection for Exchange for on-premises organizations:   Forefront Online Protection for Exchange (FOPE), now known as Exchange Online Protection (EOP), is no longer a limiting factor in hybrid transport routing options. Therefore, organizations no longer need to request that their existing EOP service be merged with the EOP service provided with the Microsoft Office 365 tenant. The EOP services are merged automatically and do not require configuration by the customer.

    • Removed limitations on configuring centralized mail transport in the Manage Hybrid Configuration wizard:   Centralized mail transport can be configured regardless of existing EOP service configuration.

October 2012 Content Update

Hybrid scenarios

  • Exchange 2003 scenario:   Updated guidance and checklists for installing Exchange 2010 SP2 servers. Guidance is for Client Access, Mailbox, and Hub Transport server roles to be installed on each Exchange 2010 SP2 server in the hybrid deployment.

  • Exchange 2003 and Exchange 2007 scenarios:   Updated Collect Information and Configure DNS guidance for hybrid deployment checklists that include Edge Transport server.

  • Exchange 2003, Exchange 2007, and Exchange 2010 scenarios:   Updated guidance for Exchange 2010 SP2 Rollup 4 requirement.

May 2012 Content Update

Hybrid scenarios

  • Exchange 2010 scenario:   Updated guidance from Exchange 2010 Service Pack 1 (SP1) to Exchange 2010 Service Pack 2 (SP2).

April 2012 Content Update

Hybrid scenarios

  • Exchange 2007 scenario:   Updated guidance from Exchange 2010 Service Pack 1 (SP1) to Exchange 2010 Service Pack 2 (SP2).

March 2012 Content Update

Hybrid scenarios

  • Exchange 2003 scenario:   

    • Updated guidance from Exchange 2010 Service Pack 1 (SP1) to Exchange 2010 Service Pack 2 (SP2).

    • Configure tenant monitoring:   Removed topic from checklists in initial Exchange 2010 SP2 update release. Content not applicable to hybrid deployments.

  • Exchange 2007 and Exchange 2010 scenarios:   Deprecated guidance for Exchange 2007 and Exchange 2010 organizations based on Exchange 2010 SP1 in advance of pending release of guidance based on Exchange 2010 SP2. Note: Exchange 2010 SP1-based guidance for these scenarios is available for reference at Office 365 Hybrid Deployments with Exchange 2010 SP1.

On-Premises scenarios

  • All scenarios:

    • Install the Client Access Server role; Install the Edge Transport server role; Install the Mailbox server role; Install the Unified Messaging server role:   Updated installation procedure for Service Pack 2 (SP2) of Exchange 2010.

    • Understanding <version> Prerequisites:   Updated for Exchange 2010 SP2.

    • Understanding Single and Multi-role Server Installations:   New topic. Available via link in the “Install the Client Access server role” topic.

  • All scenarios except 2007 Upgrade:

    • Add digital certificates on the Client Access server; Configure a legacy host name:   Added information relevant to Exchange 2003 about enabling SSL and installing certificates to secure the communications between the client messaging applications and the Exchange Front-End server.

  • 2007 Upgrade scenario:

    • Updated multiple topics to remove references to Exchange 2007 SP2, which is no longer supported by Microsoft. (For more information, see Microsoft Support Lifecycle.)

December 2011 Content Update

Hybrid scenarios

  • All scenarios:   In the “Configure mail flow” step, updated guidance for configuring the "Outbound Remote Domain to On-Premises Recipients" remote domain (Step 4 in “How do I configure transport settings in my cloud-based organization”). The TargetDeliveryDomain parameter for the remote domain is no longer configured for the cloud-based organization.

August 2011 Content Update

On-Premises scenarios

  • All scenarios:   Added estimated time-to-complete information to configuration topics.

Hybrid scenarios

  • All scenarios:   Updated content to use hybrid terminology.

  • All scenarios:   In “Configure mail flow” step, updated guidance about creating a new Receive connector. Also added a Note about recommended action to take if you see a DuplicateDomain-GUID entry, for example, DuplicateDomain-GUIDcontoso.com, when using the FOPE administration center.

  • All scenarios:   In “Install Exchange 2010 hybrid server” step, added a Note about requirement to contact Office 365 support for an Exchange 2010 Hybrid Edition product key.

  • All scenarios:   In “Verify prerequisites when deploying AD FS” step, updated guidance about required number of servers.

Cloud-Only scenarios

  • Added guidance for moving Exchange organization to the cloud via cutover migration, staged migration, or IMAP.

July 2011 Content Update

On-Premises scenarios

  • Understanding Exchange <version> Prerequisites:   In “Directory Servers” section, updated relevant Service Pack (SP) for Windows Server 2003 from SP1 to SP2.

Coexistence scenarios

  • Before you begin:   Clarified guidance about public folder replicas in the Exchange 2003 scenario.

  • Configure mail flow:   Revised guidance about configuration of smarthost and SSL certificate checks on outbound FOPE connector; updated user interface (UI) references to correspond with current UI.

  • Configure organization relationships:  Revised order of appearance of EnableCustomization step.

  • Configure Autodiscover DNS records:   Revised procedure to point the Autodiscover DNS record to Exchange 2010 SP1 Client Access server.

June 2011 Content Update

On-Premises scenarios

  • Enable Outlook Anywhere:   Revised procedure to add caution about the Negotiate Ex authentication option.

Coexistence scenarios

  • Updated the application to include the scenario of Coexistence with Exchange Online and Exchange Server 2010 on-premises. (Currently, English only.)

  • Create a test mailbox:   Clarified test user account to use when testing Outlook Web App redirection; applies to Exchange 2003 and Exchange 2007 scenarios.

  • Configure organization relationships:   Removed requirement to manually configure TargetSharingEpr endpoint and added requirement to enable OrganizationCustomization for cloud-based organization; applies to Exchange 2003 and Exchange 2007 scenarios.

April 2011 Content Update

On-Premises scenarios

  • All scenarios:   Enabled copy functionality for code examples. Users can now highlight code examples, and then copy using Ctrl+C. (Currently, English only.)

  • Add digital certificates on the Client Access server:   Revised procedure for importing certificates to legacy Exchange 2003 server.

  • Change the OAB generation server:   Revised procedure.

  • Confirm prerequisite steps are done (all scenarios):   Updated to include support for Windows Server 2008 R2.

  • Configure OAB and Web Services virtual directories:   Corrected second example in “How do I know this worked?” section.

  • Install the Client Access server role:   Removed incorrect procedure step regarding Mail Flow Settings page in the “How do I do this?” section.

Coexistence scenarios

  • All scenarios:   Enabled copy functionality for code examples. Users can now highlight code examples, and then copy using Ctrl+C. (Currently, English only.)

  • Updated the application to include the scenario of Coexistence with Exchange Online and Exchange Server 2007 on-premises. (Currently, English only.)

  • Added “Estimated time to complete” information to multiple topics in Exchange 2003 and Exchange 2007 scenarios.

  • Configure federated delegation:   Revised procedure “How do I create a federation trust with the Microsoft Federation Gateway?” in Exchange 2003 scenario.

  • Configure organization relationships:   Revised procedure in “How do I create an organizational relationship for my on-premises organization?” in Exchange 2003 scenario.

February 2011 Content Update

On-Premises scenarios

  • Add digital certificates on the Client Access server:   Added content to topic for the "New installation of Exchange 2010" scenario option.

  • Move public folder data from Exchange <version> to Exchange 2010:   Corrected syntax of second command in "How do I know this worked?" section.

  • Understanding Exchange <version> Prerequisites:   Added information about hotfixes for Windows Server 2008.

Coexistence scenario

  • Before you begin:   Removed references to support for Outlook 2003.

  • Collect needed information:   Added caution about the *.onmicrosoft.com domain.

  • Configure accepted domains:   Added caution about the *.onmicrosoft.com domain.

  • Configure Exchange certificates:   Corrected syntax of command in "How do I know this worked?" section.

  • Configure mail flow:   Updated information related to service FOPE connectors, DNS support, source IP in FOPE, and protocol logging.

  • Configure organization relationships:   Corrected reference to test user account. Added information about manual configuration of the TargetSharingEpr parameter. Relocated steps related to Outlook Anywhere to independent topic "Configure Outlook Anywhere".

  • Configure service autodiscover DNS record:   Corrected alias name in "How do I know this worked?" section.

  • Create a test mailbox:   Added steps related to assigning licenses to new users.

  • Move or create a mailbox:   Added steps related to assigning licenses to new users.

  • Understanding Shared and Split SMTP Namespaces:   Added caution about the *.onmicrosoft.com domain.

  • Understanding Transport Options:   Added caution about the *.onmicrosoft.com domain.

Version 2.0 (December 2010)

  • Released content in English only and updated the application for the following scenarios:

    • Coexistence with Exchange Online and Exchange Server 2003 on-premises

October 2010 Content Update

  • Checklists for Exchange 2003 and Exchange 2007 Upgrade scenario:   Added step about moving public folders.

  • Configure OAB and Web Services virtual directories:   Corrected parameter in second example of “How do I know this worked?” section.

  • Configure settings on virtual directories:   Updated guidance about setting the Exchange2003URL parameter.

  • Confirm prerequisite steps are done:   Corrected version of Windows Server service pack required for each Active Directory site where Exchange 2010 will be deployed.

  • Enable Outlook Anywhere:   Updated procedure to describe user interface option of Negotiate Ex authentication.

  • Install the <type> server role:   Updated with Exchange 2010 SP1 information.

  • Understanding Exchange <version> Prerequisites:   Updated with Exchange Server 2010 Service Pack 1 (SP1) information.

June 2010 Content Update

  • Configure a legacy host name:   Provided guidance regarding IMAP, POP, backup changes, OCS integration, and additional information about certificates.

  • Configure a legacy host name and Add digital certificates on the Client Access Server:   Added additional detail regarding legacy namespaces and modifying CAS server settings.

  • Configure OAB and Web Services virtual directories and Install the Client Access Server Role:   Added information about configuring Autodiscover when upgrading from Exchange 2003.

  • Configure settings on virtual directories:   Added information regarding understanding virtual directories and Autodiscover when upgrading from Exchange 2003.

  • Enable Exchange 2010 Outlook Anywhere:   Added information about using the Exchange Server Remote Connectivity Analyzer to verify connectivity.

  • Install server role tasks:   Added “| format-list” argument to “Get-Exchange <server name>” command.

  • Post-installation tasks:   Added section about optional tasks to complete the Hub Transport server role and a section about removing legacy versions of Exchange when upgrading from Exchange 2003, Exchange 2007, or a mixed environment.

April 2010 Content Update

  • Install the Client Access Server Role:   Called out need for additional steps that are required to determine RPC encryption configuration for Outlook 2003 clients.

March 2010 Content Update

  • Add digital certificates on the Client Access server:   For all scenarios except a new Exchange 2010 install, added steps related to importing the certificate to a legacy server.

  • Confirm and understand prerequisite steps for upgrade from Exchange 2003 and/or Exchange 2007 or a new Exchange 2010 install:   Added information about the new Exchange Pre-Deployment Analyzer.

  • Install the Client Access server role:   Removed non-applicable step regarding Mail Flow Settings page.

Version 1.1 (January 2010)

  • Released content for the following scenarios:

    • Upgrading from Exchange Server 2007

    • Upgrading from mixed Exchange Server 2003 and 2007

    • New Exchange Server 2010 installation

  • Exchange Team Blog article

Version 1.0 (November 2009)

Known Issues

  • The Exchange Deployment Assistant is implemented using Microsoft Silverlight technology. Currently, Silverlight only runs in a 32-bit mode. This is mainly because other browser plug-ins (and most browsers) don’t support 64-bit mode yet.

  • It's rare, but if you receive an unexpected error, it may be due to a time-out from our Web service. Close your browser, and then try to start the Deployment Assistant again.