Only local account mgt. includes power users. In an AD environment, there is no power user. The fix I found out from a GPO guru is this - create a security group called installers, add the users and computers you wish to grant this permission to (both user and computer have to be members).
Create a GPO, edit it, add a registry key, choose HKLM\SOFTWARE add the new security group and grant full permissions to the key.
**DO NOT REPLACE PERMISSIONS, you will in effect take out the everyone and system groups if you do.
Add the computer and users abilities to install with elevated privies and patch, etc...all the other switches that one would think would allow users to install locally by definition.
GOTO the properties of the GPO and remove authenticated users and add the defined security group with read/apply permissions.
The simple switch setting implies the ability to allow a user to install applications on their own but the domain user does not have permission to write to the system registry key HKLM\SOFTWARE. Ever had a problem with a user trying to accept the EULA ater installing the office suite? Or making Outlook the default email program after installing it? Or alow a user to goto windowsupdates? This will fix that. I don't want to have to deply every application through an MSI, RIS or Zenworks NAL. Coming from a consultant's point of view, I administer over a dozen networks up and down Northern California and some reaching Arizona and New York. I can't handhold every install that occurs, nor can I allow all users to be administers. Having a local administrator that works full time is nice but not all clients can afford to have both. I am curious for feedback on who else implements this workaround. I called Microsoft and spent four hours working on this issue, but formally this configuration is not supported by Microsoft - they want intellimirror to rule all installs.
Good Luck!
Matthew Tollow
CCNA, MCSE, CNA, A+
Staff Consultant
Portola Systems, Inc.