Mark Lewis
asked on
Problem with Outlook client updating to new server after migration
I am running a single 2010 Exchange server in my environment. A couple of months ago it got a bug I couldnt clean so I decided to build another server to replace it. Everything went fine, ie, moving the CAS, hub, and Internet mail roles etc but I did have a small issue that I discovered after moving the mailboxes and that was even though I created new DB's on the new server, the DB's showed the RPCClientAccessServer attribute still pointed to the old server. I ran a PS command and changed the new DB's to the new server. OWA, Outlook AnyWhere and ActiveSync work fine. Autodiscovery seems to work fine because when I create a new profile in Outlook, it finds the new server rather than the older one.
The problem I have is that not all existing Outlook clients are pointing to the new server in their existing Outlook profile as I soon figured out when I diasabled the NIC on the old server to make sure it wasnt still being called upon to do work. I would say it's about half of my clients that updated with the new server vs one's that did not. I can create a new profile but I would rather not if I didnt have to do so as we have about 500 clients across multiple cities.
The problem I have is that not all existing Outlook clients are pointing to the new server in their existing Outlook profile as I soon figured out when I diasabled the NIC on the old server to make sure it wasnt still being called upon to do work. I would say it's about half of my clients that updated with the new server vs one's that did not. I can create a new profile but I would rather not if I didnt have to do so as we have about 500 clients across multiple cities.
Last Comment
If the old server was load balanced make sure that the server is no longer apart of the load balancer whether using Windows NLB or a 3rd party load balancer. Also make sure that the old server is no longer apart of the name space, so if the name space is mail.domain.com just be sure that in DNS there is no A record with the name space pointing to an old IP address for that server, because even though you remove the NIC DNS will still reference it.
ASKER
There is no load balancing but there is still a static internal DNS record to the old server since it's technically still alive. I will give that a go.
Ok, you will have to remove that static entry for that server, and once DNS refreshes on those user machines it will eventually stop looking at it an not attempt to connect. It could take a bit for the DNS to refresh on the user machines or the users can run
ipconfig /flushdns
to speed up the refresh, but make sure when you remove the record give your DNS servers (if you have multiple) at least 30 minutes to replicate that change across all the DNS servers.
ipconfig /flushdns
to speed up the refresh, but make sure when you remove the record give your DNS servers (if you have multiple) at least 30 minutes to replicate that change across all the DNS servers.
ASKER
It seems to be a problem with those that have Cached mode enabled although I still havent figured out a solution besides manually running a repair on the Outlook profile.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
