Difference between revisions of "WPKG"
(Making the distinction between initial deployment, and subsequent deployment using WPKG, clearer) |
(→WPKG Client Settings: More description as to why this section is relevant) |
||
| Line 48: | Line 48: | ||
</source> | </source> | ||
| − | = WPKG Client Settings = | + | == WPKG Client Settings == |
| + | |||
| + | The WPKG Client installer, above, automatically imports settings during installation. You can also specify the settings in their own package and update them separately to WPKG Client. | ||
Note - don't use quotations (") after --SETTINGSFILE - it will be interpreted directly, as part of the name. | Note - don't use quotations (") after --SETTINGSFILE - it will be interpreted directly, as part of the name. | ||
Revision as of 14:42, 26 September 2011
WPKG Client, available from http://wpkg.org/Download, is used to automatically deploy updates using WPKG on the server. It is available as a MSI package.
WPKG Client will need to be installed before it can automatically install software using WPKG.
Contents
Initial WPKG Client deployment
Running the installer directly
It can be installed silently from the command line or in a script like below:
msiexec /norestart /qn /i "%SOFTWARE%\WPKG\WPKG Client 1.3.9-x32.msi" ALLUSERS=1 SETTINGSFILE="%SOFTWARE%\WPKG\settings.xml"
Installation using wpkg.js
If you have wpkg.js configured, and WPKG Client defined in packages.xml and profiles.xml, you can run the following:
cscript \\path\to\wpkg.js /synchronize /quiet
Deploying WPKG Client using WPKG
WPKG Client
You need Windows Installer 3.1 installed to upgrade WPKG if the service is running (or any other Windows MSI package, where the software runs during the upgrade).
<package
id="wpkg_client"
name="WPKG Client"
revision="%version%"
reboot="false"
priority="10">
<variable name="version" value="1.3.14" />
<check type="uninstall" condition="versionequalto" path="WPKG" value="%version%"/>
<install cmd='msiexec /norestart /qn /i "%SOFTWARE%\WPKG\WPKG Client %version%-x32.msi" ALLUSERS=1 SETTINGSFILE="%SOFTWARE%\WPKG\settings.xml"'>
<exit code="3010" reboot="false" />
</install>
<upgrade cmd='msiexec /norestart /qn /i "%SOFTWARE%\WPKG\WPKG Client %version%-x32.msi" ALLUSERS=1 SETTINGSFILE="%SOFTWARE%\WPKG\settings.xml"'>
<exit code="3010" reboot="false" />
</upgrade>
</package>
WPKG Client Settings
The WPKG Client installer, above, automatically imports settings during installation. You can also specify the settings in their own package and update them separately to WPKG Client.
Note - don't use quotations (") after --SETTINGSFILE - it will be interpreted directly, as part of the name.
--SETTINGSFILE=\\server\some\path to settings\file.xml is fine and will be interpreted correctly.
<package
id="wpkg-settings"
name="WPKG Settings"
revision="5"
priority="5"
reboot="false"
execute="once">
<depends package-id="wpkg"/>
<install cmd='"%PROGRAMFILES%\WPKG\wpkginst.exe" --SETTINGSFILE=%SOFTWARE%\WPKG\settings.xml' />
<upgrade cmd='"%PROGRAMFILES%\WPKG\wpkginst.exe" --SETTINGSFILE=%SOFTWARE%\WPKG\settings.xml' />
<remove cmd='echo "nothing"' />
</package>