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. ----- Original Message ----- From: "Marc-André Lureau" <mlureau@xxxxxxxxxx> To: sstutsma@xxxxxxxxxx Cc: virt-tools-list@xxxxxxxxxx Sent: Tuesday, June 9, 2015 5:37:21 AM Subject: Re: [virt-viewer PATCH V2] Add InstallScope="perMachine" to virt-viewer.wxs.in hi ----- Original Message ----- > From: Sandy Stutsman <sstutsma@xxxxxxxxxx> > > Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1146016 > Without this parameter the installer will place the start menu icon in the > Admin users path rather than the 'AllUsers'. Unprivileged users are unable > to use the menu to start the remote-viewer. > > N.B. Because previous installations mixed Users and PerMachine (AllUsers) > paths, this installation will *NOT* properly upgrade them. They must be > manually uninstalled first. I still don't understand what you mean by "mixed Users and PerMachine" _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
