[virt-tools-list] [virt-viewer PATCH V2] Add InstallScope="perMachine" to virt-viewer.wxs.in

[Sandy Stutsman]

The default installation (say double clicking the .msi file) results in an inconsistent installation state, part perMachine/part perUser. (The situation that raised the bug.)  The expected behavior is that the default installation be consistent. If other clients don't have admin privileges they can't install the client.

Adding the ALLUSERS to the command line works but double clicking the .msi file will remain broken and difficult to upgrade to a true perMachine installation.

-S
  

----- Original Message -----
From: "Marc-André Lureau" <mlureau at redhat.com>
To: "Sandy Stutsman" <sstutsma at redhat.com>
Cc: virt-tools-list at redhat.com
Sent: Tuesday, June 9, 2015 9:47:19 AM
Subject: Re: [virt-tools-list] [virt-viewer PATCH V2]	Add	InstallScope="perMachine" to virt-viewer.wxs.in



----- Original Message -----
> Hi
> 
> ----- Original Message -----
> > Hi Mark,
> > 
> > A perUser install puts all the package contents in the User's path; the
> > start
> > menu items and executable will be places under the installer's user paths.
> > A perMachine install puts the packages under directories that are
> > accessible
> > by all users.
> > 
> > The current installation puts the executable in the accessible paths but
> > the
> > start menu items under the installer's path.  So to other users the package
> > doesn't appear to be installed.
> > While it is possible for all users to run the programs, it isn't obvious or
> > particularly easy for them to do so.
> > 
> 
> Given that Microsoft recommends per-user:
> https://msdn.microsoft.com/en-us/library/aa367559%28v=vs.85%29.aspx
> 
> And that  ProgramMenuFolder,ProgramFilesFolder etc.. are set according to the
> installation context, I wonder what we are doing wrong in the current wxs.
> 
> It looks to me like we should try fixing the start menu path to be for the
> current user only. That way we wouldn't break upgrade, the client would
> remain per-user (by default), and thus could be used by activex auto-install
> eventually.

sorry, so that's the current behaviour, so what's wrong with it? other users
can't install their own client?

I read from the bug that they want perMachine install, can't they instruct
Windows installer to do so via msiexec ALLUSERS=1 (or probably other means)?