#EXCHANGE CLIENT HOW TO#

However, once a mailbox is moved from 2010 to 2016, the outlook client used still points to the 2010 system. My original thought was that given both servers are both running a Mailbox service and a Client Access Service, Outlook clients would just connect to whatever server held their mailbox. I'm rather new to this, and i feel like there's something obvious I'm missing. Logging into the OWA of the 2016 box shows that any test messages sent/received are present and accounted for. Once a test mailbox is moved from the 2010 server to the 2016, Outlook will no longer update given the mailbox is on the 2016 server and it is connecting to the 2010 server. When I moved a test user from 2010 server to the 2016 server, their outlook still connects to the 2010 server.Р”В¤. When configuring outlook with any of the test accounts I created on the 2016 server, they connect to the 2016 server.Р”Р€. All existing users' are still connecting to the 2010 server.Р”Сћ.

#EXCHANGE CLIENT HOW TO#

I am having a strange issue that I'm unsure of how to resolve. the internal A-record for the mail server has been switched to point to the new 2016 server's IP. There are also two SCPs in AD for the two servers, 20. local domain, so I am using an SRV record for autodiscover.

So, right now nothing business-critical is being disrupted given mailflow is still working fine. Mail is properly delivered to the 2010 clients' mailboxes, and is properly sent as well. The 2016 server is what is sending/receiving all mail at this point, but has no mailboxes other than test mailboxes when I was verifying functionality. Then, I brought up a 2016 server to begin migration. Standard single-server setup for 2010 (Mailbox, Client Access, Hub Transport, etc.) Originally, we had a single 2010 Exchange server.

Exchange client