Originally Posted By: Glenn Barnas
Using a specific server name in the path is not recommended, because it places all the load and responsibility on that server. Using %LOGONSERVER% in that form is questionable, as it isn't in my environment set to confirm the slashes are present (although the LOGON environment is different from the RUNNING environment). See this page for standard environment variable definitions. Unfortunately, it doesn't clarify the format.

The proper method is to use
 Code:
\\DOMAIN\NETLOGON\kix32.exe \\DOMAIN\NETLOGON\logon.kix
which will connect to the first responding DC. This is usually the same as the logon server, but a more flexible method. Note that "DOMAIN" is your local domain name. You could use %USERDOMAIN% instead of DOMAIN if you wish.

Glenn



Then again, DFS on 2000 Domains is less stable then using Sharenames on servers, and is prone to errors in the DFS system, DNS system et all. besides that %LOGONSERVER% is the server that answered the quickest. So load balancing is always in place. %LOGONSERVER% will always point to an Active server so %LOGONSERVER% is best practice in my opinion.

Anyway this is just discussing Proper use. Has nothing to do with the original problem ;-)