A wrong script runs during Group Policy processing if a Windows client computer cannot connect to a domain controller

The Microsoft Windows XP-based or the Microsoft Windows Server 2003-based computer runs a wrong executable file during Group Policy processing. This symptom occurs if the Windows XP-based or the Windows Server 2003-based computer cannot connect to a domain controller.

This behavior occurs because the path variable is set to include the following items when a computer runs a logon script:

�	The SYSVOL path
�	The %systemroot% folder
�	The %systemroot%\System32 folder

If the computer cannot connect to the domain controller, the computer cannot locate the logon script in the SYSVOL folder. The computer searches for the logon script in the other folders that are listed in the path variable. If there is a file in one of these folders that has the same name as the logon script, the wrong file runs.

This behavior is by design.