[wpkg-users] [Bug 141] Unable to install client through software group policy

[Peter Gough]

Many thanks for the quick response.

I'm still canvassing my pilot group of users about what they'd like to see
when the software is working its magic but I think the WPKG message will be
more useful than the generic Windows 'Running Startup Scripts...' message.

Unfortunately I've yet to see the WPKG logon window so if you've got any
recommendations for troubleshooting its disappearance that would be great,
otherwise I think I'm pretty much sorted!

Peter

2009/3/16 Tomasz Chmielewski <mangoo at wpkg.org>

> Peter Gough schrieb:
>
>> Does this mean that if I want to install the client using Group Policy all
>> I need to do is create a batch file with 'cscript \\path\to\wpkg.js
>> /install:wpkgclient' as the first line and as long as I've got a package
>> called 'wpkgclient' in my packages.xml file it will be installed?
>>
>
> Yes.
>
>
>  If that's the case then is there any benefit to installing the client as
>> surely I could use this process to install any software.
>>
>
> For example Samba does not have GPO and this is the main reason why WPKG
> Client was developed.
>
> But even if you use AD, you may find WPKG Client's "logon window" more
> informative. Or any other of WPKG Client's features.
> If you don't need it, using GPO only should be fine for you.
>
>
>  Additionally would it then be possible to use the 'cscript
>> \\path\to\wpkg.js /synchronize /quiet' line in a batch file and let my
>> workstations synch with the server for all of my packages without installing
>> the client?
>>
>
> Yes.
>
>
>  Does this mean that as long as my hosts.xml, packages.xml, profiles.xml
>> and settings.xml files are in the same folder as wpkg.js they would all be
>> used by the client?
>>
>
> Yes.
>
>
> --
> Tomasz Chmielewski
> http://wpkg.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20090316/2ddd4a01/attachment-0002.html>