Article ID: 176197 - View products that this article applies to.
This article was previously published under Q176197
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
When the logon script runs, a dialog box is presented until the script finishes. Many administrators want a way to minimize this dialog box while it is running, or have it perform in the background so users aren't aware of the logon script. Because Windows does not use the LMSCRIPT file and you do not want to change the default properties of Cmd.exe, other methods must be used.
Create a batch file that calls the actual logon script. Using Notepad, create a file that has the following entry:
Save the batch file and specify this file as the logon script name for the user accounts in User Manager for Domains. Now, when the users log on to Windows, they will initially run the above batch file, which, in turn, calls the logon script and starts it minimized. The last entry in the real logon script file must be EXIT so the file will close properly.
This works great and solves the problem of users seeing the commands being processed in the actual logon script.
Windows for Workgroups clients do not understand the START command, so this won't work if you have those clients. Also, the initial call to the logon script designated in User Manager for Domains still creates a logon dialog box. The box disappears almost immediately, but may still cause a problemfor the administrator who does not want the user to see anything out of the ordinary when logging on. To have the logon script dialog box minimized during logon and support all clients, do the following:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
After that key is deleted, the default dialog box will once again be presented for Windows with that same title.
Because logon scripts reside in the NetLogon share of every domain controller, the chances are good that you may run the logon script from a different server than the one used in the above example.
Your file is represented in the registry as _ComputerName_NETLOGON_LogonScript. The computer name obviously won't be the same if you are validated by a different controller. Here are two methods to solve this problem.
Article ID: 176197 - Last Review: March 27, 2007 - Revision: 2.6