Hi Riccardo
Riccardo Marcon wrote:
i am going to switch to last stable wpkg to handle winxp / winxp x64
environement: i don't want to use wrapper.js since it runs wpkg thru
cmd.exe and this leaves cmd.exe window exposed to users. so users can
feel free to close cmd.exe window...
There is a
wpkg-users-boun...@lists.wpkg.org scritti il 28/10/2009 16.52.43
Why would you like to disable the message box at shutdown?
Because it shows the window message everytime. And sometimes when there are
network problems (i.e. samba server down, etc) the WPKGMessage.exe remains
stuck and never
thanks Rainer,
Rainer Meier wrote:
The real system32 folder which contains the 64-bit binaries (damn, which
sick
brain invented this re-direction...) is only accessible to 64-bit processes.
That's why you need to invoke the 64-bit cscript.exe from a real 64-bit
process
(I used cmd.exe).
i don't use wpkg client, i am activating wpkg.js thru GPO:
anyway your suggestion is truly the easyest viable
alternative, i will
follow it.
it will be not so practical setting the layout of cmds to a
minimum size
or to switch exec with run in wrapper.js.
i will be exploring for
I'm moving in my organization from symantec corporate edition to
kaspersky as AV solution.
I'm doing some tests with WPKG, disinstalling old AV and installing new
one.
I'm using WPKG 'install on shutdown'.
I've done some test, and:
- symantec are correctly removed
- then, kaspersky network
wpkg-users-boun...@lists.wpkg.org scritti il 29/10/2009 12.23.53
I'm doing some tests with WPKG, disinstalling old AV and installing new
one.
I'm using WPKG 'install on shutdown'.
So do us.
I've done some test, and:
- symantec are correctly removed
- then, kaspersky network client got
I've tried to add to 'network agent' installation a row like:
install cmd='schtasks /create /tn KNA forced reboot
/sc ONSTART /ru SYSTEM /tr shutdown /r /t 5 /f' /
but does not work, probably because the 'shutdown' executed on startup
are ignored (the scheduled task are correctly
