troubleshooting Question

Exchange 2013 resource forest - Outlook will not connect to the new Mail Server post-mailbox migration

Avatar of IT for JHS
IT for JHSFlag for United States of America asked on
Exchange* AutodiscoveryOutlook* exchange install
6 Comments1 Solution26 ViewsLast Modified:
Overview:
3 AD Domains, each hosting its own Microsoft Exchange environment. End game, we will most likey migrate all users/computers into the new domain, but Exchagne is the primary objective
Objective:
Migrate users to one Exchange System to ease administration burden
Plan:
Create new Resource Domain to host Exchange. Migrate users from the 3 existing Exchange footprints to the new one.

Two-Way forest trusts are in place and working across all 4 domains.
ADMT has been installed on a server in the New Targeted Exchagne Forest (for migrating users/computers)
PES Server has been installed in each Source Forest/Domain (not really needed at this stage)

The first step in the migration process, we run the PrepareMailboxMove.ps1 from the Newe Target Exchange Server, for the desired Source Exchagne User. This completes successfully, adding the x.500 proxy address variables to both Exchange Systems.

If we migrate a Mailbox to the new Exchagne System, everything migrates without a problem. The end-user is told "Outlook needs to be relaunched due to an administrator change" - once users close Outlook and relaunch it, Outlook will not connect to their mailbox. The issue seems to be Outlook not directing the client to the new Exchange Server, mail.newexchangesystem.com , instead, it continues trying to connect to mail.oldexchagnesystem.com and never attempts to look at the new Exchange System.
If we go into the Clients Outlook profile (on their computer) and tell it to "Connect to Microsoft Exchange using HTTP" and then specify the New Exchange URL in the "Exchange Proxy Server" address, the client does connect.

I had everyting working in this environment a short while ago, where, migrated Mailbox users had no problem with Outlook finding their *new* mailbox post-migration. At some point, something must've changed to cause the behavrior we are now running into.

Looking for some guidance. Thanks. 
ASKER CERTIFIED SOLUTION
IT for JHS
IT

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 6 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 6 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros