This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 95%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEK%3C/text%3E%3C/svg%3E)
Hi,
I have multiple site and in each site I have one RWDC.
When I logon on site A => logonserver variable and nltest /dsgetsite are ok.
I shutdown my computer and I logon on site B => logonserver has site A DC value and nltest /dsgetsite is ok (site B)
I restart my computer and I logon on site B => logonserver variable and nltest /dsgetsite are ok.
Why logonserver variable is not updated on first logon on site B ?
Thx
Emmanuel
Hi
Have a read of this article about sticky domain controller, not 100% sure it's your problem but does sound like it.
https://dirteam.com/sander/2008/06/24/domain-controller-stickiness-prevention/amp/
Gary.
Hi Gary,
Thx for the reply.
It does sound like it. But I don't understand which value in seconds I have to put in the GPO ?
I would set try next closest dc option and set the force rediscovery interval to one hour, the discovery process only has a small overhead so should have little impact but test it first to make sure there are no impacts in your environment.
Both of these option and the dc discovery process assumes that AD sites and services have been setup correctly and IP addresses are assigned to the correct sites.
Gary.
Hi there,
One thing I've seen is the %logonserver% variable can sometimes be inaccurate and using nltest is better.
%logonserver% shows DC from different site
------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer--