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

[Peter Gough]

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?

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. 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? 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?

Sorry for being a bit slow on this one but I'm trying to get my head around
what benefit I get from installing the client.

Thanks,

Peter

On 16/03/2009, Tomasz Chmielewski <mangoo at wpkg.org> wrote:
>
> Peter Gough schrieb:
>
>> The MS approach is that you must use transform files (.mst) to modify the
>> package. There are apps which will let you work with these (Orca and InstEd
>> both spring to mind) but there is no way to directly enter command line
>> switches in AD.
>>
>
> I see.
>
> Let's follow the market leader then - limit install commands in WPKG to
> one, and forbid any additional options/parameters ;)
>
> I added it to the TO DO list - installer should search for settingsfile in
> the same directory where the MSI file is located.
>
>
> Before it's added, as a workaround, one can add a script to GPO which will
> do:
>
> cscript \\path\to\wpkg.js /install:wpkgclient
>
>
> With a proper XML package (see http://wpkg.org/WPKG) it will install WPKG
> Client once, even if the script is started many times.
>
>
> --
> Tomasz Chmielewski
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20090316/09d3ec8c/attachment-0002.html>