We help IT Professionals succeed at work.

Exchange Migration 2013 - 2016 Error in outlook.

Raneesh A
Raneesh A asked
on
Dear Team,
I made an exchange Migration from 2013 to 2016.
I migrated all the system Mailboxes and started migrating all the users to new DB.
But i am frequently getting an error. below in my outlook.
The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook

Can you please help me sorting this out.
Comment
Watch Question

AlexA lack of information provides a lack of a decent solution.
CERTIFIED EXPERT

Commented:
that's completely normal, you're migrating user mailboxes, outlook will have to close and reopen in order to connect to your new 2016 servers.

Regards
Aelx
timgreen7077Exchange Engineer
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
The error is normal. once the user closes outlook and reopen it will no longer appear. That error is by design. I agee with @Alex, so there is no cause for concern.
Rajkumar DuraisamyRajkumar Duraisamy (Rajkumar-MCITP)
Top Expert 2012

Commented:
If it is continuously prompting the same message now and then.. repair or recreating the out profile is the only option for you..
Raneesh AIT Engineer

Author

Commented:
Yes the error is keep coming again for some users.

Also the in DNS record the A record only points to the DAG IP of the 2013 Exchange. But all email al working fine even if the Mailbox is in 2016 DB.
The DB created in Exchange 2016 is not added in DAG. Waiting for it to finish and then i will create a separate DAG for 2016 and then Remove the 2013 Servers.
AlexA lack of information provides a lack of a decent solution.
CERTIFIED EXPERT

Commented:
Also the in DNS record the A record only points to the DAG IP of the 2013 Exchange. But all email al working fine even if the Mailbox is in 2016 DB.

What A Record we talking about here? Auto-discover should take care of everything

The DB created in Exchange 2016 is not added in DAG. Waiting for it to finish and then i will create a separate DAG for 2016 and then Remove the 2013 Servers.

Ok, bad plan to be fair because you now have a single point of failure, but ok.
Raneesh AIT Engineer

Author

Commented:
Hi Alex ,

Auto discover is not configured.
Because users are connected through RDP profile only.
Do I need to configure Auto Discover in order to sort this out.
Only entry is mail.company.com points to DAG IpP address in DNS.
A lack of information provides a lack of a decent solution.
CERTIFIED EXPERT
Commented:
if autodiscover hasn't been configured properly how do you expect the client to find it!

You'd have to point each client to the new 2016 servers manually.

https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Client-Connectivity-in-an-Exchange-2016-Coexistence-Environment/ba-p/603945

that should work for 2013 too. I think.

Essentially this is why you're having issues.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.