Customized Power Management policy does not take effect
This is a known issue. Windows 7 does not apply customized power plan policy created by Group Policy Management Editor.
Repro steps: (w and w/o SP1)
==========
1. Open group policy management editor=>computer configuration=>preferences=>control panel settings=>power options
2. Create new power plan, in ACTION column, choose “Create” option
3. In next column choose either of the build in plan, choose “High performance” as an example.
4. Check the “set as the active power plan”
5. Customize power plan settings
6. Click ok the finish policy setting.
7. In windows 7, restart computer to apply computer policy.
8. Open power option, you will find the “High performance” box is not checked. But customized settings such as idle time are applied.
Note: this problem also exists in user configuration.
Solution:
=========
In the new power plan properties, there is four options in ACTION column “create” ”update” ”replace” ”delete”, choose the “update” option instead of “create”, then problem will not occur.
Do not choose "Create" or "Replace”, instead, choose "Update" then it works fine.
Read the following article. At the end the behavior of Replace/Update/Delete/Active is explained:
Managing Power with Group Policy: Part 3 of 3
https://blogs.technet.com/askds/archive/2008/03/21/managing-power-with-group-policy-part-3-of-3.aspx
Reference:
=========
Comments
Anonymous
January 01, 2003
I have applied this with the "Use Group policy Loopback Policy " but the Windows XP PCs apply the policy but do not apply the Power scheme I configured...Anonymous
January 01, 2003
I am trying this now, hope it resolves my problem. Thanks for your helpAnonymous
January 01, 2003
The solution provided in this article does work with some caveats. It requires issuing the command gpupdate twice if you want to see it take effect right away. The first gpupdate creates the power plan. The second one sets the new plan as active. (I did not have patience to wait to see how long it would take for a single plan with Update type to take effect.)Another solution is to create 2 power plans with the same name and settings. The one processed first must be a Create type. The second should be an Update type. This causes the new plan to be created and set as default with one gpupdate. I also noted that gpupdate /force when used with one power plan of Update type does set the new plan as active.Anonymous
July 09, 2012
The comment has been removedAnonymous
September 11, 2012
This does not work either. Creating a new power plan using the Update option does not default it to active.Anonymous
April 08, 2013
agree, doesn't work. This is yet another example of these preferences just not working. What a shame.