Exchange 2016 not accessible in exch 2013 and 2016 coexistence

This is a migration from MS Exchange server 2013 to 2016 for a small environment with 25 mailboxes. There is 1 multi-roles exch2013 and a new deployment of exch2016 server. Setup of Exchange 2016 server progress and completed successfully. After that, most of the mailboxes migrated without problem. However, we found that the URLs to access to Exchange 2016 server doesn't work. These URLs include, outlookanywhere, owa, Activesync, powershell, etc. OWA access to mailboxes still kept in exch 2013 are working. It looks like there are some of the post-installation tasks still yet to conduct, is that true?

Please enlighten what tasks need to be conduct in order to get client access part of Exchange 2016 work. Thanks in advance.
Who is Participating?
Todd NelsonSystems EngineerCommented:
It looks like there are some of the post-installation tasks still yet to conduct, is that true?

Please enlighten what tasks need to be conduct in order to get client access part of Exchange 2016 work.

After you installed Exchange, did you move the arbitration mailboxes?  Those are the first mailboxes that must be moved.

Get-Mailbox -Arbitration | where { $_.ServerName -eq "EXCH2013SERVERNAME" } | New-MoveRequest -TargetDatabase "EXCH2016DATABASE

Open in new window

If you have not configured the URLs for Exchange 2016, that would be a requirement. Check the current settings using this reference and make note of the URLs on the 2013 server ...

And then set both the internal and external URLs using the value of the Exchange 2013 external URL using these commands...

Set-ActiveSyncVirtualDirectory -Identity "EXCH2016SERVERNAME\Microsoft-Server-ActiveSync (Default Web Site)" -InternalUrl "" -ExternalUrl ""
Set-ClientAccessService -Identity "EXCH2016SERVERNAME" -AutoDiscoverServiceInternalUri ""
Set-EcpVirtualDirectory -Identity "EXCH2016SERVERNAME\ecp (Default Web Site)" -InternalUrl "" -ExternalUrl ""
Set-MapiVirtualDirectory -Identity "EXCH2016SERVERNAME\mapi (Default Web Site)" -InternalUrl "" -ExternalUrl ""
Set-OabVirtualDirectory -Identity "EXCH2016SERVERNAME\OAB (Default Web Site)" -InternalUrl "" -ExternalUrl ""
Set-OutlookAnywhere -Identity "EXCH2016SERVERNAME\Rpc (Default Web Site)" -ExternalHostname "" -ExternalClientsRequireSsl $True -InternalHostname "" -InternalClientsRequireSsl $True -ExternalClientAuthenticationMethod "Negotiate"
Set-OwaVirtualDirectory -Identity "EXCH2016SERVERNAME\owa (Default Web Site)" -InternalUrl "" -ExternalUrl ""
Set-PowerShellVirtualDirectory -Identity "EXCH2016SERVERNAME\PowerShell (Default Web Site)" -ExternalUrl ""
Set-WebServicesVirtualDirectory -Identity "EXCH2016SERVERNAME\EWS (Default Web Site)" -InternalUrl "" -ExternalUrl ""

Open in new window

Did you export the SSL certificate from the Exchange 2013 server and import into Exchange 2016? ...

Did you move the public folders? ...

Did you migrate your "relay" receive connectors? ...

Review the articles in this reference ...

And these references...
Gaurav SinghSolution ArchitectCommented:
did u created DNS records for new exchang server?  

Refer below for checking the things in your environment.
you need to point your autodiscover and / to exchange 2016
Also point AD SCP to exchange 2016 if already not done
Have you checked / configured mail flow?
Is it working?
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Sandeep KumarAssociate ConsultantCommented:
There are two ways to migrate MS Exchange 2013 to Exchange 2016:

Via manual method: For this you can refer to Step-by-step guide for migrating Exchange Server 2013 to 2016

Via automated tool: It is better to use this method for large amount of mailboxes. For this I recommend Kernel Migrator for Exchange software. It is so advanced tool which can perform migration in multiple scenarios. To know more about Exchange Migration, visit:
MichaelBalackAuthor Commented:
Hi Todd,

Give me sometime to read through your suggestions and articles. I will get back to you soon.
MichaelBalackAuthor Commented:
Hi Todd,

I went through all of the suggested checklists and actions. Now, Exchange 2k16 is fully accessible and working fine.
MichaelBalackAuthor Commented:
Thanks for Expert Todd in providing the comprehensive checklists and actions. Eventually, Exch 2k16 is working fine.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.