[wpkg-announce] [Wpkg-announce] WPKG Client 1.2-rc1 released
mangoo at wpkg.org
Sun Dec 2 15:15:18 CET 2007
WPKG Client 1.2-rc1 has been released.
1. Offline mode (previously discussed as the "laptop mode")
Some of you complained that if logon delay is enabled and the server is
unreachable (because that client machine is a laptop unplugged from a
network), users have to wait for too long. This happens for several
reasons - trying to resolve DNS name, wrong routing etc.
The idea with "offline mode" is to try to reach a server for few seconds
(3 seconds default, configurable), and if it fails (no connection, no
reply etc.), discontinue further execution (skip logon delay, don't
execute any actions).
Here we have two configurable options:
* server IP or name, OR
* custom script - execute a custom scrip/program; if it exits with a
non-zero code, consider it a failure. The rationale behind a custom
script is that a client can have a connection to the server, but it's a
slow dial-up connection. Installing something big over a dial-up is
certainly not a good idea. Of course, it is up to the administrator to
write such a custom script.
Both options can have maximum waiting time specified.
NOTE: the "server IP or name" tries to connect to the server using port
139 - obviously, the server has to listen on this port.
NOTE2: the "server IP or name" will currently report a success if it
gets *any* packet back from the server (like RST). It should only report
success if it receives a SYN packet - this should change before a final
2. Configuration check/validation.
So you configured your new WPKG Client setup, exported the configuration
to 100 clients, and you notice that it doesn't work at all on any of the
machines. Why? Because you made a typo in the password (or server name,
share path, you name it).
Let's push the button and test if our settings are OK then!
Executing as DOMENA\Admin [FAILED]
Connecting to \\server\wpkg as DOMENA\me [OK]
Trying to read \\server\wpkg\wpkg.js [OK]
Trying to read \\server\wpkg\program-pre.bat [OK]
etc. for everything that can potentially fail.
3. New reboot behaviour.
Right now, when wpkg.js schedules a reboot, 2 minutes have to pass
before the reboot is actually initiated (one can see a system window
that the reboot is scheduled). But why wait and waste 2 precious minutes
if nobody is logged on?
- now, WPKG Client waits only few seconds if nobody is logged on, and
waits 2 minutes if a user is already logged on
4. WPKG service depends now on TCPIP and ADF services, as suggested by
Marco Gaiarin. This should make sure that WPKG starts when network is
already configured; not before.
== Upgrading ==
Note that on Windows, upgrading a program which is currently running can
be a bit tricky.
Obviously, one would like to upgrade WPKG Client with WPKG Client, but how?
XML file for upgrading WPKG Client should do the following:
* kill WPKGSrv.exe
* start an installation
taskkill /F /IM /WPKGsrv.exe
msiexec /qn /i "%SOFTWARE%\wpkg\WPKG Client 1.2-rc1.msi" ALLUSERS=1
Note: you have to specify a SETTINGSFILE - it's obligatory.
Note2: on Windows 2000, there is no command line tool which can kill
processes (like taskkill on XP). You have to use some 3rd party tool,
Wpkg-announce mailing list
Wpkg-announce at lists.sourceforge.net
More information about the wpkg-announce