[wpkg-users] A few quick questions

[Falko Trojahn]

Hello Donny,

> Here at work, we are using an older verison of wpkg (most clients are
> using 1.0.0.8-1.0.0.18 and the server is 0.9.8) and I would like to do
> a two-fold deal here: use the current wpkg installation to push out a
> new wpkg installation and point that new installation to a new server.
> Should this be possible?
yes, just did that.
> Would I have to remove all the packages that the old installation
> installed and reinstall them with the new so it would know what it can
> control?
No. If the new Wpkg share is a identical copy of the old share ->
nothing is removed. For sure you can add new/changed
packages/profiles/hosts to the new share and as far as a client is using
the new share, it gets the new/changed packages.

But I'd suggest to carefully test the new, at first identical,  share
using a new wpkg.js version, so no problems arise due to your
packages/profiles/hosts.xml structure.

> Should I be able to remove the old client using the new client?
Yes. Just make sure that the "wpkginst" packages (see e.g.
http://wpkg.org/WPKG) on old and new server/share are identical and
point to the new server.

My recent wpkginst package looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<packages>
    <package
       id="wpkginst"
       name="WPKG Client 1.3.14"
       revision="7"
       reboot="false"
       priority="10">
     
        <check type="uninstall" condition="exists" path="WPKG" />
        <check type="file" condition="versiongreaterorequal"
path="%PROGRAMFILES%\wpkg\wpkginst.exe" value="1.0.0.22" />
     
        <install cmd='msiexec /norestart /qn /l*
c:\netinst\logs\wpkginst.log /i "%SOFTWARE%\wpkg\WPKG32-1314.msi"
ALLUSERS=1 SETTINGSFILE="%SOFTWARE%\wpkg\settings.xml"' >
            <exit code="3010" />
        </install>
     
        <upgrade cmd='msiexec /norestart /qn /l*
c:\netinst\logs\wpkginst.log /i "%SOFTWARE%\wpkg\WPKG32-1314.msi"
ALLUSERS=1 SETTINGSFILE="%SOFTWARE%\wpkg\settings.xml"' >
            <exit code="3010" />
        </upgrade>
        <upgrade cmd="%PROGRAMFILES%\WPKG\wpkginst.exe
--SETTINGSFILE=%SOFTWARE%\wpkg\settings.xml"  />
    </package>
<packages>

Perhaps you have to decide if you put a 'reboot="yes"' or
'reboot="postponed"' somewhere in the package, but we don't like our
client stations to reboot in this case (as the client is shut down
anyway when the user goes home).

HTH
Best regards,
Falko