Got it!

I haven't worked out all the details but changing the MSIRMSHUTDOWN
property to "0" makes it do what I wanted. Note that in this case the .exe
files that I want to keep running aren't actually being modified. Our
deployment folks just don't like to deal with distribution of patches;
they'd rather send out a full MSI.

Here are the properties I have set, in case some future reader comes upon
this thread. I think it's only the last three that matter but I haven't dug
through all of the Reinstall... ones.

<Property Id="REBOOT" Admin="yes" Secure="yes">ReallySuppress</Property>
<Property Id="ARPNOMODIFY" Value="1" />
<Property Id="ARPNOREPAIR" Value="1" />
<Property Id="DISABLEROLLBACK" Value="1" />
<Property Id="ReinstallFileOlderVersion" Value="o" />
<Property Id="ReinstallFileVersion" Value="o" />
<Property Id="ReinstallRepair" Value="r" />
* <Property Id="MSIRESTARTMANAGERCONTROL" Value="0" /> *
* <Property Id="MSIRMSHUTDOWN" Value="2" /> *
* <Property Id="MSIDISABLERMRESTART" Value="0" />*



On Sun, Jan 26, 2014 at 7:00 AM, Walter Dexter <wfdex...@gmail.com> wrote:

> I tried that. Disable just makes it use the older method instead of the
> restart manager. In practical terms, it's just a different dialog box if
> you don't use the /quiet option, and no difference in behavior if you do.
>
> I'm going to try actually having the restart manager restart them and see
> how disruptive that is,but it wouldn't surprise me if the default quiet
> behavior is to not restart.
> On Jan 25, 2014 12:42 PM, "Rob Mensching" <r...@robmensching.com> wrote:
>
>> Maybe MSIRESTARTMANAGERCONTROL is the one that would actually help. Your
>> example shows a "0". You might use "Disable". Ultimately, all this is
>> documented here:
>> http://msdn.microsoft.com/en-us/library/aa372059(v=vs.85).aspx
>>
>> -----Original Message-----
>> From: Walter Dexter [mailto:wfdex...@gmail.com]
>> Sent: Saturday, January 25, 2014 9:12 AM
>> To: General discussion about the WiX toolset.
>> Subject: Re: [WiX-users] Install busy executables at reboot - Windows 7
>>
>> I tried MSIRMSHUTDOWN = 2, and REBOOT is = ReallySuppress. Behavior is
>> the same - with /quiet it just quietly kills the exe off, without /quiet it
>> asks me what to do (the Reinstall Manager prompt.)
>>
>> I hate to drop a giant XML bomb on the forum, but here's a (trimmed down,
>> believe it or not) WXS file.
>>
>> If you (Rob) or anyone has some advice, I sure appreciate it. Otherwise I
>> guess I'll just do the console logoff as a custom action and take some more
>> time to figure it out.
>>
>> Walt
>>
>> <?xml version="1.0" encoding="utf-8"?>
>>
>> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"; xmlns:util="
>> http://schemas.microsoft.com/wix/UtilExtension";>
>>
>>
>>
>> <?define ProductName="MCO e*System Integration Files" ?>
>>
>> <?define UpgradeCode="{B44477EF-7487-4302-875C-DA2846EB30DA}" ?>
>>
>> <?define ProductVersion="1.0.5.0" ?> <!-- Product version. -->
>>
>> <?define MaxVersion="1.0.5.0" ?> <!-- Highest version this should upgrade.
>> Most of the time, should be same as ProductVersion.-->
>>
>> <?define MinVersion="1.0.0.0" ?> <!-- Lowest version this should upgrade.
>> -->
>>
>>
>>     <Product
>>
>> Id="*"
>>
>> Name="$(var.ProductName)"
>>
>> Language="1033"
>>
>> Version="$(var.ProductVersion)"
>>
>> Manufacturer="Our Co, LLC"
>>
>> UpgradeCode="$(var.UpgradeCode)" >
>>
>>
>> <Package
>>
>>     InstallerVersion="300"
>>
>>     Compressed="yes"
>>
>>     InstallScope="perMachine"
>>
>>     Comments="No detail."
>>
>>     Description="e*System Integration Programs"
>>
>>     Manufacturer="US e*System Integration - Walt Dexter -
>> walter.dex...@example.com" />
>>
>>
>> <Upgrade Id="$(var.UpgradeCode)">
>>
>>     <UpgradeVersion
>>
>> IgnoreRemoveFailure="yes"
>>
>> IncludeMinimum="yes"
>>
>> IncludeMaximum="yes"
>>
>> Minimum="$(var.MinVersion)"
>>
>> Maximum="$(var.MaxVersion)"
>>
>> MigrateFeatures="yes"
>>
>> Property="UPGRADE_1"
>>
>> >
>>
>>     </UpgradeVersion>
>>
>> </Upgrade>
>>
>>
>> <MediaTemplate EmbedCab="yes" CompressionLevel="high" />
>>
>>
>> <Feature Id="FEAT_ALLFILES" Title="e*System Integration Files" Level="1">
>>
>>     <ComponentGroupRef Id="CMPG_SCRIPTS" />
>>
>> </Feature>
>>
>>
>> <Property Id="REBOOT" Admin="yes" Secure="yes">ReallySuppress</Property>
>>
>> <Property Id="ARPCOMMENTS">e*System Application from
>> Metametrics</Property>
>>
>> <Property Id="ARPCONTACT">US e*Restaurant Integration - Walt
>> Dexter</Property>
>>
>> <Property Id="ARPNOMODIFY" Value="1" />
>>
>> <Property Id="ARPNOREPAIR" Value="1" />
>>
>> <Property Id="DISABLEROLLBACK" Value="1" />
>>
>> <!-- <Property Id="REINSTALLMODE" Value="amus" /> -->
>>
>> <Property Id="MSIRESTARTMANAGERCONTROL" Value="0" />
>>
>> <Property Id="MSIRMSHUTDOWN" Value="2" />
>>
>> <Property Id="ReinstallFileOlderVersion" Value="o" />
>>
>> <Property Id="ReinstallFileVersion" Value="o" />
>>
>> <Property Id="ReinstallRepair" Value="r" />
>>
>> <Property Id="MCO___APP_TYPE" Value="$(var.ProductName)" />
>>
>>
>> <CustomAction Id="CA_SetCDrive" Directory="C_DRIVE" Value="c:\" />
>>
>>
>> <InstallExecuteSequence>
>>
>> <RemoveExistingProducts After="InstallInitialize" />
>>
>> <Custom Action="CA_SetCDrive" After="CostFinalize" />
>>
>> </InstallExecuteSequence>
>>
>>
>> <Directory Id="TARGETDIR" Name="SourceDir">
>>
>>     <Directory Id="C_DRIVE" Name="CDrive">
>>
>> <Directory Id="DIR_PROGRAMDATA" Name="ProgramData" >
>>
>>     <Directory Id="DIR_MICROSOFT" Name="Microsoft" >
>>
>> <Directory Id="DIR_POINTOFSERVICE" Name="Point of Service" >
>>
>>     <Directory Id="DIR_CONFIGURATION" Name="Configuration" />
>>
>> </Directory>
>>
>>     </Directory>
>>
>>     <Directory Id="DIR_EPSON" Name="epson" >
>>
>> <Directory Id="DIR_PORTCOMMUNICATIONSERVICE"
>> Name="portcommunicationservice" />
>>
>>     </Directory>
>>
>> </Directory>
>>
>> <Directory Id="DIR_MCOUSA" Name="MCOUSA" >
>>
>>     <Directory Id="DIR_SCRIPTS" Name="Scripts" />
>>
>>     <Directory Id="DIR_CONFIG_BASE" Name="config.base" />
>>
>>     <Directory Id="DIR_CONFIG" Name="config" />
>>
>> </Directory>
>>
>> <Directory Id="DIR_XPESTAGING" Name="XPeStaging" >
>>
>>     <Directory Id="DIR_APP" Name="App" />
>>
>> </Directory>
>>
>>     </Directory>
>>
>> </Directory>
>>
>>
>> <ComponentGroup Id="CMPG_SCRIPTS" Directory="DIR_SCRIPTS">
>>
>>     <Component Id="CMP_ESCINT_EXE"
>> Guid="{E99F5E86-2CDB-4EB9-A638-54144CDD50FD}">
>>
>> <File Source="..\..\source\MCOUSA_eSC_Int\MCOUSA_eSC_Int\bin\Release\"
>> Id="eSCInt.exe" DefaultVersion="$(var.ProductVersion)" KeyPath="yes" />
>>
>>     </Component>
>>
>>     <Component Id="CMP_MCOHTMLWATCHER_EXE"
>> Guid="{DE351116-CA6E-4A27-9351-56A3B674F536}">
>>
>> <File Source="..\..\source\MCOUSA_eSC_Int\MCOHTMLWatcher\bin\Release\"
>> Id="MCOHtmlWatcher.exe" DefaultVersion="$(var.ProductVersion)"
>> KeyPath="yes" />
>>
>>     </Component>
>>
>> </ComponentGroup>
>>
>>     </Product>
>>
>> </Wix>
>>
>>
>>
>>
>> On Fri, Jan 24, 2014 at 10:35 PM, Rob Mensching <r...@robmensching.com
>> >wrote:
>>
>> > 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
>> >
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>
------------------------------------------------------------------------------
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

Reply via email to