Microsoft KB Archive/169227
Article ID: 169227
Article Last Modified on 12/8/2003
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows 95
This article was previously published under Q169227
Your Windows 95 client does not process your logon script, terminates the script prematurely, or the script stops responding (hangs) during processing.
There are several reasons that your client may not be properly processing your script file.
- There is an environment variable such as %USERNAME% specified in the logon script. Windows 95 does not understand all of the environment variables that Windows NT does. In order to have this type of functionality, you must use a third-party script application, such as KiXtart.
- There may be a batch file that has been called that has not terminated properly.
- User Manager for Domains is not configured to launch the Script file such as the file name is mistyped. This is configured in User Manager from User/Properties on the menu bar and selecting the Profile button.
- The file does not exist in the Netlogon share on every domain controller in the logon domain.
You may see different behavior on a computer running Windows NT Workstation or Windows NT Server. For full Environment Variable functionality, upgrade to Windows NT Workstation or Windows NT Server.
NOTE: For more information on KiXtart, see the following article in the Microsoft Knowledge Base:
162793 How to Setup KiXtart Logon Scripts for a Windows 95 Client
Additional query words: Win95 Global Set Winset.exe