This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Auto-repair mode failing when user is not an Admin
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 15, 2008
08:33 AM
Auto-repair mode failing when user is not an Admin
We have a basic msi install project created with IS 2008 that seems to be having some auto-repair issues when pushed out by the Admin but ran on the machines by non-admins.
For every user that logs onto these machines the install will trigger an auto-repair and then fail because the user is not an Admin. When the Admin logs onto those machines the install and app are fine.
Now there are no entries that are created un the HKCU so I can not see that causing an issue, but there is something that has to be causing the repair mode.
Now I have asked for Event viewer logs, but is there anything else that I should be asking from the users to determine what is causing the auto-repair to occur?
If our installs are set to only run if the user is an admin does this mean that if there is anything that causes a repair mode that it will automatically fail if the users that is logged in is not an admin? If so then how can we get around this issue?
Most of our installs are made to be pushed out over the network and therefore made for admins to install. So if this causes issues for non-admins and repair mode then again I would need to know how we should handle these cases.
Thanks for any insight.
For every user that logs onto these machines the install will trigger an auto-repair and then fail because the user is not an Admin. When the Admin logs onto those machines the install and app are fine.
Now there are no entries that are created un the HKCU so I can not see that causing an issue, but there is something that has to be causing the repair mode.
Now I have asked for Event viewer logs, but is there anything else that I should be asking from the users to determine what is causing the auto-repair to occur?
If our installs are set to only run if the user is an admin does this mean that if there is anything that causes a repair mode that it will automatically fail if the users that is logged in is not an admin? If so then how can we get around this issue?
Most of our installs are made to be pushed out over the network and therefore made for admins to install. So if this causes issues for non-admins and repair mode then again I would need to know how we should handle these cases.
Thanks for any insight.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 15, 2008
11:39 AM
Without knowing what is failing, it's hard to suggest how to fix it. As a guess, I would look for custom actions that require administrative privileges, but are not authored in a way to guarantee receiving them from the implicit elevation in auto-repair (i.e. aren't deferred in system context).
If you can reliably trigger the auto-repair, it should be easy enough to get a log by setting the Windows Installer logging policy in the registry (http://support.microsoft.com/kb/223300). Perhaps that will point in the right direction to solve it.
If you can reliably trigger the auto-repair, it should be easy enough to get a log by setting the Windows Installer logging policy in the registry (http://support.microsoft.com/kb/223300). Perhaps that will point in the right direction to solve it.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)