Re: [wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
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 64-bit version of WPKG client available. The problem when invoking wpkg.js with 32-bit WPKG client is that invoking %WINDIR%\System32\cscript.exe will make Windows re-directing the path to %WINDIR%\SysWOW64\cscript.exe which contains the 32-bit binary. 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). Alternatively you can use 64-bit WPKG client which will be able to launch the real 64-bit process from system32\cscript.exe. In this case no wrapper is needed at all and wpkg.js will be able to access all 64-bit paths and registry entries. So wpkg.js fully supports 64-bit systems when cscript.exe is launched either by 64-bit WPKG client or any other 64-bit process. br, Rainer - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] How to not show WPKGMessage?
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 closes. This will be the only way for keeping users from pushing the power button to force a shutdown. Aborting the installations will result in an unstable system. No, because I will invoke a my application that shows a progress message box, different by application. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
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 didn't know about folder redirection... Alternatively you can use 64-bit WPKG client which will be able to launch the real 64-bit process from system32\cscript.exe. In this case no wrapper is needed at all and wpkg.js will be able to access all 64-bit paths and registry entries. 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 something like rundll* hack. thanks again riccardo -- riccardo marcon dipartimento di scienze economiche universita' di padova via del santo 33 - 35123 padova tel +39 049 827 4272 (4212) fax +39 049 827 4211 e-mail: riccardo.mar...@unipd.it - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
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 something like rundll* hack. thanks again riccardo Then there is nothing to take care of, no tweaks needed at all. The startup and logon scripts are always run in native mode, none of them is run in 32-bit mode on a 64-bit machine. --- Stefan - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Forcing a second reboot...
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 client got installed - then kaspersky AV fail saying 'reboot needed before installing' after that, machine shut down/reboot, but at next startup... the machine are without AV until next shutdown. I cannot keep machines an entire day without AV... ;((( 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 installed and work runned by hand). How can i force a reboot at next boot? ONLOGON will suffice? Thanks. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Forcing a second reboot...
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 installed - then kaspersky AV fail saying 'reboot needed before installing' after that, machine shut down/reboot, but at next startup... the machine are without AV until next shutdown. I cannot keep machines an entire day without AV... ;((( How can i force a reboot at next boot? ONLOGON will suffice? The problem is that if you force a reboot IMMEDIATELY at the next login screen, the WPKGMessage.exe window will remain stuck because the Windows Network subsystem is not completely initialized. Have you tried to launch ...\wpkg.js /synchronize /nonotify /sendStatus ? - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Forcing a second reboot...
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 installed and work runned by hand). How can i force a reboot at next boot? ONLOGON will suffice? Thanks. -- I would use ONIDLE with a delay of 5 minutes and remove the task with the installation of the new AV. --- Stefan - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
