When you say it's advertised, I'm not sure whether you're referring to other users on the machine, and if some of the scenarios are about an administrator doing a repair but a limited user can't use the advertised feature correctly.
If it's registry data intended for different users it typically goes into HKCU so that each new user gets the data when they use the feature. Windows Installer does not violate security rules, so if the basic situation is that a limited user is doing something that installs registry data to HKLM then I can't see that working without some administrator blessing somewhere (such as via group policy). You probably need logging policy set to get log for these spontaneous repair-type situations: http://support.microsoft.com/kb/223300 or the issue might be that you're using * in MsiLogging, which seems to like * so spell out the options: http://msdn.microsoft.com/en-us/library/aa370322(v=vs.85).aspx --------------- Phil Wilson On Fri, Apr 11, 2014 at 6:20 AM, Phill Hogland <phogl...@rimage.com> wrote: > Yes, the MSI package has the following: > > <Package Platform="x86" Description="$(var.AppNameLong)" > InstallerVersion="500" > Compressed="yes" InstallScope="perMachine" > SummaryCodepage="!(loc.SummaryCodepage)" /> > > When this package is launched as part of the bundle chain the log indicates > that ALLUSERS is 1. > > This package has been installing with the feature advertized, but without > complaining about this registry value for some time. However I recently > refactored some of the wxs files to make then more maintainable, and I moved > this registry key to a different fragment, but also associated with the same > advertised feature. > > This old code, which did not result in an error, and the key was written > during the advertised portion of the install: > <Fragment> > <ComponentGroup Id="QD_HKLM_SOFTWARE_RegKeys"> > <Component Directory="QuickDiscDir"> > <RegistryValue Root="HKLM" Key="SOFTWARE\Company" Name="SDA" > Value="0" Type="integer" KeyPath="yes" /> > </Component> > </ComponentGroup> > </Fragment> > > This is the current code which does result in the error (but only when being > installed as result of advertised feature): > <Fragment> > <ComponentGroup Id="$(var.ProductAbreviation).uniqueProperties" > Directory="$(var.ProductDir)"> > <Component> > <RegistryValue Root="HKLM" Key="$(var.Release_CompanyRegKey)" > Name="SDA" Value="[SDA]" Type="integer" KeyPath="yes" /> > </Component> > </ComponentGroup> > </Fragment> > > I also found that I can add AllowAdvertise="no" to the feature and avoid the > problem, but I appreciate any advice so that I can understand this behavior > and learn the best practices to avoid this problem. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/advertised-install-and-user-permissions-tp7594058p7594070.html > Sent from the wix-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
