1 / 25

virtual techdays

INDIA │ 9-11 February 2011. virtual techdays. Implementing a Power M anagement S trategy with System Center Configuration Manager 2007 R3. Chandramouli K │ Sr. Program Manager, Microsoft. INDIA │ 9-11 February 2011. virtual techdays. Overview of Configuration Manager 2007 R3

kaemon
Download Presentation

virtual techdays

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. INDIA │ 9-11 February 2011 virtual techdays • 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 S E S S I O N A G E N D A

  3. INDIA │ 9-11 February 2011 virtual techdays • 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 Our Team & What we do

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

  5. INDIA │ 9-11 February 2011 virtual techdays • 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 ConfigMgr R3 – at a glance • ConfigMgr 2007 R3 upgrade needs a pre-requisite hot-fix KB977384 on servers & clients • ConfigMgr07 SP2 is a pre-requisite for the above hot-fix to be applied

  6. INDIA │ 9-11 February 2011 virtual techdays • Below table illustrates the dependencies that are internal/external to ConfigMgr 2007 R3 to make it usable for Power Management Enabling power management in R3 • 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

  7. INDIA │ 9-11 February 2011 virtual techdays • Leveraging the existing ConfigMgr 07 hierarchy makes it easier to set-up R3 • ConfigMgr R3 provides complete set of desktop power management tools that can help organizations save on energy costs with minimal effort and expense • Centralized Power Management • Perform and control power management aspects centrally from an admin console • Granular settings • Works with the power management capabilities built into the Windows 7 OS, enabling administrators to optimize power settings on a granular level • Rich reporting • Report on power management aspects like Kwh, CO2, computer activity & Insomnia etc., Why R3 for power management

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

  9. INDIA │ 9-11 February2011 virtual techdays Power Management Lifecycle Phases Check compliance & report savings Monitor current 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 Power policy planning Apply power policies • 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

  10. INDIA │ 9-11 February 2011 virtual techdays • Below flowchart indicates the sequence of activities that constitute the monitoring state Phase 1: Monitor current state - detailed Existing ConfigMgr 2007 infrastructure Deploy Client hot-fix Upgrade all Site Servers to R3 Gather power management data Review data and qualify the power management opportunities Enable power management agent Start Understand various reports • Goals: • Prepare the existing ConfigMgr Infrastructure for power management • ‘Gather’ power management data for 6-8 weeks • Understand about your existing environment through various power management reports • Determine the opportunity for power management Baseline power consumption (Kwh) and CO2 emissions per machine End

  11. INDIA │ 9-11 February 2011 virtual techdays • Below flowchart indicates the sequence of activities that constitute the power policy Planning phase Phase 2: Power policy planning - detailed Start Verify the computer activity/Power settings reports Evaluate Desktop/Laptop differences Identify peak/off-peak plan & existing power settings Evaluate the need for default vs. custom power plans Choose optimal values for peak/off-peak balancing productivity vs. User experience Analyze as-is data Finalize power plans/ power settings & enforcement strategy • Goals: • Analysis of the base-line data and establish a current state • Verify ‘Out of box’ power plans and evaluate the need for customization • Determine the values for various power plan settings • Finalize power plans, power settings and enforcement strategy through a small pilot • Plan for exclusions Plan for collection structure considering exclusions Conduct pilot to validate the strategy End

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

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

  14. INDIA │ 9-11 February 2011 virtual techdays Best Practices

  15. INDIA │ 9-11 February2011 virtual techdays • 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 Best Practices

  16. INDIA │ 9-11 February 2011 virtual techdays OOB Reports

  17. INDIA │ 9-11 February2011 virtual techdays • 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. Power Consumption and Environmental Impact Report Enforcement Enforcement

  18. INDIA │ 9-11 February2011 virtual techdays • Below snapshot is the Computer Activity report for a pre & post enforcement duration depicted in the snapshot Computer Activity Report

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

  20. INDIA │ 9-11 February2011 virtual techdays • Displays an aggregated list of power settings used by computers in a specified collection Power Settings Report

  21. INDIA │ 9-11 February2011 virtual techdays • 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 Other Key Observations

  22. INDIA │ 9-11 February2011 virtual techdays • Below are the recommendations from Energy Star for consideration during implementation of PC power management 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 20-30 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 Savings opportunity of $25-$75 per PC annually Source: energy star

  23. INDIA │ 9-11 February2011 virtual techdays • For more Information • For detailed steps about the Configuration Manager 2007 upgrade procedures, refer to: http://technet.microsoft.com/en-us/library/bb680651.aspx • System Center Configuration Manager 2007 R3 home page: http://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-r3.aspx • Configuration Manager 2007 R3 – upgrade procedures: http://technet.microsoft.com/en-us/library/ff977066.aspx • Configuration Manager 2007 R3 – Data sheet: http://download.microsoft.com/download/0/A/C/0AC0350B-296E-4A9E-A0D4-9A7CA47E33EE/SC_Power_Management_DS_final.pdf • To download a white paper on Microsoft IT implementation of ConfigMgr R3: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7b31a05f-379a-4a09-9c81-4e48c2c45681 RESOURCES

  24. INDIA │ 9-11 February2011 virtual techdays • 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’… Key Takeaways

  25. THANKS│ 9-11 February2011 virtual techdays chkothan@microsoft.com

More Related