http://bugzilla.wpkg.org/show_bug.cgi?id=141
--- Comment #6 from Stefan Pendl ---
Tomasz,
Which release reads the settings.xml file from the folder where the client
installer resides?
Thanks in advance,
Stefan
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
--- You
http://bugzilla.wpkg.org/show_bug.cgi?id=141
--- Comment #5 from Tomasz Chmielewski 2009-05-06 12:17:08
---
Alternatively, GPO allow starting scripts.
So one could deploy anything there.
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
--- You are receiving this
ine to use?
Not all MSI apps use MST files to set install parameters...
Chris
Date: Mon, 16 Mar 2009 09:10:37 +1100
From: pmgo...@gmail.com
To: bugzilla-dae...@bugzilla.wpkg.org
CC: wpkg-users@lists.wpkg.org
Subject: Re: [wpkg-users] [Bug 141] Unable to inst
True, although user impatience isn't limited to software installation ;-)
We've used Group Policy to assign packages and generally the process is
pretty smooth but if we're undertaking a major roll-out then we'll
communicate this to the users ahead of time and potentially schedule
installs to suit
Hello,
I searched the net and it seems there are only two options:
1) create a .MST file
2) use ORCA to change the default settings inside the .MSI file
I don't like both, so I do the installation of the WPKG client manually, since
I do not like to activate the guest account accross the
Peter Gough schrieb:
> AFAIK in MS world it doesn't really matter. You can use switches if
> you're installing packages using scripts.but if you assign a package via
> GP then the user sees a message at startup or logon telling them that
> Windows is installing (or removing) a package. Obviously
gt; Not all MSI apps use MST files to set install parameters...
>
> Chris
>
>
>
>
> --
> Date: Mon, 16 Mar 2009 09:10:37 +1100
> From: pmgo...@gmail.com
> To: bugzilla-dae...@bugzilla.wpkg.org
> CC: wpkg-users@lists.wpkg.org
> Subject: Re: [wpkg-use
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 W
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
o roll out the WPKG client
should be fine to use?
Not all MSI apps use MST files to set install parameters...
Chris
Date: Mon, 16 Mar 2009 09:10:37 +1100
From: pmgo...@gmail.com
To: bugzilla-dae...@bugzilla.wpkg.org
CC: wpkg-users@lists.wpkg.org
Subject: Re: [wpkg-users] [Bug 141]
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 ca
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.
Peter
On 16/03/2009, bugzilla-dae...@bugzilla.wpkg.org <
bu
http://bugzilla.wpkg.org/show_bug.cgi?id=141
--- Comment #4 from Tomasz Chmielewski 2009-03-15 14:01:44
---
I think we could do it.
Although it's really hard for me to believe that Active Directory really does
not allow setting parameters to MSI packages it deploys via GPO.
What a system
http://bugzilla.wpkg.org/show_bug.cgi?id=141
Falko Trojahn changed:
What|Removed |Added
CC||ftroj...@smi-softmark.de
--- Comment #3 fr
http://bugzilla.wpkg.org/show_bug.cgi?id=141
--- Comment #2 from Stefan Pendl 2009-01-27 11:12:18
---
Hi Tomasz,
there is no way to add command line parameters for the software group policy.
I will check, if I can find something about this at Microsoft.
I will check back with the results.
http://bugzilla.wpkg.org/show_bug.cgi?id=141
--- Comment #1 from Tomasz Chmielewski 2009-01-26 21:16:07
---
Then you found a bug in Active Directory! Did you report it to Microsoft's
bugzilla?
Seriously, you need to add settingsfile path, i.e.:
SETTINGSFILE="%SOFTWARE%\WPKG\settings.xml"
16 matches
Mail list logo
