Software Deployment Question

UAC and Active Setup

06/24/2015 3697 views
Hello I have run into a bit of an issue regarding UAT. I have an MSI which is installed by SCCM onto windows 7 OS and works fine but part of the install is adding files and registry keys under the following locations.


and file location


Part of this install is to add a registry key for Active setup with the following stubpath "Msiexec.exe /fauvs {870A37F4-0850-41C4-8518-C25AFE7A0EFE} /qb"

The problem I have is that when I login as my restricted user I get a UAC prompt asking for credentials??? I would of thought this would have used a installer account? not the actual user.

I have got around this issue for now by adding users to local admin group and turning off UAC prompt through group policy but I'm sure this is not the correct way. I couldn't use Self Healing in the package as the browser is opened on startup. I have read through allot of blogs and Microsoft posts but I'm even more confused by them.

Can anyone provide any guidance here?

Should UAC be prompting?

Is it file permissions that need to change or group policy?

Does the package need to be changed?
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author


You're asking WI to reinstall all files with the 'a'. Change the command line to:

Msiexec.exe /fup {870A37F4-0850-41C4-8518-C25AFE7A0EFE} /qb

Also, best practice is to have all of the user profile-targeted data in a discrete feature of its own and that the components in that feature have a HKCU key path, not blank/null or file-based.

Answered 06/25/2015 by: VBScab
Red Belt

  • Thanks for your help here could you elaborate on this comment more "HKCU key path, not blank/null or file-based" thankyou
    • Component key paths for user profile-targeted data should be a registry key, not a file. If one doesn't exist, just create one. Typically, I use something like HKCU\Software\(_ClientName_)\KeyPath\[ProductCode]

      If you leave a key path blank/null, WI will use the component's folder as its key path which can present problems when repairing/self-healing.
  • Also do not use /v.
    v - runs from source and recaches local package
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ