/build/static/layout/Breadcrumb_cap_w.png

UAC on repair from appwiz.cpl

Hello.

I'm getting a UAC with credentials prompt when running repair from Add Remove programs.

Standard command line repair (msiexec /fomus) does not bring up the repair prompt.

ReinstallModeText is omus.

I've tried to log the repair from ARP (by setting the log file options for the ReinstallModeText property ), but it doesn't create a log file, so I suspected that GPO is affecting this, so I've reviewed the GPO settings and was still unable to find an explanation. ;)

Would appreciate some pointers. Thank you. ;)

0 Comments   [ + ] Show comments

Answers (4)

Posted by: Teitan 13 years ago
Senior Purple Belt
0
I would take a look at the InstallUISequence in your MSI...perhaps there is an action which causes the UAC prompt.
Posted by: jmcfadyen 13 years ago
5th Degree Black Belt
0
turn on global logging I think from memory the key is here

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer

Add a string of

logging = voicewarmupx

This is from memory if its wrong I am sure someone will pick it up. I think I have been out of packaging too long now. .
Posted by: GrGrGr 13 years ago
Orange Belt
0
ORIGINAL: jmcfadyen

turn on global logging I think from memory the key is here

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer

Add a string of

logging = voicewarmupx

This is from memory if its wrong I am sure someone will pick it up. I think I have been out of packaging too long now. .


voicewarmupx

Great tip. Thank you! http://support.microsoft.com/kb/223300/en-us

Already turned on logging and found the log file. :)

REINSTALL=ALL REINSTALLMODE=ocmusv
MSI (s) (7C:8C) [10:57:52:217]: MSI_LUA: Recache/Reinstall of a product that was not originally installed by GP will require elevation approval


Some thoughts on UAC in MSI Notes: How do I troubleshoot UAC in MSI via the log?, but no solution [url]http://blogs.msdn.com/b/rflaming/archive/2006/09/30/uac-in-msi-notes-how-do-i-troubleshoot-uac-in-msi-via-the-log.aspx[/url]

Most likely the "V" option is causing this.
v Use to run from the source package and re-cache the local package. Do not use the v reinstall option code for the first installation of an application or feature.

Does anyone have suggestions why it is being set when repair is run from ARP?
Posted by: GrGrGr 13 years ago
Orange Belt
0
This is still something that I haven't found a solution for.

I'm getting the suspicion that it might be related to AS10 built .msi files.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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