Outlook clients don't automatically update to new Exchange server when mailbox moved

We are migrating from SBS2011 (Exchange 2010) to on-premises Exchange 2013.  Both are at the latest SP and CU level.

Each server has its own WAN IP and DNS name (2010: remote.domain.com, 2013: mail.domain.com). Both have a valid SSL certificate installed.  Autodiscover is configured with a DNS SRV entry pointing to the new server.

OWA works fine for mailboxes on either server (with the 2013 proxying for the 2010 where needed).

New Outlook profiles work fine for mailboxes on either server (in Outlook 2007, 2010, 2013 and 2016).  Outlook clients are patched with WSUS to the latest level.  No changes have been made to the default settings rolled out to Outlook by Autodiscover.  Microsoft's testconnectivity.com passes for mailboxes on either server.

When a mailbox is moved, we see the following behaviour:

iOS: automatically updates server name, no changes required.
Android: requires manual change (expected).
Outlook 2007: pop-up "administrator has made a change", restart Outlook, server name is updated automatically, no changes required.
Outlook 2010, 2013, 2016: pop-up as above but server name is not updated automatically after restart.

Currently the only solution is to edit the server name in the account properties (if available, it's not in fully patched Outlook 2010-2016) or to create a new Outlook profile.  This is possible but there are 50+ clients so we'd ideally like it to update automatically.

How can we configure Exchange or Outlook so it automatically updates the server name?  Thanks in advance for any advice.
David HaycoxConsultant EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David HaycoxConsultant EngineerAuthor Commented:
Looks like this may be the solution, am testing it now:

David HaycoxConsultant EngineerAuthor Commented:
That didn't fix the original problem, although it did resolve a secondary issue (Outlook prompting for credentials and unable to access public folders on Exchange 2010 after the mailbox had been moved to Exchange 2013).  Outlook 2010 and later clients still don't automatically update the server name.
Iradat SiddiquiCommented:
Please apply this fix on outlook.. https://support.microsoft.com/en-us/kb/2863911

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David HaycoxConsultant EngineerAuthor Commented:
Answered own question.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.