Changes

The WPKG Installer will create a windows service on the client machine. The service will run at system boot, and read the configuration xml files from the wpkg WPKG network share. The service will be created to run as the local SYSTEM user (the other user credentials discussed below are different).

The "Script WPKG 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 WPKG 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 Installer 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.

Setting "Show" in "Script WPKG user interface" is only needed if we want to see the installers working in the foreground - it's good for debugging.<br>