Exchange 2010 to Exchange 2016 Migration-Part 7: Moving Namespaces

In this Part 7, We will see how to move Namespaces to Exchange 2016 Servers

If you would like to read the part 1 in this article series please go to Exchange 2010 to Exchange 2016 Migration -Part 1: AD Installation

If you would like to read the part 2 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 2: Exchange 2010 Installation and configuration 

If you would like to read the part 3 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 3: Exchange 2010 DAG and outlook Anywhere Configuration

If you would like to read the part 4 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 4: Exchange 2016 Installation 

If you would like to read the part 5 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 5: Exchange 2016 Configuration 

If you would like to read the part 6 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 6: Mailboxes Move

 

Configure Outlook Anywhere:

If you’re currently using Outlook Anywhere in your Exchange 2010 environment, you’ll need to enable and configure Outlook Anywhere on all Exchange 2010 servers in your organization. This will allow your Exchange 2016 servers to proxy connections to your Exchange 2010 servers. If you’re not currently using Outlook Anywhere in your Exchange 2010 environment, and you don’t want to use it, you can skip this step. When you use the steps below to configure Outlook Anywhere, the following configuration is set on each Exchange 2010 server:

  • The Outlook Anywhere external URL is set to the external host name of the Exchange 2016 server.
  • Client authentication, which is used to allow clients like Outlook 2016 to authenticate with Exchange, is set to Basic.
  • Internet Information Services (IIS) authentication, which is used to allow Exchange servers to communicate, set to NTLM and Basic.
  1. Open the Exchange Management Shell on your Exchange 2010 Client Access server.
  2. Store the external host name of your Internet-facing Exchange 2016 Mailbox server in a variable that will be used in the next steps. For example, webmail.windowstechpro.com.

$Exchange2016HostName = “webmail.windowstechpro.com”

and run the below command,

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $True} | ForEach {Set-OutlookAnywhere “$_\RPC (Default Web Site)” -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName $Exchange2016HostName -IISAuthenticationMethods NTLM, Basic}

1

The following command will change the configuration of Outlook Anywhere on any Exchange 2010 server in your organization on which it’s already enabled.

Run the following command to configure Exchange 2010 servers that already have Outlook Anywhere enabled to accept connections from Exchange 2016 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName $Exchange2016HostName -IISAuthenticationMethods NTLM, Basic

2

To verify that you successfully configured Outlook Anywhere on your Exchange 2010 servers to accept connections redirected from Exchange 2016, do the following:

  1. Open the Exchange Management Shell on your Exchange 2010 Client Access server.
  2. Run the following command to view the Outlook Anywhere configuration on your Exchange 2010 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-OutlookAnywhere | Format-Table Server, ClientAuthenticationMethod, IISAuthenticationMethods, SSLOffloading, ExternalHostname -Auto

3

Configure service connection point(SCP)

Autodiscover uses an Active Directory object called the service connection point (SCP) to retrieve a list of Autodiscover URLs for the forest in which Exchange is installed. When you install Exchange 2016, you need to update the SCP object to point to the Exchange 2016 server. This is necessary because Exchange 2016 servers provide additional Autodiscover information to clients to improve the discovery process.

You must update the SCP object configuration on every Exchange server in the organization. You need to use the version of the Exchange Management Shell that corresponds to the version of the Exchange server you’re updating.

Perform the following steps to configure the SCP object on your Exchange 2010 servers.

  1. Open the Exchange Management Shell on your Exchange 2010 Client Access server.
  2. Store the Autodiscover host name of your Internet-facing Exchange 2016 Mailbox server in a variable that will be used in the next step. For example, autodiscover.contoso.com.

$AutodiscoverHostName = “autodiscover.windowstechpro.com”

 3 Run the following command to set the SCP object on every Exchange 2016 server to the Autodiscover URL of the new Exchange 2016 server.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xml

Perform the following steps to configure the SCP object on your Exchange 2016 servers.

Perform the following steps to configure the SCP object on your Exchange 2016 servers.

  1. Open the Exchange Management Shell on your Exchange 2016 Mailbox server.
  2. Store the Autodiscover host name of your Exchange 2016 Mailbox server in a variable that will be used in the next step. For example, autodiscover.contoso.com.
    $AutodiscoverHostName = “autodiscover.windowstechpro.com”
  3. Run the following command to set the SCP object on every Exchange 2016 server to the Autodiscover URL of the new Exchange 2016 server.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xml

To verify that you successfully configured the AutoDiscoverServiceInternalUrl property on your Exchange 2010 servers with the value of the Exchange 2016 Autodiscover URL, do the following:

  1. Open the Exchange Management Shell on your Exchange 2010 Client Access server.
  2. Run the following command to view the SCP object configuration on Exchange 2010 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 14*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto

4

To verify that you successfully configured the AutoDiscoverServiceInternalUrl property on your Exchange 2016 servers with the value of the Exchange 2016 Autodiscover URL, do the following:

  1. Open the Exchange Management Shell on your Exchange 2016 Mailbox server.
  2. Run the following command to view the SCP object configuration on Exchange 2016 servers.

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version 15*”) -And ($_.ServerRole -Like “*ClientAccess*”)} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto

5

Configure DNS records

Now that you’ve configured your Exchange 2010 and Exchange 2016 servers, it’s time to change your DNS records to direct connections to your new Exchange 2016 server. You’ll move the host names (for example, Webmail.windowstechpro.com) users have been using to connect to Outlook Web Access (now known as Outlook on the web in Exchange 2016), Autodiscover, and so on, from your Exchange 2010 server to your Exchange 2016 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2016 server will proxy the request and communicate with the Exchange 2010 server on their behalf. Configuring DNS includes the following:

Point the below records to the exchange 2016 servers,

Autodiscover.windowstechpro.com

Webmail.windowstechpro.com

Once DNS Records pointed to Exchange 2016, You can still see the mailboxes of the Exchange 2010 getting connected without any issues.

also mailboxes of Exchange 2016 are getting configured using autodiscover URL that you can verify using TEST E-mail AutoConfiguration

6

Outlook Connection Status shows that proxy server and connections are Established properly.

7

 

If you would like to read the part 1 in this article series please go to Exchange 2010 to Exchange 2016 Migration -Part 1: AD Installation

If you would like to read the part 2 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 2: Exchange 2010 Installation and configuration 

If you would like to read the part 3 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 3: Exchange 2010 DAG and outlook Anywhere Configuration

If you would like to read the part 4 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 4: Exchange 2016 Installation

If you would like to read the part 5 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 5: Exchange 2016 Configuration

If you would like to read the part 6 in this article series please go to Exchange 2010 to Exchange 2016 Migration-Part 6: Mailboxes Move

So far, we have done the migration from Exchange 2010 to Exchange 2016.Hope you enjoyed this multi part articles.Will meet you again with another set articles. Bye for now..

Author Bio

Radhakrishnan Govindan

Leave a Reply

Your email address will not be published. Required fields are marked *