I'm currently halfway through a Windows 2000 rollout and have discovered a number of small issues that need to be repaired. Rather than making Desktop Support suffer and sending them out to manually fix each machine (150 PCs) I have written a CMD script that will alter and patch the PCs using KIXtart and regini. The script is implemented through A.D.S. Group Policy.
My understanding is that Startup Scripts (as opposed to Logon Scripts) run under Local Machine SYSTEM privileges. The script alters keys in the LOCAL_MACHINE section of the registry and changes files in "Program Files"
The script runs, but the changes do not happen. The script can be run under Administrator, and then the changes happen...
Is there something about Startup Script Permissions I've missed?
Am I going nuts?
Why did they put Jar-Jar Binks in Star Wars I?
Any ideas?
My understanding is that Startup Scripts (as opposed to Logon Scripts) run under Local Machine SYSTEM privileges. The script alters keys in the LOCAL_MACHINE section of the registry and changes files in "Program Files"
The script runs, but the changes do not happen. The script can be run under Administrator, and then the changes happen...
Is there something about Startup Script Permissions I've missed?
Am I going nuts?
Why did they put Jar-Jar Binks in Star Wars I?
Any ideas?