Our Windows NT 4, SP3 PCs run a login script in a DOS window; however, users interrupt the script once the icons appear on the desktop, causing all sorts of problems relating to the bits of the script that don't run. Users either use <Ctrl C> or click on the crosshairs to shut down the script. Can anyone tell me how to make the script tamperproof ?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How can I prevent users from terminating NT login script ?
- Thread starter TFinn
- Start date
Copied from here
And finally, how to prevent users from terminating the logon script window prior to completion?
One approach is by way of System Policies. In User policy, there is an option to "Run logon scripts synchronously", under the "Windows NT System" in the Profile Policy Editor. What "Run logon scripts synchronously" means is "Wait for the logon scripts to complete before starting the user's shell."
Another way to prevent users from interrupting the logon script is to use KixTART utility. The KiXtart (Kix32.exe) tool included on the Windows NT Server Resource Kit version 4.0 CD-ROM provides some networking functionality for Windows NT that is not built-in to the Windows NT user interface. KiXtart is a login script processor and enhanced batch language for Windows NT. However, depending on how the logon script is started (for example, from a batch file) there still may be a short period of time between when the batch file calls the logon script that the user may be able to cancel the batch. More information on KiXtart can be found in Knowledge Base article "Installing and Using the KiXtart Login Processor Tool."
And finally, how to prevent users from terminating the logon script window prior to completion?
One approach is by way of System Policies. In User policy, there is an option to "Run logon scripts synchronously", under the "Windows NT System" in the Profile Policy Editor. What "Run logon scripts synchronously" means is "Wait for the logon scripts to complete before starting the user's shell."
Another way to prevent users from interrupting the logon script is to use KixTART utility. The KiXtart (Kix32.exe) tool included on the Windows NT Server Resource Kit version 4.0 CD-ROM provides some networking functionality for Windows NT that is not built-in to the Windows NT user interface. KiXtart is a login script processor and enhanced batch language for Windows NT. However, depending on how the logon script is started (for example, from a batch file) there still may be a short period of time between when the batch file calls the logon script that the user may be able to cancel the batch. More information on KiXtart can be found in Knowledge Base article "Installing and Using the KiXtart Login Processor Tool."
- Thread starter
- #3
bierhunter
IS-IT--Management
I'd like to add, we use Kixtart at work. It's great! If someone closes the script window prematurely, it kicks them back to the ctrl-alt-del screen.
Also, you can use kixtart for a wide variety of scripting uses and control many properties of the workstations.
Also, you can use kixtart for a wide variety of scripting uses and control many properties of the workstations.
- Thread starter
- #5
- Status
