Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1360
  • Last Modified:

Allow non local admin users to change power options

I need to be able to allow users who do not have local admin rights to be able to change their power options on the XP machine.
Does any know of a GPO I can create for this?
DC is W2K3
0
tolinrome
Asked:
tolinrome
  • 3
  • 3
1 Solution
 
mooodiecrCommented:
Option 1:
The only way I have been able to do this, is to change permissions on a registry key.
    *  Run Regedit.exe as an administrator
    * Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\PowerCfg
    * Right-click on the “GlobalPowerPolicy” key and choose “Permissions”.
    * Click on the “Advanced” button.
    * Click “Add”.
    * Type INTERACTIVE and click “Check names”, then OK.
    * Check the “Set value” and “Create Subkey” checkboxes in the “Allow” column, and click OK, then OK, then OK.
    * Do the same thing with the “PowerPolicies” key.

I know this was found on a website but I just saved the "how to" and seemed to work great for us.  If this is for several users you can script a permission change using this article:
http://support.microsoft.com/kb/264584

Option 2:
You can also create a security Template to allow permissions to the registry file in Group Policy.  
Open up Group Policy Editor and browse to Computer Configuration -> Windows Settings -> Registry
Then right click in the right hand pane and choose new key.  Browse to the keys noted above and add the correct permissions.


0
 
tolinromeAuthor Commented:
Wouldn't it be possible to make the changes to those registry keys on a client then export them and then push it out via GPO?

I need to do this on many machines and doing it manually or having any user interaction is out of the question.
0
 
mooodiecrCommented:
Since there are so many of them the best way would be option 2 mentioned above.

"You can also create a security Template to allow permissions to the registry file in Group Policy.  
Open up Group Policy Editor and browse to Computer Configuration -> Windows Settings -> Registry
Then right click in the right hand pane and choose new key.  Browse to the keys noted above and add the correct permissions."

You can link this at the Top of the domain and all the users would receive the proper registry permissions.
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
tolinromeAuthor Commented:
Ok,that sounds better.
I just followed your suggestion on GPED on the DC and after I set the permissions I'm prompted with a box "Security policy Setting"

Radio Button options are:
1. Propagate inheritable permissions to all subkeys
2. Replace existing permissions on all subkeys with inheritable permissions
3. Do not allow permissions on this key to be replaced.

I'm assuming that I should choose the second choice?
I only want them to have the ability to change the power options.
0
 
mooodiecrCommented:
Option 1 or 2 should be fine.  The only thing you might want to be aware of is that if you do choose option 2 it will replace any permissions that an application installed by an admin have put on those keys.  Since it is a power management, I would assume that this would not be the case.  However, if it were those permissions would be removed with whatever you have put on the parent key.  

Just something to consider.
0
 
tolinromeAuthor Commented:
Worked great, thanks.
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now