<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.gmailquote
{mso-style-name:gmail_quote;}
span.e
{mso-style-name:e;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.q
{mso-style-name:q;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>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<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>SET SRVPATH=\\wpkg\install<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>copy %SRVPATH%\srvany.exe %SystemRoot%\System32 /Y<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>copy %SRVPATH%\instsrv.exe %SystemRoot%\System32 /Y<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>net stop "WindowsPackager"<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>instsrv "WindowsPackager" REMOVE<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>del /Q %WINDIR%\system32\wpkg.xml<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>instsrv "WindowsPackager" "%SystemRoot%\System32\srvany.exe"
-a .\admin -p password<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>%SRVPATH%reg add
"HKLM\SYSTEM\CurrentControlSet\Services\WindowsPackager\Parameters"
/v AppParameters /d "\\wpkg\wpkg.js /synchronize /quiet /nonotify" /f<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>%SRVPATH%reg add "HKLM\SYSTEM\CurrentControlSet\Services\WindowsPackager\Parameters"
/v Application /d "%systemroot%\system32\cscript.exe" /f<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>net start "WindowsPackager"<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> wpkg-users-bounces@lists.wpkg.org
[mailto:wpkg-users-bounces@lists.wpkg.org] <b>On Behalf Of </b>Peter Gough<br>
<b>Sent:</b> 15 March 2009 11:51<br>
<b>To:</b> Bart van Egmond<br>
<b>Cc:</b> wpkg-users@lists.wpkg.org<br>
<b>Subject:</b> Re: [wpkg-users] WPKG - possibly stupid questions<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>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<o:p></o:p></p>
<div>
<p class=MsoNormal><span class=gmailquote>On 14/03/2009, <b>Bart van Egmond</b>
<<a href="mailto:bart@webbieworld.nl">bart@webbieworld.nl</a>> wrote:</span><o:p></o:p></p>
<div>
<p class=MsoNormal>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">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: <o:p></o:p></p>
<div>
<p class=MsoNormal><span class=e>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.</span><br>
<br>
<span class=e>Peter Gough wrote: <o:p></o:p></span></p>
<p class=MsoNormal>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>'cscript \\server\path\to\WPKG\wpkg.js
/synchronize /quiet /nonotify' </b>or the <b>wpkg-start.bat </b>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<o:p></o:p></p>
<pre style='text-align:center'>
<hr size=4 width="90%" align=center>
</pre><pre><br>
-------------------------------------------------------------------------<br>
wpkg-users mailing list archives >> <a
href="http://lists.wpkg.org/pipermail/wpkg-users/" target="_blank">http://lists.wpkg.org/pipermail/wpkg-users/</a><br>
<br>
<o:p></o:p></pre><pre>_______________________________________________<br>
wpkg-users mailing list<br>
<a href="mailto:wpkg-users@lists.wpkg.org" target="_blank">wpkg-users@lists.wpkg.org</a><br>
<br>
<o:p></o:p></pre><pre><a
href="http://lists.wpkg.org/mailman/listinfo/wpkg-users" target="_blank">http://lists.wpkg.org/mailman/listinfo/wpkg-users</a><br>
<o:p></o:p></pre>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
</div>
<p class=MsoNormal>__________ 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">http://www.eset.com</a><o:p></o:p></p>
<pre><span class=q><o:p> </o:p></span></pre><pre style='text-align:center'><span
class=q>
<hr size=4 width="90%" align=center>
</span></pre><pre><br>
<span class=q>-------------------------------------------------------------------------</span><br>
<span class=q>wpkg-users mailing list archives >> <a
href="http://lists.wpkg.org/pipermail/wpkg-users/" target="_blank">http://lists.wpkg.org/pipermail/wpkg-users/</a></span><br>
<br>
<span class=q><o:p></o:p></span></pre><pre><span class=q>_______________________________________________</span><br>
<span class=q>wpkg-users mailing list</span><br>
<span class=q><a href="mailto:wpkg-users@lists.wpkg.org" target="_blank">wpkg-users@lists.wpkg.org</a></span><br>
<br>
<span class=q><o:p></o:p></span></pre><pre><span class=q><a
href="http://lists.wpkg.org/mailman/listinfo/wpkg-users" target="_blank">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>
<o:p></o:p></pre><pre><br>
The message was checked by ESET NOD32 Antivirus.<br>
<br>
<a href="http://www.eset.com" target="_blank">http://www.eset.com</a><br>
<br>
<o:p></o:p></pre>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>