SCCM R3 : Power Management In Practice (how-to) Part 1

June 5, 2010 at 9:33 am in ConfigMgr, ConfigMgr 2007, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Power Management, R3, Reporting, sccm, SCCM 2007, SCCM 2007 R3, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

Hi there ,

I have recently deployed Configuration Manager 2007 R3 beta (refresh) in production at my TAP customer.In my previous blog post I highlight the R3 the beta installation on your SCCM 2007 SP2 lab environment .

See “

Disclaimer: You are not allowed to install any beta products in your production environment!!! This is only allowed for selected TAP Customers !!! Always install beta products in lab environments !!!

This blog post highlights the R3 Powermgmt feature ; how to use it in your environment and start using reporting on your powerconsumption.


Prerequisites :

First you need to start rolling out the R3 Client mgmt hotfix to your clients.When done the SCCM client will show up with a newer version build.The current version is 4.00.6487.2125.


Enable your Power management client under “Client Agents”:


Configuration Manager 2007 R3 beta Client upgrade Validation Report

After you have deployed the R3 beta Client hotfix, you can use the below query to create a web or SQL SRS report for tracking the R3 beta Client upgrade status

SELECT  CASE sis.Client_Version0
             WHEN ‘4.00.6487.2000’ THEN ‘ConfigMgr SP2 RTM’
             WHEN ‘4.00.6487.2125’ THEN ‘ConfigMgr SP2 R3 beta’
        END AS [ClientVersion]
       ,COUNT(1) AS [Total]
  FROM v_R_System sis where
         sis.Client0 = 1
         AND sis.Obsolete0 = 0
         AND sis.Client_Version0 IN (‘4.00.6487.2000′,’4.00.6487.2125′)
GROUP BY CASE sis.Client_Version0
               WHEN ‘4.00.6487.2000’ THEN ‘ConfigMgr SP2 RTM’
               WHEN ‘4.00.6487.2125’ THEN ‘ConfigMgr SP2 R3 beta’

Collections :

You basically need 3 collections :

    • A Baseline collection : This collection contains the members that have will be in scope for Powermgmt.
    • An Enforcement collection : This collection are going to have a Powermgmt plan applied.
    • An Opt-Out collection : This collection will never have a Powermgmt plan applied.

Some people have different requirements for implementing power plan: some people will have longer work hours (eg. From 6 am – 11 pm), some branch office may have different working hours, etc. To define different power policy, people need to communicate with different teams and make different power settings for different requirements. So you will define different PowerMgmt collections to meet different needs.
In this blog post example, we will only enforce power policy for one set of regular working hours.

This is how my collection structure looks like :


Like you see here , I have made the difference between laptops/Desktops . This has been done to monitor more closely of what the consumption/savings would be , but also with in the back of my mind for later enabling different powerplans between desktops/laptops.

[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Baseline Collection query :

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 inner join SMS_G_System_POWER_MANAGEMENT_CAPABILITIES on SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like "Microsoft Windows NT Workstation %" and SMS_R_System.Name not like "OCHP%" and SMS_R_System.Client is not null  and SMS_R_System.ADSiteName = "CDM-Hoofdzetel" and SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.PreferredPMProfile = 1

It looks like this :


As you can see I use the “Power Capabilities.PreferedPMProfile” .

This value is been returned from your HW inventory that reads out the value from the BIOS that have the ACPI v2.0 Specification  The set of values is currently:

    • 0–Unspecified
    • 1–Desktop
    • 2–Mobile
    • 3–Workstation
    • 4–Enterprise Server
    • 5–SOHO Server
    • and more


[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Disabled Collection query :

This is right now a static collection membership as I want to add different computers quickly

[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Enabled Collection query :

I had the need to make a collection that toke all the members from my baseline “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Baseline Collection” collection and exclude members from my “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Disabled” collection.I needed to seperate several custom machines that I don’t want to be treated by my powermgt plan . I had a really hard time trying to find and/or build a query that actually worked.

The query to 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.Client = 1

and SMS_R_System.ClientType = 1

and SMS_R_System.ResourceId in (select ResourceID from SMS_CM_RES_COLL_xxxxxxx)

and SMS_R_System.ResourceId not in (select ResourceID from SMS_CM_RES_COLL_yyyyyyy)

Replace the item in red with the Collection ID of the baseline collection : “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Baseline Collection” and replace the item in Blue with the Collection ID of the collection : “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Disabled” you are trying to exclude, which is located under the General tab of the properties window.

It looks like this :


Power Plans :

Before enabling Powerplans to your collections , you need to know about which clients are capable to apply any of your powerplan settings and eventually at that moment take corrective measures.

To do that we will use SRS reporting  and I will explain that in my other blog post next week . So stay tuned to see my next blog post on how to indentify machines that will need different powerplans and actions taken to resolve some of the issues found.


Hope it Helps ,

Kenny Buntinx .

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest