Difference between revisions of "WPKG with Active Directory"
m |
m |
||
Line 35: | Line 35: | ||
'''cscript \\server\path\to\WPKG\wpkg.js /synchronize /quiet /nonotify''' | '''cscript \\server\path\to\WPKG\wpkg.js /synchronize /quiet /nonotify''' | ||
+ | |||
+ | |||
+ | '''NOTE!'''<br> | ||
+ | Sometimes, for an unknown reason, a group policy is not applied when it is set up and the workstations are rebooted for the first time. This may look like WPKG not working, but a second reboot proves that it's an issue with the Active Directory. | ||
+ | |||
[[category:Installation|WPKG and Active Directory]] | [[category:Installation|WPKG and Active Directory]] |
Revision as of 10:58, 4 August 2005
Below settings for Active Directory - screenshots are in German, but I think anyone who doesn't know German, but saw Active Directory will know what to do:
Next, you have to choose the right settings for the execution of scripts:
Navigate to Computerkonfiguration -> Administrative Vorlagen -> System -> Skripts.
Make sure that "Startscripts asynchron ausführen" is set to "Aktiviert".
This make sure that the user can log in, even though the software is still being installed. It's a good choice, because some unpatient users will just press Reboot button when they can't log in immediately, which can have unexpected results (software not installed properly etc.).
Next thing to set is setting "Maximale Wartezeit für Gruppenrichtlinienskripts". Default is 600 seconds (10 minutes), which can be often not enough for installing some software, or when you install more than one software package. So a safe bet is 1800 seconds (30 minutes).
The last thing you have to do, is to select a script which will start WPKG on a system start. This script is located in a batch file:
\\server\path\to\WPKG\wpkg-start.bat
and contains the folowing line which starts WPKG:
cscript \\server\path\to\WPKG\wpkg.js /synchronize /quiet /nonotify
NOTE!
Sometimes, for an unknown reason, a group policy is not applied when it is set up and the workstations are rebooted for the first time. This may look like WPKG not working, but a second reboot proves that it's an issue with the Active Directory.