<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18876"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff face=Calibri><SPAN
class=619084022-07022010>Rainer, thanks for your information,
however I understand how WPKG works, and the WPKG client 1.3.9 is
definitely supposed to be able to read from STDIN and support
/sendStatus</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff face=Calibri><SPAN
class=619084022-07022010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff face=Calibri><SPAN
class=619084022-07022010><B>21-Sep-2009</B> </DIV>
<DIV dir=ltr align=left>
<P>WPKG Client 1.3.9 has been released.<BR></P>
<P>Small summary (not to be complete):<BR></P>
<UL>
<LI>32-bit and 64-bit client versions </LI>
<LI><STRONG>support for /sendStatus switch of wpkg.js 1.1.x (display the
progress in the message window) </STRONG></LI></UL></SPAN></FONT></DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff face=Calibri>The
question is, why doesn't it work? It certainly has nothing to do with VC++. I'm
thinking it is more to do with a service that our Group Policy is blocking. Are
there dependant services required?</FONT></SPAN></DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff
face=Calibri></FONT></SPAN> </DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff face=Calibri>Regarding
logon/shutdown delay, this is most certainly a required feature, for a number of
reasons:</FONT></SPAN></DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff
face=Calibri></FONT></SPAN> </DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff face=Calibri>1)
Much of our software requires a reboot. We simply cannot automatically
reboot production users during the day, no matter how much "warning" you give
people.</FONT></SPAN></DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff face=Calibri>2) Much of
our software takes 5-10 minutes to install, however the icons
sometimes become available before installation completes. Hence, users can
"run" the software before its finished installing, and it will crash, sometimes
ruining the actual installation.</FONT></SPAN></DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff face=Calibri>3)
Installing software slows down the computer and network connection,
thus interfering with production users.</FONT></SPAN></DIV>
<DIV><SPAN class=619084022-07022010></SPAN><SPAN class=619084022-07022010><FONT
color=#0000ff face=Calibri></FONT></SPAN> </DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff face=Calibri>I am
curious if Windows 7 will support logon delay, or at least shutdown delay.
Status messages are more important if we use the Execute at System start-up, but
we could easily swap to Execute on shutdown. However Execute on shutdown will of
coarse only work with a shutdown delay :)</FONT></SPAN></DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff
face=Calibri></FONT></SPAN> </DIV>
<DIV><SPAN class=619084022-07022010><FONT color=#0000ff face=Calibri>We will be
migrating our 300 users to Windows 7 in the near future, so WPKG compatibility
with that is quite an important factor... I guess we need to start
testing.</FONT></SPAN></DIV>
<DIV><STRONG><FONT color=#0000ff face=Calibri></FONT></STRONG><STRONG><FONT
color=#0000ff face=Calibri></FONT></STRONG><STRONG><FONT color=#0000ff
face=Calibri></FONT></STRONG><STRONG><FONT color=#0000ff
face=Calibri></FONT></STRONG><BR> </DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Peter Gough [mailto:pmgough@gmail.com]
<BR><B>Sent:</B> Friday, 5 February 2010 6:55 PM<BR><B>To:</B> Rainer
Meier<BR><B>Cc:</B> wpkg-users@lists.wpkg.org<BR><B>Subject:</B> Re:
[wpkg-users] /sendStatus command not working<BR></FONT><BR></DIV>
<DIV></DIV>Many thanks for the clarification. I've played around again with this
today and it looks like adding '/sendStatus' to the command line options in WPKG
Client and setting the sendStatus value to 'true' in the 'settings.xml' file on
the server gives me information messages together with the regular message
box.<BR><BR>This is on Windows XP SP3 clients using 1.3.6 WPKG
Client.<BR><BR>I've tried updating my test clients to 1.3.9 but get an error
messsage relating to the WPKG service. I understand from previous correspondance
that there are known issues with this version on SP3 - hopefully these will be
ironed out at some stage in the future but I'm pretty happy for the time being
with what I've got working.<BR><BR>Many thanks for all of your hard work in
providing WPKG; it really is much appreciated!<BR><BR>Peter<BR><BR>
<DIV class=gmail_quote>On 5 February 2010 17:12, Rainer Meier <SPAN
dir=ltr><<A href="mailto:r.meier@wpkg.org">r.meier@wpkg.org</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Hi Peter,<BR>
<DIV class=im><BR>On 05.02.2010 01:34, Peter Gough wrote:<BR>> I just
wondered if you couid confirm what your users see on the screen<BR>> when
the workstation is shutting down. I've never been able to get<BR>> anything
to display apart from the alternating status messages despite<BR>> trying
to set this up as you have described.<BR>><BR>> I've got this set in the
Client's WPKG parameters:<BR>><BR>> /synchronize /nonotify
/quiet<BR>><BR>> I've got the WPKG user interface dialog box unticked
and I've set<BR>> sendStatus value in the config.xml file on my server to
'true'.<BR>><BR>> Any thoughts?<BR><BR></DIV>First a few words for
better understanding. WPKG is split into a "Server" and a<BR>"Client" Part.
The Server-Part is implemented in wpkg.js. Well, actually it's<BR>not a real
server but rather a script executed on the client. The Client part is<BR>"WPKG
Client" which just executes wpkg.js depending on your settings. WPKG<BR>Client
is optional and you might also invoke wpkg.js using any other
method.<BR>However WPKG Client offers a couple of nice features like running
wpkg.js at<BR>startup/shutdown or blocking user input during wpkg.js
execution.<BR><BR>Such features need to be implemented on a quite low level in
the operating<BR>system. Currently logon delay only works on Windows prior to
Vista. The logon<BR>delay feature allows you to display messages (alternating)
to the user.<BR><BR>It was intended to extend this static message display into
a dynamic status<BR>update shown to the user. However there are a couple of
technical limitations.<BR>First of all wpkg.js will have to communicate with
WPKG client in order to<BR>update the status displayed to the user. Remember:
wpkg.js executes the job and<BR>WPKG client prevents user input and displays
messages.<BR>Unfortunately IPC technologies are quite limited from
WSH/JScript. So for the<BR>moment wpkg.js only supports writing the status
updates to STDOUT if /sendStatus<BR>is enabled (or sendStatus within
config.xml is switched on).<BR><BR>Honestly I am not fully sure if WPKG Client
already supports reading from STDIN<BR>and showing these messages to the user.
Personally I prefer not to block users<BR>and run WPKG silently in the
background. Another reason for me is that<BR>logon/shutdown delay is not
something easily achievable by standard API and as<BR>Vista shows it might be
even blocked/prevented by the OS. I am using /sendStatus<BR>usually when I run
WPKG from a memory-stick to update offline nodes. So I can<BR>see the progress
of package installation within the console window.<BR><BR>So please note that
config.xml controls behavior or wpkg.js but sendStatus will<BR>only make
wpkg.js to print status information to the console. If this<BR>information is
picked up and displayed to the user depends on the method used to<BR>run
wpkg.js (console, client application which picks up the
output).<BR><BR>br,<BR><FONT
color=#888888>Rainer<BR></FONT></BLOCKQUOTE></DIV><BR></BODY></HTML>