Difference between revisions of "WPKG Client - GUI help"
m |
m |
||
| Line 2: | Line 2: | ||
'''WPKG file path (required)''' | '''WPKG file path (required)''' | ||
| + | |||
This is where your wpkg.js is located. You can specify its location in several ways: | This is where your wpkg.js is located. You can specify its location in several ways: | ||
| Line 7: | Line 8: | ||
\\192.168.1.1\wpkg\scripts\wpkg.js<br/> | \\192.168.1.1\wpkg\scripts\wpkg.js<br/> | ||
W:\folder\wpkg.js | W:\folder\wpkg.js | ||
| + | |||
'''WPKG parameters''' | '''WPKG parameters''' | ||
| + | |||
Parameters you give to wpkg.js. By default, it is: | Parameters you give to wpkg.js. By default, it is: | ||
| Line 14: | Line 17: | ||
You shouldn't change it, unless you know what you're doing. | You shouldn't change it, unless you know what you're doing. | ||
| + | |||
'''WPKG path user''' | '''WPKG path user''' | ||
| + | |||
This is the username which will access Script file path. It is recommended that you specify here non-privileged credentials - credentials only needed to access wpkg.js and your installers. Avoid specifying privileged credentials here (domain admins etc.), as they are not needed here. | This is the username which will access Script file path. It is recommended that you specify here non-privileged credentials - credentials only needed to access wpkg.js and your installers. Avoid specifying privileged credentials here (domain admins etc.), as they are not needed here. | ||
Examples: | Examples: | ||
| Line 24: | Line 29: | ||
'''WPKG path password''' | '''WPKG path password''' | ||
| + | |||
Password for Script file path. | Password for Script file path. | ||
= WPKG execution context = | = WPKG execution context = | ||
| + | |||
By default, we start all installers as a SYSTEM user. It is the recommended setting. Whatever you put in here, the user almost certainly needs administrative privileges. If your installation scripts require access to parts of your network other than the location where the wpkg scripts are located, then you may want to put in here a user/password that has read access to those network areas in addition to admin privileges on the workstation. | By default, we start all installers as a SYSTEM user. It is the recommended setting. Whatever you put in here, the user almost certainly needs administrative privileges. If your installation scripts require access to parts of your network other than the location where the wpkg scripts are located, then you may want to put in here a user/password that has read access to those network areas in addition to admin privileges on the workstation. | ||
| − | '''User''' | + | |
| − | '''Password''' | + | '''User'''<br /> |
| + | '''Password'''<br /> | ||
Username and password of the user executing WPKG. Must have admin privileges (SYSTEM doesn't need a password). | Username and password of the user executing WPKG. Must have admin privileges (SYSTEM doesn't need a password). | ||
| Line 57: | Line 65: | ||
| − | '''WPKG user interface''' | + | '''WPKG user interface''' |
| + | |||
Setting "Show" in "Script user interface" is only needed if you want to see the installers working in the foreground - it's good for debugging.<br/> | Setting "Show" in "Script user interface" is only needed if you want to see the installers working in the foreground - it's good for debugging.<br/> | ||
When the "Show" option is disabled (default), the installers will execute in the background - recommended for normal usage (normal users shouldn't interact with installers). | When the "Show" option is disabled (default), the installers will execute in the background - recommended for normal usage (normal users shouldn't interact with installers). | ||
| + | |||
== Logon settings == | == Logon settings == | ||
| + | |||
'''Maximum logon delay''' (minutes) | '''Maximum logon delay''' (minutes) | ||
| Line 71: | Line 82: | ||
The two messages will display alternately while the user logon is being delayed. | The two messages will display alternately while the user logon is being delayed. | ||
| + | |||
== Misc settings == | == Misc settings == | ||
'''Execution priority settings''' | '''Execution priority settings''' | ||
| + | |||
Here, you can set priority for the service. Default priority (normal) is usually a good choice, but if your workstations are really old, and you don't use logon delay, you may want to choose a lower priority. | Here, you can set priority for the service. Default priority (normal) is usually a good choice, but if your workstations are really old, and you don't use logon delay, you may want to choose a lower priority. | ||
'''Stop the service when all actions are done''' | '''Stop the service when all actions are done''' | ||
| + | |||
If you check this box, the service will stop when everything is executed. | If you check this box, the service will stop when everything is executed. | ||
Revision as of 15:44, 18 August 2007
Contents
WPKG source
WPKG file path (required)
This is where your wpkg.js is located. You can specify its location in several ways:
\\server\wpkg\scripts\wpkg.js
\\192.168.1.1\wpkg\scripts\wpkg.js
W:\folder\wpkg.js
WPKG parameters
Parameters you give to wpkg.js. By default, it is:
/synchronize /nonotify /quiet
You shouldn't change it, unless you know what you're doing.
WPKG path user
This is the username which will access Script file path. It is recommended that you specify here non-privileged credentials - credentials only needed to access wpkg.js and your installers. Avoid specifying privileged credentials here (domain admins etc.), as they are not needed here. Examples:
WORKSTATION\username DOMAIN\user
WPKG path password
Password for Script file path.
WPKG execution context
By default, we start all installers as a SYSTEM user. It is the recommended setting. Whatever you put in here, the user almost certainly needs administrative privileges. If your installation scripts require access to parts of your network other than the location where the wpkg scripts are located, then you may want to put in here a user/password that has read access to those network areas in addition to admin privileges on the workstation.
User
Password
Username and password of the user executing WPKG. Must have admin privileges (SYSTEM doesn't need a password).
Advanced
General
WPKG variables
It is convenient to define a variable for the location of your setup programs. Most of the example silent installer scripts on the WPKG wiki use the variable SOFTWARE, so you should too.
Example:
Name: SOFTWARE, Value: \\server\wpkg\software
You can later use these variables in your XML files.
Additional actions
Execute before
Execute after
You can start your custom programs or scripts before and after wpkg.js is executed.
WPKG user interface
Setting "Show" in "Script user interface" is only needed if you want to see the installers working in the foreground - it's good for debugging.
When the "Show" option is disabled (default), the installers will execute in the background - recommended for normal usage (normal users shouldn't interact with installers).
Logon settings
Maximum logon delay (minutes)
If you enter a maximum logon delay, WPKG will allow the user to log on after the maximum number of minutes, even if installations are still in progress. It is probably a good idea to set a value here, in case you make a bad package that hangs indefinitely.
First message
Second message
The two messages will display alternately while the user logon is being delayed.
Misc settings
Execution priority settings
Here, you can set priority for the service. Default priority (normal) is usually a good choice, but if your workstations are really old, and you don't use logon delay, you may want to choose a lower priority.
Stop the service when all actions are done
If you check this box, the service will stop when everything is executed.
Import settings
Export settings
Here, you can import or export a XML file with WPKG Client settings.