jpbowdoin
asked on
SBS/Exchange 2010 to Exchange 2016 Migration - Servers still pointing to Old.
Good Morning! Last leg of the migration between SBS 2011/ Exchange 2010 and Exchange 2016.
Will spare the long slog to this point and just sum up where I'm at.
Mail is flowing to E2016.
First major problem is when setting up a new Outlook client with user mailbox on E2016, it's still deferring autodiscover to the old E2010 server. SCP's still exist in ADSS Services for both servers. I'm hesitant to just delete those.
I've run all the Epowershell commands associated with getting autodiscover but it doesn't appear to be setting up outlook on the new server.
Let's start there, the additional details we can add because I bet you've go this off the top of your head. This is critical at this point for me so anything you can do is much appreciated.
JP
Will spare the long slog to this point and just sum up where I'm at.
Mail is flowing to E2016.
First major problem is when setting up a new Outlook client with user mailbox on E2016, it's still deferring autodiscover to the old E2010 server. SCP's still exist in ADSS Services for both servers. I'm hesitant to just delete those.
I've run all the Epowershell commands associated with getting autodiscover but it doesn't appear to be setting up outlook on the new server.
Let's start there, the additional details we can add because I bet you've go this off the top of your head. This is critical at this point for me so anything you can do is much appreciated.
JP
OK Setup a SRV record like this Then create a new mail profile for a mailbox that resides on EX2016.
On that server set the correct URLS like this.
</p>
On that server set the correct URLS like this.
</p>
I hope you have:
• Perform firewall changes in order to route mail flow and port 443 traffic to Exchange 2016 server.
• And performed public dns changes in order route OWA and Autodiscover record to target Exchange 2016 server.
You might also have to change the internal host A record pointing to old exchange 2010 to exchange 2016 internal IP.
From EMS on 2010 or 2016 server run cmd:
get-clientaccessserver | fl name, *uri*, identity
Once you get the exchange 2010 autodiscoverURI
Run command:
Set-clientaccessserver -identity "which you got from above" -autodiscoveruri:$null
This will set the SCP for old 2010 to null and outlook will look for the new exchange 2016 only.
• Perform firewall changes in order to route mail flow and port 443 traffic to Exchange 2016 server.
• And performed public dns changes in order route OWA and Autodiscover record to target Exchange 2016 server.
You might also have to change the internal host A record pointing to old exchange 2010 to exchange 2016 internal IP.
From EMS on 2010 or 2016 server run cmd:
get-clientaccessserver | fl name, *uri*, identity
Once you get the exchange 2010 autodiscoverURI
Run command:
Set-clientaccessserver -identity "which you got from above" -autodiscoveruri:$null
This will set the SCP for old 2010 to null and outlook will look for the new exchange 2016 only.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
ASKER