Hi,

I have migrated ex2010 to ex13cu5, migration fine. But when I shutdown old exchange server outlook clients getting delay to update the folder.  When I check on the connection status, it is trying to connect to old ex10 server (by fqdn then server name) then automatically close this query. Finally it will be fine!

If there is ex10 is online, no issue at all to connect and latency for updating folder.

Why it is still contacting old exchange server?

Autodiscover name , I set for all as below:

Set-ClientAccessServer Identity CON-EX2010CAS - AutoDiscoverServiceInternalUri https://mail.contoso.com/Autodiscover/autodiscover.xml

Set-ClientAccessServer Identity CON-EX2013CAS - AutoDiscoverServiceInternalUri https://mail.contoso.com/Autodiscover/autodiscover.xml

Thanks,

Riyatanu,

I would check your Local DNS and make sure the local MX records do not have the old server still listed.  This can cause the Outlook Clients to try the old server.  While you are in the DNS records also make sure all references to the old mail server are removed.

Curt Winter

Certified Microsoft Professional

I don't have any dns entry to old ex2010, but there is only A record for old ex2010. and I am using split dns scenario. email, autodiscover entires pointed to new cas13 server.

Thanks,

Riyatanu,

Check the local machines for HOSTS files that could point to the old server also.

Depending on when you made DNS changes it can take up 48 hours to propagate across the internet and the old  settings to disappear.

Curt Winter

Microsoft Certified Professional

Hi Curt,

The problem we are facing internal outlook clients.

and one thing let me clear you,

Get-WebServicesVirtualDirectory mbx01\ews* | fl name, internal*, external*, *authentication

The result showing; internal nlbbypass url still pointing to old exchange2010 server local url

and remaining exchange2013 server is empty.

can we remove this one or do we need keep as it is?

Thanks.

Riyatanu,

If it is pointing to the old server I would remove it.  The old server does not exist so any settings still pointing to it need to be removed so the clients are not getting the information to connect to it.

Curt Winter

Microsoft Certified Professional

Removed Internal nlbbypass url, still the same..,

Dear Experts

Have any idea,

Thanks

• Edited by Riyatanu 2 minutes ago

Removed Internal nlbbypass url, still the same..,

Dear Experts

Have any idea,

Thanks

• Edited by Riyatanu Wednesday, March 25, 2015 7:20 AM

The Problem resolved by deleting the ex2010 old Database and public folder, now it looks so fine,,

now I am ready for removal old exchange server :)

Thanks

• Marked as answer by Riyatanu 19 hours 6 minutes ago