What about the MSIRMSHUTDOWN property and maybe the REBOOT property. -----Original Message----- From: Walter Dexter [mailto:wfdex...@gmail.com] Sent: Friday, January 24, 2014 8:10 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Install busy executables at reboot - Windows 7
I have an embedded system running Windows POSReady 7 (Windows 7 for POS devices.) I have an MSI that installs a collection of .Net .exe files, VBScripts, and other stuff. Three of the executables are always running under a user account. That's just a normal thing on this device - it boots, automatically logs in as a specific user, and these executables start. I'm now trying to do a upgrade by doing a Major Upgrade of the prior MSI. That's actually working fine. My problem is that Windows Installer seems to be shutting down the executables that are always running to do the install. I've read a bit about the restart manager, and other things, but all I really want it to do is make a note that these files are to be replaced at the next reboot (which happens at 4:00 AM every day) and leave the executables running. We run the MSIs out of the usual set of Microsoft system management tools (SCCM? SCOM? It isn't my area so I don't real know) so there's no UI, and no user to say "shut them down and restart them." Honestly I haven't tried this out of the Microsoft infrastructure; I'm just firing up a "runas /user:administrator cmd.exe" and running the MSI with the /quiet flag. I guess it's possible that it will behave differently there but it seems unlikely. So is there a way to get it to do this? I've read a bit about the restart manager and messed about with various property values but none of it seemed to have any impact. If I run without /quiet it presented a variety of different dialogs telling me the programs needed to be stopped, sometimes offering to do it and restart them later. If I run with /quiet, it always quietly kills them and doesn't restart them. My fallback position is to have the MSI logoff the console - whiich is trivial to do - because it will then autolog back on and start all the programs up. It's a lot easier politically if I can hand off an MSI that the users don't notice installing. If they notice it - if the programs stop and restart, or if it logs off and back on - then we've got a lot of communication that needs to happen. Thanks for any advice! Walt ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
