Synopsis
This article explains how to install an installation package on a target machine regardless of user privileges.
Discussion
The following methods can be used to enable a non-administrator to install an applictaion with elevated system privileges.
To Enable Via User Access Control (Vista and Later)
A member of the Administrators group can provide authorization for a non-administrator to elevate through User Access Control which is described in Using Windows Installer with UAC.
To Enable by System Policy
- On the Start menu, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
- In the console tree, right-click the domain or organizational unit for which you want to set the policy.
- Click Properties, and then click the Group Policy tab.
- Select a Group Policy Object in the Group Policy Objects Links box and click Edit.
- Open the
Local Computer Policy\Administrative Templates\Windows Installerfolder. - In the details pane, double-click the Always install with elevated privileges policy.
- In the Group Policy Property dialog box, enable the policy, select the check box to turn the setting on, and then click OK.
- Open the
User Configuration\Administrative Templates\Windows Installerfolder and repeat Steps 6 and 7.
Under Windows NT 4.0, you can use the System Policy Editor and Windows Installer policy template file (Instlr11.adm) to set the Always install with elevated privileges policy. You must set the policy for the computer and for each user. For more information about setting system policies in Office XP, see Understanding System Policies.
If you choose not to use the Group Policy Editor or the System Policy Editor, you can specify the same setting on each computer by changing a value in the Windows registry.
To Enable Elevated Privileges in the Windows Registry
- On the Start menu, click Run and type regedit to open the Registry Editor.
- Find or add the following subkey in the Windows registry:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer - In the Installer subkey, insert AlwaysInstallElevated as a REG_DWORD and its value to 1.
- Find or add the following subkey in the Windows registry:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer - In the Installer subkey, insert AlwaysInstallElevated as a REG_DWORD and its value to 1.
- Repeat Steps 5 and 6 for each user of the computer.
Additional Information
With the release of Windows Server 2003 SP1 it has been reported that in some cases setting AlwaysInstallElevated was not sufficient. In this environment, the DisableMSI setting might also need to be set to 0.
For more information, see the following MSDN Library articles
Related Articles
Always Overwrite Files Regardless of Version, Date, and Time Stamp 18Number of Views Alerts related to software maintenance on licenses are not scoped to user privileges 4Number of Views How does a Service With User Account Privileges Go About Starting The FlexNet Licensing Service? 10Number of Views Authoring a Silent Installation 37Number of Views Spider Setup: Administrative privileges for installation 7Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago