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.
Please enlighten what tasks need to be conduct in order to get client access part of Exchange 2016 work. Thanks in advance.
you need to point your autodiscover and mail.domain.com / owa.domain.com to exchange 2016
Also point AD SCP to exchange 2016 if already not done
Have you checked / configured mail flow?
Is it working?
Also point AD SCP to exchange 2016 if already not done
Have you checked / configured mail flow?
Is it working?
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: https://www.kerneldatarecovery.com/exchange-migrator/
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: https://www.kerneldatarecovery.com/exchange-migrator/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Todd,
Give me sometime to read through your suggestions and articles. I will get back to you soon.
Give me sometime to read through your suggestions and articles. I will get back to you soon.
ASKER
Hi Todd,
I went through all of the suggested checklists and actions. Now, Exchange 2k16 is fully accessible and working fine.
I went through all of the suggested checklists and actions. Now, Exchange 2k16 is fully accessible and working fine.
ASKER
Thanks for Expert Todd in providing the comprehensive checklists and actions. Eventually, Exch 2k16 is working fine.
Refer below for checking the things in your environment.
https://www.stellarinfo.com/blog/migrate-ms-exchange-server-2013-to-2016/