Configuring Configuration Manager R3 – Power Management
In my previous post, I showed you how to install the R3 component of Configuration Manager. After you’re done with the install, there’s a couple more things you should do before you can go ahead and start managing power on your client computers.
First up, enabling the Power Management client agent! You soon realise right after installing the R3 there is a new client agent and that will be your Power Management Client Agent.
Not much to configure there though. All you need to do is to enable it. Just a simple checkbox.
You do also need to apply a hotfix to all the Advanced Clients which you should remember as part of the R3 installation. The package for the hotfix is already automatically created, so all you need to do is to get it out to all your clients. I would probably use the Software Distribution to advertise this out to all clients. While doing that I would also probably create a collection to track computers that are still running the “un-patched” agents. Here’s the query I’d probably use.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion < “4.00.6487.2153”
No biggie here so far I hope. Note that the client version is .2153 and that’s the Release Candidate version. The number should change once it gets to RTM.
As you’ve deployed the hotfix out you’ll realise the change in client version number. Here’s where you can check just to make sure.
And this is from the client side in the control panel Configuration Manager properties.
Hey hey, and you’re almost done! Last thing to do is to now set the power management policies. This is done on a collection level. How great is that? So, how I would begin is to create a first level collection for computers I want to implement power management policies. Below that I would create sub-collections that will represent my different power plans/policies. In my example I have different working times or shifts; e.g. Graveyard shift and the normal day shift. You can go ahead to create more as you like.
In each collection you can configure power management to either only monitor the power management settings or to monitor and implement power management settings for computers in that collection. When you decide to also implement power management settings, you would need to configure peak hours. Anything outside the peak hours are considered non-peak hours.
You would then decide what power plans to use for peak hours and non-peak hours. You get to choose from the standard templates; Power Saver, Balanced, and High Performance. You get to view the granularity of each power plan settings by clicking on the View button. You will not be able to change those settings though.
If you would like to have your own customised power plans, there is also a customised power plan which will give you the ability to edit its granular settings.
One thing I like about is the Wakeup timer. Though this only works for desktop computers, it is a great feature where you can set a time when computers will turn itself on. You can do this either to perform maintenance in the middle of the night or simple powering up those computers right at the start of a working shift. Reasons why this is not available for notebook and laptop computers is the fear of the computer batteries catching fire; not sure if this has happened to anyone before.
I would probably do another part of this power management series surrounding the reporting of power management. In the meantime…