Bart,<br>
<br>
Would it be possible to post the script? This sounds like it might be the most straightforward way to implement things.<br>
<br>
Thanks,<br>
<br>
Peter<br><br><div><span class="gmail_quote">On 14/03/2009, <b class="gmail_sendername">Bart van Egmond</b> <<a href="mailto:bart@webbieworld.nl">bart@webbieworld.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Hi Pete,<br>
<br>
I think it is not possible to use group policy to deploy WPKG at the
moment ( see this bug: <a href="http://bugzilla.wpkg.org/show_bug.cgi?id=141" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://bugzilla.wpkg.org/show_bug.cgi?id=141</a> ).
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.<br>
<br>
Bart<br>
<br>
Adam Williams wrote:
<blockquote type="cite"><div><span class="e" id="q_12004f1608266dce_1">
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.<br>
<br>
Peter Gough wrote:
<blockquote type="cite">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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
As I understand it I
can now do the following:<br>
<br>
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.<br>
<br>
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.<br>
<br>
3, use a GP script to run <b><span style="font-weight: bold;">'</span>cscript
\\server\path\to\WPKG\wpkg.js /synchronize /quiet /nonotify' </b>or
the <span style="font-weight: bold;">wpkg-start.bat </span>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.<br>
<br>
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.<br>
<br>
Many thanks in advance,<br>
<br>
Pete<br>
<pre><hr size="4" width="90%"><br>-------------------------------------------------------------------------<br>wpkg-users mailing list archives >> <a href="http://lists.wpkg.org/pipermail/wpkg-users/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.wpkg.org/pipermail/wpkg-users/</a><br>
_______________________________________________<br>wpkg-users mailing list<br><a href="mailto:wpkg-users@lists.wpkg.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">wpkg-users@lists.wpkg.org</a><br>
<a href="http://lists.wpkg.org/mailman/listinfo/wpkg-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.wpkg.org/mailman/listinfo/wpkg-users</a><br> </pre>
</blockquote>
<br>
<br></span></div>
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3936 (20090313) __________<br>
<br>
The message was checked by ESET NOD32 Antivirus.<br>
<br>
<a href="http://www.eset.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.eset.com</a><br>
<pre><span class="q"><br><hr size="4" width="90%"><br>-------------------------------------------------------------------------<br>wpkg-users mailing list archives >> <a href="http://lists.wpkg.org/pipermail/wpkg-users/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.wpkg.org/pipermail/wpkg-users/</a><br>
_______________________________________________<br>wpkg-users mailing list<br><a href="mailto:wpkg-users@lists.wpkg.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">wpkg-users@lists.wpkg.org</a><br>
<a href="http://lists.wpkg.org/mailman/listinfo/wpkg-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.wpkg.org/mailman/listinfo/wpkg-users</a></span><br><br><br><br>__________ Information from ESET NOD32 Antivirus, version of virus signature database 3936 (20090313) __________<br>
<br>The message was checked by ESET NOD32 Antivirus.<br><br><a href="http://www.eset.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.eset.com</a><br><br> </pre>
</blockquote>
<br>
</div>
</blockquote></div><br>