Raneesh A
asked on
Exchange Migration 2013 - 2016 Error in outlook.
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.
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.
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.
If it is continuously prompting the same message now and then.. repair or recreating the out profile is the only option for you..
ASKER
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.
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.
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.
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Regards
Aelx