I ran the Power Management Configuration Wizard to setup a custom power plan for Windows 7 machines. The script runs and creates the plan but fails to switch the active plan to it. What can I do to make the Custom Kace plan active across the machines I am testing this on?

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



I had the same problem. I had to create a second script that set the created power configuration as the active one.

I used these commands (see link) to find the GUID for the power configuration. Once I found the GUID I checked it on several different computers and found that it didn't vary from computer to computer. I would assume this would be the same for you, but you should probably check and make sure.

Once I found the GUID I just made a script that ran the command to set it as active (see link again). Hope this helps.


Answered 06/28/2012 by: Ben M
Ninth Degree Black Belt

Please log in to comment

I believe the problem is that the script wizard auto checks the "Wait for startup" check in the steps. It appears that this does not work well when you are executing several steps with the powercfg.exe command in a script.

Answered 06/28/2012 by: jraley
Yellow Belt

Please log in to comment

I would check the script and verify that it has lines for IMPORT and for SETACTIVE.  Here's a batch file I use (during a Win7 scripted install) that imports a previously created custom power plan and makes it the active plan, for reference:

POWERCFG -IMPORT C:\KACE\Applications\98\win7.pow 00000000-0000-0000-0100-000000000000

POWERCFG -SETACTIVE 00000000-0000-0000-0100-000000000000

One other thing to mention is that I had mixed results with trying to replace (overwrite) an existing power scheme using this method.  I found creating a new scheme (i.e. using a completely different ID number) and setting it active to be consistently successful.

A final thing to try (if you haven't done so already) is to play with what account the script is running under - sometimes a script that is failing when running as system does just fine running as the current user (and for something like this, it shouldn't matter who it runs as, as long as the account has local admin rights).


Answered 06/27/2012 by: jverbosk
Red Belt

Please log in to comment

Set your power settings via GPO's less hassles. when we tried on the pc's with scripts not all users got the settings, with GPO they do.

Answered 06/28/2012 by: SMal.tmcc
Red Belt

Please log in to comment