Look in the Bundle's log file. It'll show what was installed. If anything
per-machine was installed, it will have to elevate.


On Tue, Jul 30, 2013 at 1:14 AM, David Watson <dwat...@sdl.com> wrote:

> I don't think burn currently supports this kind of scenario well (it may
> but
> I am not an expert).
>
> What you could do is make a per-user burn bundle that just installs your
> msi
> silently then add that as an .exe package to your main with-prerequisites
> bundle.
>
> Or indeed leave it the way you have it and maybe flag the upgradable msi as
> visible in ARP and supply the msi directly when you service it.
>
> Or you could work out how burn is deciding to show the UAC prompt and fix
> it
> so it works in your scenario if possible.
>
> Dave
>
> -----Original Message-----
> From: dave [mailto:d...@swordfishsoftware.co.nz]
> Sent: 30 July 2013 06:02
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Unattended upgrade of Burn package
>
> I'd like to use Burn to install multiple pre-requisites (VC++ redist,
> console
> app) and two desktop application msi packages. One of these desktop
> applications is a client program to be remotely upgraded without elevation.
> I have it installing to LocalAppData and major upgrades work fine without
> elevation.
>
> Now, can I install this client app via Burn and then run a major upgrade on
> it using just the msi package? I have installed via Burn with the
> pre-requisites and this raises UAC as expected. I ran a major upgrade using
> just the msi and this performed as expected but put a new entry into
> Programs
> and Features.
>
> I cannot run the complete burn bundle as a major upgrade in quiet mode as
> this raises the UAC prompt, even though only the client app is updated
> with a
> new version.
>
> Is this even possible? How do I go about it?
>
> My bundle:
>
> - VC++ redist (installed via burn)
> - console app (requires elevation, installed via burn)
> - client app (DOESN'T require elevation, installed via burn) <- I want to
> upgrade this silently either with burn or msi
> - server app (requires elevation, installed via burn)
>
> Thanks
>
> Dave
>
>
>
> --
> View this message in context:
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unattended-upgr
> ade-of-Burn-package-tp7587678.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> -----------------------------------------------------------------------------
> -
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught
> up. So what steps can you take to put your SQL databases under version
> control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and
> requires that you delete it without acting upon or copying any of its
> contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.
>  Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
> 7DY, UK.
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&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