[wix-users] MSI MajorUpgrade is not detecting old version

[Stein Inge Åsmul]

OK, if the old version is per-machine and the new one is per-user, then
there is nothing to clean up per-user of course. Hope that is the case. I
just thought it was the other way around glancing at it.

2018-07-16 0:44 GMT+02:00 Stein Inge Åsmul <glytzhkof at gmail.com>:

> Does that auto-magically clean out older per-user installs now?
>
> 2018-07-16 0:16 GMT+02:00 Rob Mensching via wix-users <
> wix-users at lists.wixtoolset.org>:
>
>> Or set the new WiX-based Package/@InstallScope='perMachine'  :)
>>
>> _____________________________________________________________
>>  Short replies here. Complete answers over there:
>> http://www.firegiant.com/
>>
>> -----Original Message-----
>> From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of
>> Stein Inge Åsmul via wix-users
>> Sent: Sunday, July 15, 2018 2:05 PM
>> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
>> Cc: Stein Inge Åsmul <glytzhkof at gmail.com>
>> Subject: Re: [wix-users] MSI MajorUpgrade is not detecting old version
>>
>> Maybe also a note that you could conceivably use your logon script, or
>> maybe WMI (I have never tried for per user stuff) to clean out the existing
>> per-user installations?
>>
>> I like the logon script approach, provided you have access to it (can be
>> an endless sea of red tape in big environments or disallowed by principle
>> of course). Just have your users log off on Friday, perform various
>> maintenance and then uninstall on login for all of them?
>>
>> 2018-07-15 20:15 GMT+02:00 Stein Inge Åsmul <glytzhkof at gmail.com>:
>>
>> > The best approach would perhaps be to clean out the existing per-user
>> > install via your distribution mechanism (SCCM?) and then rely on
>> > per-machine installations from now on? Or perhaps continue to install
>> > per-user? Hope not ;-). How about changing your new version to be able
>> > to install side-by-side with the per-user installation? (no
>> > interference between them - not always possible)
>> >
>> > Rob has an answer here on cleaning out old installs:
>> > https://stackoverflow.com/a/15659159/129130 (if you don't have
>> > features in your distribution system to do so auto-magically):
>> >
>> > You'll see a comment in that answer from me with another tip on how to
>> > do a per-user to per-machine migration using Installshield (
>> > https://stackoverflow.com/a/12291807/129130). It is an involved
>> > procedure that worked for me in a particular case, but it is quite
>> > clunky. I have never tried it with WiX.
>> >
>> > How large is your distribution?
>> >
>> > 2018-07-14 15:15 GMT+02:00 Nir Bar via wix-users <
>> > wix-users at lists.wixtoolset.org>:
>> >
>> >> MSI_new.log says: MSI (c) (E4:0C) [08:15:00:855]: FindRelatedProducts:
>> >> current install is per-user.  Related install for product
>> >> '{41EEEE03-A050-46D8-82EC-4C6834A6A8C1}' is per-machine.  Skipping...
>> >> -- Nir Bar, Independent WiX Expert. Creator of- JetBA: WiX WPF
>> >> Bootstrapper User Interface Framework JetBA++: WiX Native
>> >> Bootstrapper User Interface Framework JetRummikub: Install WiX
>> >> packages on remote machines
>> >>
>> >> ____________________________________________________________________
>> >> WiX Toolset Users Mailing List provided by FireGiant
>> >> http://www.firegiant.com/
>> >>
>> >
>> >
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant
>> http://www.firegiant.com/
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant
>> http://www.firegiant.com/
>>
>
>