Difference between revisions of "WPKG-GP"
(Added separate deployment of WPKG-GP Configuration File and other improvements) |
(→Deploy WPKG-GP with WPKG: Added remove line) |
||
Line 26: | Line 26: | ||
</install> | </install> | ||
− | + | <upgrade include="install" /> | |
+ | |||
+ | <remove | ||
+ | cmd='"%PROGFILES%\WPKG-GP\uninstall.exe" /S' /> | ||
</package> | </package> |
Revision as of 09:52, 6 March 2014
This article is a stub. You can help WPKG Wiki by expanding it.
WPKG-GP hooks into the Group Policy Extensions (GPE) interface available in Windows (the one saying "Applying Group Policies" at boot up), and executing wpkg.js, providing some feedback to the user via the interfaces made available by GPE. This gets around the issue in Windows Vista/7, where delayed login is unavailable owing to the way Windows Vista's security architecture is structured.
Contents
Deploy WPKG-GP with WPKG
This example installs version 0.16, with a configuration defined through a wpkg-GP.ini file. Unless you already have WPKG Client installed, you will have to initially deploy WPKG-GP somehow, such as manually.
<package id="wpkg-gp" name="Wpkg-GP" revision="%version%">
<variable name="VERSION" value="0.16" />
<variable name="ARCHITECTURE" value="x86" architecture="x86" />
<variable name="ARCHITECTURE" value="x64" architecture="x64" />
<check type="uninstall" condition="versiongreaterorequal" path="Wpkg-GP %version% .*" value="%version%"/>
<!-- Install WPKG-GP -->
<!-- wpkg-gp.ini contains settings such as location of wpkg.js, username/password to connect as, and the %SOFTWARE% environment variable -->
<install cmd="%SOFTWARE%\wpkg-gp\Wpkg-GP-%VERSION%_%ARCHITECTURE%.exe /S /INI %SOFTWARE%\wpkg-gp\Wpkg-GP.ini">
<exit code="3010" reboot="delayed" />
</install>
<upgrade include="install" />
<remove
cmd='"%PROGFILES%\WPKG-GP\uninstall.exe" /S' />
</package>
Replace WPKG Client with WPKG-GP
If you already have WPKG Client installed, you can add the following, to the package above, to replace WPKG Client with WPKG-GP:
<!-- Uninstall WPKG Client -->
<install cmd='msiexec /x "%SOFTWARE%\wpkg\WPKG Client 1.3.14-%ARCHITECTURE%.msi" /qn /norestart' />
WPKG-GP Configuration File
WPKG-GP's configuration is saved in %PROGRAMFILES%\WPKG-GP\Wpkg-gp.ini. WPKG-GP configuration can be updated by copying a new version of this file to that location, enabling its configuration to be updated without reinstalling he program. wpkg-gp.ini contains the location of wpkg.js, the username/password to connect, and the %SOFTWARE% and %WPKGROOT% environment variables.
WPKG Package For WPKG-GP Configuration File
This checks to see if the configuration file in %SOFTWARE%\wpkg-gp\ differs to that currently deployed in the Program Files directory.
<package
id="wpkg-gp-config"
name="WPKG-GP Configuration"
revision="3">
<-- WPKG-GP can be either 32-bit or 64-bit -->
<variable architecture="x86" name="PROGFILES" value="%PROGRAMFILES%" />
<variable architecture="x64" name="PROGFILES" value="%PROGRAMFILES(X86)%" />
<check
type="file"
condition="datemodifyequalto"
path="%PROGFILES%\WPKG-GP\Wpkg-gp.ini"
value="@%SOFTWARE%\wpkg-gp\Wpkg-gp.ini"/>
<install cmd='%COMSPEC% /c copy /Y "%SOFTWARE%\wpkg-gp\Wpkg-gp.ini" "%PROGFILES%\WPKG-GP\Wpkg-gp.ini" '/>
<upgrade include="install" />
<!-- Should there be a remove line? If we leave it without a config file then it won't function, if we do nothing then it will never be removed as the config file check remains positive. -->
<remove />
</package>