3,217
edits
Changes
m
→GUI / graphical client installation mode
The "Script path user" credentials are used to gain access to the network share where the wpkg.js script and the configuration xml files are located. A directory to hold installation files is often also placed in the same share, as shown in the example below. If the share is set up to accept guest read access from anyone, then these credentials may not matter.
The "Script execution context" user is the user that "executes all commands". This user probably has to have administrative privileges on the local machine to be able to do most interesting installs. By default, WPKG-install sets this to SYSTEM (no password needed), which works fine as long as it does not have to access other network shares. If any of your installation scripts require access to network shares (other than the share where the script and configuration files are) then you can set this to a user that has administrative privileges on the local machine and also read (or read/write) privileges on the necessary network shares.
[[Image:Parameters2.png]]
...and change logon settings - it is possible to delay user logon when applications are installing. Of course, if applications are installed faster than the delay we specified, the user is not unnecessarily delayed.<br>
Additionally, the messages seen by the user can be changed with a custom message in any language.
[[Image:Parameters3.png]]
After that, installation and configuration on the client is complete! Reboot the machine to start the service and see if it correctly finds the configuration files and so forth. Check the Windows Events log for details of its actions.