Migrating users from Exc2k7 to 2k10 - getting certificate warning
I recently migrated a bunch of users from Exchange 2007 to Exchange 2010. We have powered off the 2007 server and plan to decomission it within 2 weeks. Everything works properly except that users get a certificate error when rebooting their computer and opening Outlook, or when creating new Outlook profiles. The certificate error says oldserver.domain.com - The name on the security certificate is invalid or does not match the site name. Is it possible to get rid of this error before I am able to fully decomission the Exchange 2007 server?
July 20th, 2012 1:35pm

Can you check your web services urls? Is it still pointing to oldserver.domain.com? Use the article below to check. Don't run set just run get against each URL to check. Outlook 2007 security warning: "The name of the security certificate is invalid or does not match the name of the site" http://support.microsoft.com/kb/940726James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 2:17pm

Thanks - when I run get-clientaccesserver | fl the old server lists the old autodiscover url. Is it posisble to fix this from the new server? when I try to change it using the Set command I get an error saying I cannot change the URL because it is read-only to the current version of Exchange.
July 20th, 2012 3:06pm

I am not a fan of the "turn it off and see what breaks" method of confirming it is good to remove. Thanks - I am powering the server on today. How do you confirm a server is good to be decmossioned before actually decomissioning then?
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2012 12:39pm

As long as you followed the article below you should be good. You can look through some logs, receive logs, IIS etc to see if it's still getting traffic but some entries you see could be a red herring and legit noise but you'll be able to decipher what is noise and what is legit. Remove the Last Legacy Exchange Server from an Exchange 2010 Organization http://technet.microsoft.com/en-us/library/gg576862James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
July 24th, 2012 1:18pm

I've found that the Technet articles for decomissioning Exchange do not always account for everything. Sometimes the Syntax of a command has changed since an article was published and you may not be ready to decomission a server, or you have a non-standard setup. I still feel like powering off Exchange is the best way to catch these issues - albeit, as in my case it clearly presents new issues.
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2012 1:26pm

You can shut it down it's your own preference some like to do that some don't. You can update that autodiscover URL to the new server now, you don't need to wait until you decom the old server, actually it should be set now since all users are on the new server. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
July 24th, 2012 1:41pm

I am not a fan of the "turn it off and see what breaks" method of confirming it is good to remove. Thanks - I am powering the server on today. How do you confirm a server is good to be decmossioned before actually decomissioning then? Hi, Please verify if the issue still persists after you change the autodiscoverinternaluri to your CAS 2010 server.Xiu Zhang TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 25th, 2012 2:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics