virtual techdays INDIA │ 9-11 February 2011 Implementing a Power Management Strategy with System Center Configuration Manager 2007 R3 Chandramouli K │ Sr. Program Manager, Microsoft

 Overview of Configuration Manager 2007 R3  Configuration Manager R3 at a glance  Enabling power management in R3  Why R3 power management  R3 power management implementation life cycle  Best practices  R3 out of box reports  Key observations  Noteworthy industry facts on power management virtual techdays INDIA │ 9-11 February 2011 S E S S I O N A G E N D A

 Management Platform and Service Delivery  Operational Team of System Center - Desktop Management System Technologies  Deployment Services - System Center Configuration Manager  Dogfooding (early adoption/product feedback): ConfigMgr 2012, R3, Forefront, etc.  Windows Update/Microsoft Update infrastructure  Windows InTune  Customers:  Microsoft IT  Microsoft Retail Stores  Online Customers: Energizer and XL virtual techdays INDIA │ 9-11 February 2011 Our Team & What we do

virtual techdays INDIA │ 9-11 February 2011 Overview of ConfigMgr R3

 ConfigMgr R3  is a new release of System Center Configuration Manager in line of previous releases SP1, SP2, R2 and R3  Provides a set of tools that enable the site administrator to configure standard Windows power settings across computers (‘Power Management feature’)  Other key features include  Active Directory Delta Discovery  Dynamic Collection Evaluation  Higher no. of supported clients per hierarchy (~ 300K clients)  Simplified Resource Management virtual techdays INDIA │ 9-11 February 2011 ConfigMgr R3 – at a glance  ConfigMgr 2007 R3 upgrade needs a pre-requisite hot-fix KB on servers & clients  ConfigMgr07 SP2 is a pre-requisite for the above hot-fix to be applied  ConfigMgr 2007 R3 upgrade needs a pre-requisite hot-fix KB on servers & clients  ConfigMgr07 SP2 is a pre-requisite for the above hot-fix to be applied

virtual techdays INDIA │ 9-11 February 2011 Enabling power management in R3  Below table illustrates the dependencies that are internal/external to ConfigMgr 2007 R3 to make it usable for Power Management Microsoft  Upgraded 170 ConfigMgr servers to R3 in a 48h duration over the weekend  Deployed an average of 50K R3 client hot fix per day Microsoft  Upgraded 170 ConfigMgr servers to R3 in a 48h duration over the weekend  Deployed an average of 50K R3 client hot fix per day

virtual techdays INDIA │ 9-11 February 2011 Why R3 for power management

virtual techdays INDIA │ 9-11 February 2011 Power Management Lifecycle

virtual techdays INDIA │ 9-11 February 2011 Power Management Lifecycle Phases Phase 1 - Monitor Current State  Gathering of baseline data  Examine the as-is state Phase 1 - Monitor Current State  Gathering of baseline data  Examine the as-is state Phase 2 – Power Policy Planning  Analyze usage patterns and existing power settings  Define power plans and power settings Phase 2 – Power Policy Planning  Analyze usage patterns and existing power settings  Define power plans and power settings Phase 3 – Apply power policies  Turn-on the power policies  Gather enforcement data Phase 3 – Apply power policies  Turn-on the power policies  Gather enforcement data Phase 4 – Compliance & Reporting  Verify compliance and take remedial actions  Report cost and CO2 savings Phase 4 – Compliance & Reporting  Verify compliance and take remedial actions  Report cost and CO2 savings

virtual techdays INDIA │ 9-11 February 2011 Phase 1: Monitor current state - detailed  Below flowchart indicates the sequence of activities that constitute the monitoring state Start Existing ConfigMgr 2007 infrastructure Upgrade all Site Servers to R3 Enable power management agent Deploy Client hot- fix Gather power management data Review data and qualify the power management opportunities Baseline power consumption (Kwh) and CO2 emissions per machine Understand various reports End

virtual techdays INDIA │ 9-11 February 2011 Phase 2: Power policy planning - detailed  Below flowchart indicates the sequence of activities that constitute the power policy Planning phase Analyze as-is data Verify the computer activity/Power settings reports Identify peak/off- peak plan & existing power settings Evaluate Desktop/Laptop differences Plan for collection structure considering exclusions Choose optimal values for peak/off-peak balancing productivity vs. User experience Finalize power plans/ power settings & enforcement strategy Evaluate the need for default vs. custom power plans Start End Conduct pilot to validate the strategy

virtual techdays INDIA │ 9-11 February 2011 Phase 3: Applying power policies - detailed Start Is power plan/ settings finalized End Finalize Power Plan/Settings No Yes End user communication Is there a roll-back Plan Yes No Define roll-back Define roll-back Create suitable collections Configure power plan/settings Turn on Enforcement Validation of enforcement Enforcement complete Is pilot Complete? No Conduct Pilot enforcement Yes Evaluate feedback and throttle settings periodically

virtual techdays INDIA │ 9-11 February 2011 Phase 4: Compliance Reporting- detailed Start Is enforcement Complete? Yes No Did you establish a baseline for comparison? Yes No Baseline avg. Kwh & CO2 emission per PC for a pre- enforcement month. Determine the post enforcement month for data comparison Compare and determine savings in Kwh, CO2 per PC Verify the computer activity report and compare the Computer vs. user activity pattern Verify the incompatibility report Verify the Insomnia report and identify the Insomnia applications Take Corrective action Re-verify compliance & continue fine tuning End Complete Enforcement

virtual techdays INDIA │ 9-11 February 2011 Best Practices

virtual techdays INDIA │ 9-11 February 2011 Best Practices  Below are some best practice guidelines evolved out of Microsoft Implementation of power management.  Pre-deployment baseline determination is critical  Ensure to have rich pre enforcement data is captured before enforcement. It is suggested to collect data for at least 6-8 weeks before enforcement.  Reduce collection complexity  Minimize the number of collections. This reduces complexity in the configuration of power plans, reporting, and troubleshooting  Plan for an exception process to accommodate exclusions  Not all systems are suitable for power management. You may want to exclude certain business critical systems and those that are needed to run 24X7. It is critical to plan for those exceptions  Consider other initiatives  It is important to understand other similar programs impacting desktop/laptop for avoiding functional conflicts and better end-user experience  Carefully consider results of the pilot programs  Finalize power management settings by carefully considering pilot results

virtual techdays INDIA │ 9-11 February 2011 OOB Reports

virtual techdays INDIA │ 9-11 February 2011 Power Consumption and Environmental Impact Report  Out of the box reports for power management are available through SQL Server Reporting Services (SSRS) Report. It is a key that your ConfigMgr environment has an implementation of power management for understanding of various power management reports. There are 19 individual power management reports available in R3. Enforcement

virtual techdays INDIA │ 9-11 February 2011 Computer Activity Report  Below snapshot is the Computer Activity report for a pre & post enforcement duration depicted in the snapshot

virtual techdays INDIA │ 9-11 February 2011 Power Insomnia Report  This report displays a list of common causes that prevented computers from sleeping or hibernating and the number of computers affected.

virtual techdays INDIA │ 9-11 February 2011 Power Settings Report  Displays an aggregated list of power settings used by computers in a specified collection

virtual techdays INDIA │ 9-11 February 2011 Other Key Observations  Enforcement without consideration of existing settings  Enforcing blindly might lead to increase in power consumption as there are chances that PCs with better power settings might be applied with a lesser aggressive settings. It is critical to understand the existing power settings before enforcement  Insomnia applications preventing sleep  Certain processes & applications can prevent a capable machine going to sleep. These are called Insomnia applications and can be a hurdle to effective power management. For win7 & vista the cause of Insomnia can be identified through ‘Power Insomnia Report’ whereas for XP OS, the Insomnia reason is not available. Certain known applications that causes Insomnia are  RDBSS - An open remote desktop connection  Share - An open file share  Complex Screen savers – Certain type of screen savers  Old video drivers  Media applications

virtual techdays INDIA │ 9-11 February 2011 Some Noteworthy facts To maximize power savings, EPA recommends setting computers to enter system standby or hibernate after 30 to 60 minutes of inactivity. To save even more, set monitors to enter sleep mode after 5 to 20 minutes of inactivity. The lower the setting, the more energy you save Notebook computers still burn around watts of power in active mode. During hibernate or sleep time, the power drops to approximately 1-3 watts. So energy saving is still significant. A notebook on AC saves power and extends the life of the battery when running on DC System standby – Drops computer and monitor power down to 1-3 watts and wake-up in seconds System hibernates - Drops computer and monitor power down to 1-3 watts and wake-up in 20+ seconds Turn off monitor – Again drops monitor power use to 1-3 watts System standby – Drops computer and monitor power down to 1-3 watts and wake-up in seconds System hibernates - Drops computer and monitor power down to 1-3 watts and wake-up in 20+ seconds Turn off monitor – Again drops monitor power use to 1-3 watts Source: energy star Savings opportunity of $25-$75 per PC annually  Below are the recommendations from Energy Star for consideration during implementation of PC power management

virtual techdays INDIA │ 9-11 February 2011 RESOURCES  For more Information  For detailed steps about the Configuration Manager 2007 upgrade procedures, refer to:  System Center Configuration Manager 2007 R3 home page:  Configuration Manager 2007 R3 – upgrade procedures:  Configuration Manager 2007 R3 – Data sheet: 9A7CA47E33EE/SC_Power_Management_DS_final.pdf 9A7CA47E33EE/SC_Power_Management_DS_final.pdf  To download a white paper on Microsoft IT implementation of ConfigMgr R3: 9c81-4e48c2c45681

virtual techdays INDIA │ 9-11 February 2011 Key Takeaways  A brief introduction regarding the Overview of ConfigMgr R3 and its deployment in your environment  A perspective of power management implementation lifecycle and workflow of sequence within each of the phases  Best practices that can be considered when implementing R3 in your environment  Overview of different types of ConfigMgr Out of box reports  Some facts from Industry sources Are you in ConfigMgr 07 environment? Do you have a SA agreement with Microsoft? Why to wait…’Go Green with R3’…

virtual techdays THANKS │ 9-11 February 2011