Configure SCP and update DNS Records for Exchange 2010 to Exchange 2016 migration

Instant Solution - Kernel Migrator for Exchange

Exchange/Office 365 migrations are quite easy with professional tools like Kernel Migrator for Exchange. This tool helps to manage mailbox and public folder migrations involving different Exchange versions and deployment types. Also, this tool helps with all tasks starting from the pre-migration analysis to the preparation of reports after the migration.

Configure SCP

While configuring services in Exchange Server 2016 (for more info, please see Part 5 of this series), you need to update the Service Connection Point. This should be done all servers. This is how you can do this:

In Exchange 2010

  1. In Exchange 2010 CAS Server, open Exchange Management Shell.
    Run $AutodiscoverHostName = “<Autodiscover host name of your Internet-facing Exchange 2016 Mailbox server>”
    For e.g.:

    $AutodiscoverHostName = “”

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

    Note: To verify the SCP in Exchange Server 2010, run the following cmdlets:

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

  3. In Exchange 2016 Server

  4. In Exchange 2016 Mailbox Server, open the Exchange Management Shell.
  5. Run $AutodiscoverHostName = "<Autodiscover host name of your Internet-facing Exchange 2016 Mailbox server>"
    For e.g.:

    $AutodiscoverHostName = “”

  6. Now run:
    Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version
    15.1*”) -And ($_.ServerRole -Like “*Mailbox*”)} | Set-
    ClientAccessService -AutoDiscoverServiceInternalUri https://

  7. To verify these settings, run:
    Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like “Version
    15.1*”) -And ($_.ServerRole -Like “*Mailbox*”)} | Get-
    ClientAccessService | Format-Table Name,
    AutoDiscoverServiceInternalUri -Auto

Change the DNS Records

Finally, you need to change the DNS records so as to direct the connection to the newly installed Exchange 2016 Server. So update Public DNS Records and Internal DNS Records as per the requirements.

The configuration of Exchange 2016 services completes with SCP configuration and DNS record changes. Now you can migrate mailboxes and public folders to Exchange 2016 (see Part 7 of this series).


To prepare Exchange 2016 for Exchange 2010 migration, you need to configure SCP and change DNS records. These are the final requirements before the migration of mailboxes and public folders to Exchange 2016.

Instant Migration Tips : Migrate Outlook rules & permissions

Migration of Outlook rules and folder permissions is an import task after Exchange 2010 to Exchange 2016 migration. Kernel Migrator for Exchange helps to migrate Outlook rules and folder permissions from the source Exchange Server to the destination Exchange Server.