How does a server ending up in the wrong site actually happen? Michael, in your blog post, it sounds like you never found out for sure why that machine was in the wrong site.
Based on this KB: https://support.microsoft.com/en-us/kb/247811 it sounds like a client should attempt to locate a DC in its own site if the one that it first contacted is outside of its site. Matthew Topper ________________________________ From: [email protected] <[email protected]> on behalf of Kelsey, John <[email protected]> Sent: Friday, July 10, 2015 11:12 AM To: '[email protected]' Subject: [Exchange] RE: Exchange 2007 using wrong DC ? Hmph. I’ve added that key and will reboot tonight to see if it corrects it. Thank you good sir. From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Friday, July 10, 2015 10:57 AM To: [email protected] Subject: [Exchange] RE: Exchange 2007 using wrong DC ? There is your problem. A remote DC responded before the local DCs when the server was being rebooted. Exchange just asked AD for the site name and is using it. See: http://theessentialexchange.com/blogs/michael/archive/2015/04/29/forcing-a-server-s-active-directory-site.aspx From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kelsey, John Sent: Friday, July 10, 2015 10:50 AM To: '[email protected]' Subject: [Exchange] RE: Exchange 2007 using wrong DC ? It does not. It reports the remote site. This reg key is also incorrect, showing the remote site name. HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DynamicSiteName From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Friday, July 10, 2015 10:44 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Exchange 2007 using wrong DC ? On the exchange server nltest /dsgetsite Does it report the proper site? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kelsey, John Sent: Friday, July 10, 2015 9:40 AM To: '[email protected]' Subject: [Exchange] Exchange 2007 using wrong DC ? Exchange 2007 server with rollup 14 installed. We rebooted the server last evening to correct an issue with our backups. Since the server reboot, when Outlook clients (2007) launch and try to connect to Exchange, they fail on the first try. You click ‘retry’ and it works. It appears that Outlook is trying to use a DC in another AD site on the first try instead of the DCs here on the local LAN Not sure why a reboot would cause this issue..but how can you tell Outlook/Exchange to use only the local DCs instead of ones in other AD sites first? Thanks all! *************************************** John C. Kelsey Penn Highlands DuBois •: 814.375.3073 • : 814.375.4005 •: [email protected]<mailto:[email protected]> *************************************** [PHH ESig Logo 150dpi] This email and any attached files are sensitive in nature and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of Penn Highlands Healthcare or its affiliates.. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. This email and any attached files are sensitive in nature and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of Penn Highlands Healthcare or its affiliates.. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. This email and any attached files are sensitive in nature and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of Penn Highlands Healthcare or its affiliates.. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
