Recently, I needed to shutdown one of our domain controllers. At the end of the day I logged out of the network. Next day I started my computer and logged in, but when my logon script tried to execute it froze and eventually timed out. After reviewing my system I noticed that the LOGONSERVER environment variable was pointing to the server I took off line the day before. Our network logon scripts are bat files and use the LOGONSERVER variable throughout. I tried many times to reset that variable until I finally found it in the "Volatile Environment" registry key. Once I changed it to the DC that is accessible, I was able to successfully log on and run my script. I realize it's not often that a DC would be offline, but I would think this variable should auto update whenever a user gets a response back from the DC that answers the call for authentication. I must have something configured incorrectly but I don't know where to go to fix this. Can you please point me in the right direction? Thank you.
↧