Difference between revisions of "WPKG-GP"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
(package to replace client with wpkg-gp)
Line 30: Line 30:
  
  
 +
=Installing with wpkg v2=
 +
 +
I have another way to work this, because i install with wpkg but without WPKG Client, may be is helps someone.
 +
 +
This package definition works with the latest wpkg.js (1.3 as of this writting) running on the server, it install the version acording it's architecture:
 +
 +
<source lang="xml">
 +
<package id="wpkg-gp" name="Wpkg-GP" revision="%version%">
 +
 +
    <variable name="version" value="0.15" />
 +
    <variable name="EXE" value="%SOFTWARE%\wpkg\Wpkg-GP-0.15_x86.exe" architecture="x86" />
 +
    <variable name="EXE" value="%SOFTWARE%\wpkg\Wpkg-GP-0.15_x64.exe" architecture="x64" />
 +
 +
    <check type="uninstall" condition="versiongreaterorequal" path="Wpkg-GP %version% .*" value="%version%"/>
 +
 +
    <install cmd="%EXE% /S /INI %SOFTWARE%\wpkg\Wpkg-GP.ini">
 +
        <exit code="3010" reboot="delayed" />
 +
    </install>
 +
 +
    <upgrade cmd="%EXE% /S /INI %SOFTWARE%\wpkg\Wpkg-GP.ini">
 +
        <exit code="3010" reboot="delayed" />
 +
    </upgrade>
 +
</package>
 +
</source>
 +
 +
for installing WPKG-GP for the first time, i just run
 +
<code>cscript \\server\path\to\wpkg.js /synchronize</code>
 +
on the 'Run' dialog box of the Windows Client.
  
  

Revision as of 21:00, 9 May 2012

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.

Bootup-windows-7-small.png

Installing with wpkg

If you have already installed the standard WPKG Client, you can use a package to replace it with WPKG-GP.

This example installs version 0.15, with a configuration defined through a wpkg-GP.ini file. Then it uninstalls the standard Wpkg Client.

<package id="wpkg-gp" name="Wpkg-GP" revision="%version%">

    <variable name="version" value="0.15" />

    <check type="uninstall" condition="versiongreaterorequal" path="Wpkg-GP %version% .*" value="%version%"/>

    <install cmd="%SOFTWARE%\wpkg-gp\Wpkg-GP-0.15_x64.exe /S /INI %SOFTWARE%\wpkg-gp\Wpkg-GP.ini">
        <exit code="3010" reboot="delayed" />
    </install>
    <install cmd='msiexec /x "%SOFTWARE%\wpkg\WPKG Client 1.3.14-x64.msi" /qn /norestart' />

    <upgrade cmd="%SOFTWARE%\wpkg-gp\Wpkg-GP-0.15_x64.exe /S /INI %SOFTWARE%\wpkg-gp\Wpkg-GP.ini">
        <exit code="3010" reboot="delayed" />
    </upgrade>
</package>


Installing with wpkg v2

I have another way to work this, because i install with wpkg but without WPKG Client, may be is helps someone.

This package definition works with the latest wpkg.js (1.3 as of this writting) running on the server, it install the version acording it's architecture:

<package id="wpkg-gp" name="Wpkg-GP" revision="%version%">

    <variable name="version" value="0.15" />
    <variable name="EXE" value="%SOFTWARE%\wpkg\Wpkg-GP-0.15_x86.exe" architecture="x86" />
    <variable name="EXE" value="%SOFTWARE%\wpkg\Wpkg-GP-0.15_x64.exe" architecture="x64" />

    <check type="uninstall" condition="versiongreaterorequal" path="Wpkg-GP %version% .*" value="%version%"/>

    <install cmd="%EXE% /S /INI %SOFTWARE%\wpkg\Wpkg-GP.ini">
        <exit code="3010" reboot="delayed" />
    </install>

    <upgrade cmd="%EXE% /S /INI %SOFTWARE%\wpkg\Wpkg-GP.ini">
        <exit code="3010" reboot="delayed" />
    </upgrade>
</package>

for installing WPKG-GP for the first time, i just run cscript \\server\path\to\wpkg.js /synchronize on the 'Run' dialog box of the Windows Client.


External Links