There is a third party vendor product's which can watch these process's and act accordingly.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller, Todd Sent: Tuesday, March 04, 2014 10:41 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: User logs out during package based install It turns out that any process running with desktop interaction will terminate upon user logout/shutdown. Even though a process is running as SYSTEM, if you have it set to interact with the user desktop, the process will terminate immediately upon user logout. This is not specific to SCCM. You can check this out by launching notepad.exe as SYSTEM using psexec with system & interactive flags. Once the process is running, you can see in TaskMgr that it is running as SYSTEM. If the logged in user logs out, all process running in the userland desktop are terminated even though the process is not running as that user. If on the other hand, you launch Notepad.exe as system without setting the interactive flag, the Notepad window will not be visible to the logged in user and the process will survive a logout (but not a shutdown obviously.) This affects any SCCM deployment that is set to run interactively. If the user logs out during dialogs or the installation process, the installation process will terminate. It is possible to write Autoit or other scripting wrappers which subscribe to and block shutdown/logout events. I am looking into this option to make my installers more robust. The other option, I think, might be to rely on SCCM notification processes and reboot notifications and mark package installations as non-interactive. It is not flexible enough for our environment, but it probably works great in some scenarios. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller, Todd Sent: Monday, March 03, 2014 3:36 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] User logs out during package based install I have a package (old style) that I am using SCCM to deploy. The advertisement is set to run whether or not a user is logged in, is set to run with admin rights and is set to allow interaction with the user. The advertisement runs a program called Installer.exe which is a custom Autoit script. When installer.exe kicks off according to the advertisement, Installer.exe can be seen running as SYSTEM, as expected. This is verified by Taskmgr and PSList. If the user logs out while Installer.exe is running, then the process exits. This is unexpected. Do you happen to know, if a user logs out while an advertisement is running, should I expect SCCM to kill the process? What do you think might be killing the EXE? The user doesn't have rights to the process, so I don't think their logout should be effecting the process, but it seems like it does. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of this email address. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
