[wpkg-users] WPKG - possibly stupid questions [SEC=UNOFFICIAL]

Tue Mar 17 08:23:22 CET 2009

Here an old one I use, no checking in it because it is implemented using runonce key during sysprep after ghosting. Has the advantage of being able to run as an inplace upgrade of wpkg

SET SRVPATH=\\wpkg\install
copy %SRVPATH%\srvany.exe %SystemRoot%\System32 /Y
copy %SRVPATH%\instsrv.exe %SystemRoot%\System32 /Y
net stop "WindowsPackager"
instsrv "WindowsPackager" REMOVE
del /Q %WINDIR%\system32\wpkg.xml
instsrv "WindowsPackager" "%SystemRoot%\System32\srvany.exe" -a .\admin -p password
%SRVPATH%reg add "HKLM\SYSTEM\CurrentControlSet\Services\WindowsPackager\Parameters" /v AppParameters /d "\\wpkg\wpkg.js /synchronize /quiet /nonotify" /f
%SRVPATH%reg add "HKLM\SYSTEM\CurrentControlSet\Services\WindowsPackager\Parameters" /v Application /d "%systemroot%\system32\cscript.exe" /f
net start "WindowsPackager"

From: wpkg-users-bounces at lists.wpkg.org [mailto:wpkg-users-bounces at lists.wpkg.org] On Behalf Of Peter Gough
Sent: 15 March 2009 11:51
To: Bart van Egmond
Cc: wpkg-users at lists.wpkg.org
Subject: Re: [wpkg-users] WPKG - possibly stupid questions

Bart,

Would it be possible to post the script? This sounds like it might be the most straightforward way to implement things.

Thanks,

Peter
On 14/03/2009, Bart van Egmond <bart at webbieworld.nl<mailto:bart at webbieworld.nl>> wrote:
Hi Pete,

I think it is not possible to use group policy to deploy WPKG at the moment ( see this bug: http://bugzilla.wpkg.org/show_bug.cgi?id=141 ). In my network, I wrote a small startup script that checks if WPKG is installed and else it runs the installation (and reboot). This is all working perfect and using this method there are no downsides.

Bart

Adam Williams wrote:
for option 3, the cscript dos client can only connect to file shares as the guest account.  also cscript doesn't exist on XP/Vista 64-bit, you have to use the GUI client.  the GUI client comes as an .msi you should be able to push out via group policy.

Peter Gough wrote:
I'm trying to get my head around the best way to implement WPKG in our environment but am struggling to work out the most appropriate options. We're running Windows Server 2003 with Active Directory and Windows XP SP3 on workstations.

I have created a share, granted read-only permissions to my 'wpkg-user' account, copied the server files into it, created some subfolders for my packages and updated the hosts.xml, packages.xml and profiles.xml files as described in the wiki.

I have also installed wpkg-client on a single workstation, configured it to point to this share and exported my settings.xml file to the same share as the other server files.

As I understand it I can now do the following:

1, push the client application to my workstations using psexec. If I do this then the workstations would run the wpkg service, access the share, check their status against the hosts.xml file to see if they are in any profile groups and would then install packages as required. Once each client connects (at startup?) they would write a local wpkg.xml file to %system%\system32.

2, as above but use Group Policy to deliver the client to workstations, however I can't work out how to apply the install switches as described in the documentation. I've tried using GP to run a script with the full command line but when I try to do this I get an error that the package is invalid.

3, use a GP script to run 'cscript \\server\path\to\WPKG\wpkg.js /synchronize /quiet /nonotify' or the wpkg-start.bat file at startup. Doing this would mean that I don't need to install the client but the downside is that I don't seem to get any wpkg dialog boxes when Windows starts - all the user sees is the generic 'running startup scripts' message from GP and given that some of the installs take a while this might lead some users to restart their machines thinking they have hung. I also can't get this to work unless I give 'authenticated users' permissions to read the shared folders which means that there doesn't seem to be any benefit to setting up the wpkg-user account.

Can somebody who has done this let me know what the benefits would be in using the client install over option 3. If there are some tangible benefits then can you let me know if it is possible to install the client using GP. If option 3 is preferred for my environment then can somebody point me towards how I might go about solving my missing dialog box issue and whether there are any other issues I need to think about prior to implementation.

Many thanks in advance,

Pete

________________________________

-------------------------------------------------------------------------

wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/

_______________________________________________

wpkg-users mailing list

wpkg-users at lists.wpkg.org<mailto:wpkg-users at lists.wpkg.org>

http://lists.wpkg.org/mailman/listinfo/wpkg-users

__________ Information from ESET NOD32 Antivirus, version of virus signature database 3936 (20090313) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

________________________________

-------------------------------------------------------------------------

wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/

_______________________________________________

wpkg-users mailing list

wpkg-users at lists.wpkg.org<mailto:wpkg-users at lists.wpkg.org>

http://lists.wpkg.org/mailman/listinfo/wpkg-users

__________ Information from ESET NOD32 Antivirus, version of virus signature database 3936 (20090313) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20090317/b49b0f71/attachment-0002.html>