WISE Execute program action
Hi there. I've got a WISE EXE that calls a VBS reboot handler at the end. Everything works fine, except when a target PC is in a 'locked' state (win2k, crtl-alt-delete, lock computer). The distribution program calls my WISE EXE under the system context, and it executes there fine... Except when it goes to call my execute program action (which is calling wscript.exe and a path to a vbs), and it doesn't launch it.
After I set wscript.exe to always launch with system context privileges, it started to work. My concern is: If a WISE EXE was launched under system context, why wouldn't it's child processes inherit that account privilege?
Any thoughts?
After I set wscript.exe to always launch with system context privileges, it started to work. My concern is: If a WISE EXE was launched under system context, why wouldn't it's child processes inherit that account privilege?
Any thoughts?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Robo Scripter
20 years ago
A bit more specific information would be nice. I’m assuming that you’re talking about an msi installation of some application that you have a required reboot at the end. If this is the case then I would suggest the you use a ScheduledReboot Action instead of your wise exe.
If this is not a msi installation then could you please provide a bit more information.
Regards,
If this is not a msi installation then could you please provide a bit more information.
Regards,
Posted by:
gswitzer
20 years ago
Thanks for the reply.. It's not a MSI. It's a WiseScript EXE, and the function is 'Execute Program" The 'reboot handler' is a vbs script being chunked by wscript.exe. The reason behind it is that in our enterprise, we have to give the users the option of scheduling a reboot when it suits them. So to accommodate that, I wrote a generic reboot handler for these types of installations.
This particular EXE is the new IE security patch. We are bound to get critical patches out in a very short order, regardless of the current PC state (With the caveat of the scheduled reboot). So, to add the functionality we need, we wrap the patch in a WSE script, and go from there.
Our distribution system delivers and launches the exe, under the system context. It all executes fine except when the client PC is locked. In that scenario, it still executes, but when it goes to execute the 'reboot handler' (sys32%\wscript.exe %path to vbsfile%) it just kinda of glosses over it. I found that when I added wscript.exe's path to the reg key: HKLM\software\Microsoft\WindowsNT\Currentversion\winlogon\sytem=%sys32%\wscript.exe, the problem went away. This is due to the OS intercepting the launch of wscript.exe and subsequently running it under the system context. That led me to believe that for some reason, my WISE exe was calling it with a user context level permission.
I would think that any child program that executed from within a WISE EXE that running under the system account would inherit the account privileges from it's parent.
Hope that helps clarify it a bit... Thanks again
This particular EXE is the new IE security patch. We are bound to get critical patches out in a very short order, regardless of the current PC state (With the caveat of the scheduled reboot). So, to add the functionality we need, we wrap the patch in a WSE script, and go from there.
Our distribution system delivers and launches the exe, under the system context. It all executes fine except when the client PC is locked. In that scenario, it still executes, but when it goes to execute the 'reboot handler' (sys32%\wscript.exe %path to vbsfile%) it just kinda of glosses over it. I found that when I added wscript.exe's path to the reg key: HKLM\software\Microsoft\WindowsNT\Currentversion\winlogon\sytem=%sys32%\wscript.exe, the problem went away. This is due to the OS intercepting the launch of wscript.exe and subsequently running it under the system context. That led me to believe that for some reason, my WISE exe was calling it with a user context level permission.
I would think that any child program that executed from within a WISE EXE that running under the system account would inherit the account privileges from it's parent.
Hope that helps clarify it a bit... Thanks again
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.