[wpkg-users] Automated WPKG-Client settings update

[Kevin Keane]

As Fabrice has suggested, you could use a GPO to install WPKG. However, what I ended up doing was move away from the locally-installed WPKG. I simply have the wpkg.js file on a share on the server, wrote a small batch file that invokes it (just for convenience, you could do without), and then called that batch file via a GPO AD startup script.

> -----Original Message-----
> From: wpkg-users-bounces at lists.wpkg.org [mailto:wpkg-users-
> bounces at lists.wpkg.org] On Behalf Of Jason Oster
> Sent: Wednesday, December 16, 2009 1:40 PM
> To: wpkg-users at lists.wpkg.org
> Subject: [wpkg-users] Automated WPKG-Client settings update
> 
> Hello List,
> 
> I've got some workstations on a corporate network suffering from Bug
> 172: http://bugzilla.wpkg.org/show_bug.cgi?id=172
> 
> As you can see in the bug, I've found a workaround.  Now I need to
> deploy it to all workstations; especially the ones where WPKG fails.
> Since I cannot use WPKG directly to do the update, I'd like to find an
> alternative.
> 
> I've tried using Active Directory startup-scripts to import the
> settings.xml file, but this does not work (no error messages are
> logged, no settings are changed).  Running the script while logged into
> the workstation does update the settings properly.
> 
> I thought at first the trouble with AD startup scripts was related to
> the service running in the background.  I've tried running "net stop
> wpkgservice", killing wpkgsrv.exe and wpkgmessage.exe.  On workstations
> where WPKG works, killing these just causes the WPKG logon message to
> hang until the timeout, instead of the expected result of not seeing
> the message at all.  On all workstations, settings are still not
> updated.
> 
> Any ideas how I can either fix the AD script, or a better solution to
> deploying the settings configuration?  We also have OCS-NG installed on
> all workstations, which can deploy packages.  I can use that, in the
> worst-case scenario.