Default writing domain controller

Tags:
Active Directory
Domain Controller
Windows Server 2008 R2
Hi! In my ORG we have several domain controllers, and usually when I open AD UC it automatically chooses a DC that has been close to my location. But I suddenly noticed that working in AD UC was really sluggish and everything took a lot of time. Then I saw that I had connected to a DC far away on a poor connection. I tried closing and opening AD UC several times and it always chose the same DC on the poor connection. This indicates to me that someone has made some changes to the DC on the poor connection as this is now the default chosen DC in the AD UC console. So my question is, what causes this behavior and how can I fix it? We have several other GC and writable DC`s, so it does not stand out in that way. We are running server 2008 R2 across the board.
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: