MICHAEL,BERTUIT,PASSION,SYSTEM,CENTER,FR,SCCM2007,SCCM2012,SCOM,SCSM,SCVMM,SCDPM,ORCHESTRATOR,MICROSOFT,WINDOWS,SERVER,HOW,TO,CAPTURE,DEPLOY,WIM,SERVICE,MANAGER,2008R2,2010,2012,2013,SYSTEM-CENTER.FR,SP1

Manage, Monitor, and Report: Implementing a Power Management Strategy with System Center Configuration Manager 2007 R3

Add a comment novembre 8th, 2010

Hi,

Great news, the document  for Manage, Monitor, and Report: Implementing a Power Management Strategy with System Center Configuration Manager 2007 R3 is available!!!

What’s in this document?

This document help to implement with best practice the power management Strategy by the new update System Center Configuration Manager R3.

Example of document content:

Best Practices

Microsoft IT captured a number of best practices during the Configuration Manager 2007 R3 planning and deployment. The following reflect lessons learned, what worked well, and what required improvement.

  • Pre-deployment baseline determination is critical to measuring project success. To ensure enough data for a meaningful analysis, data gathering should continue for an adequate amount of time before enabling client power management policies. This depends on hardware inventory cycles and the amount of comparison data desired. Microsoft maintains a three-day hardware inventory reporting cycle. With these conditions, it became a best practice at Microsoft to gather data for a period of four to six weeks prior to enabling power management policies. Configuration Manager 2007 R3 monthly reports were more effective because of the appreciable baseline period.

  • 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 of business critical computers. Because not all computers can be included in a client power management program, a structured exception process is key to identifying and excluding those computers.

  • Carefully consider results of the pilot programs. Finalize power management settings by carefully considering pilot results. Also, consider feedback from stakeholders and end-users about their business requirements and their experience during the pilot.

  • Consider other initiatives. It is important to understand other client desktop or laptop initiatives. This understanding helps avoid potential functional conflicts. In addition, introducing multiple changes at once can significantly impact user productivity.

  • Create a structured communication and feedback mechanism. A structured communication plan and feedback mechanism helps to ensure transparency, and minimizes impact on user productivity. A communication channel in addition to e-mail can help communicate program objectives. Microsoft IT built out an intranet website, which included program objectives, the phased deployment schedule, answers frequently asked questions, exception process information, and a link to the formal exception application process.

  • Communicate clearly and concisely. Consider planning the number and frequency of communications in advance. This helps to ensure reach and thoroughly prepare users for any changes and potential impact.

Distribution by Operating System:

 

Designing the Collection Structure:

 

 

Power Environmental Impact Report:

For read in complete and download, click HERE

<!–[endif]–>

Situation

Microsoft is committed to an ambitious goal of cutting its enterprise carbon emissions by 30% over a five-year period. To help contribute to this goal, Microsoft IT wanted to build on its System Center Configuration Manager 2007 desktop management infrastructure to implement a flexible and centralized power management solution. MSIT also wanted to fully leverage power management capabilities in products such as Windows 7. The solution needed to effectively manage, monitor, and report client power utilization across the enterprise.

Solution

Using System Center Configuration Manager 2007 R3, Microsoft IT deployed a power management solution to 165,000 desktop and laptop computers. Through new tools that enable centralized management, powerful reporting, and a deep understanding of current power settings, MSIT realized significant energy and cost savings. The solution provides a high degree of flexibility, and different levels of enforcement. In addition to delivering on power usage and carbon reduction goals, the solution also delivers on the Microsoft IT-specific goal of driving product feedback to deliver a successful power management product.

Benefits

· 27 percent drop in the amount of power used by the managed desktop computers

· 12.33 kilowatt hours per desktop computer per month savings

· A projected savings of $12 – $14 USD per desktop computer per year, based on currently reported data

· Centralized power management and enhanced reporting capabilities

· Leveraging existing client management infrastructure minimizes cost and expense

Products & Technologies

· System Center Configuration Manager 2007

· System Center Configuration Manager 2007 R3

 

Executive Summary

According to most experts, the IT industry contributes two percent of the world’s carbon emissions. Microsoft® is committed to reducing its own, and the global IT carbon footprint. Software and technology innovations from Microsoft enable people and organizations worldwide to reduce their impact on the environment. In addition to providing key technologies and solutions that help support ‘Green IT’ initiatives, many Microsoft customers can learn valuable lessons from the Microsoft IT deployment and management experience of those same solutions and technologies.

The purpose of this white paper is to describe how Microsoft IT (MSIT) successfully deployed Microsoft System Center Configuration Manager 2007 R3 to provide a centralized power management solution to 165,000 physical client desktop and laptop computers across the enterprise. The paper shows how Microsoft IT leveraged System Center Configuration Manager 2007 R3 to implement a cohesive power management strategy that takes full advantage of the native power management features integrated into products such as Windows® 7, Windows XP, and Windows Vista®.

By deploying Configuration Manager 2007 R3, Microsoft IT added centralized client power management tools and reporting functionalities to its existing Configuration Manager 2007 client management hierarchy. The solution builds on existing Configuration Manager 2007 capabilities, including software distribution and hardware inventory capabilities. Configuration Manager 2007 R3 provides centralized, console-based administration of power management settings and policies, and delivers robust power management reports.

With Configuration Manager 2007 R3, MSIT now has the ability to more deeply understand the current power settings environment, assess power saving opportunities, and centrally manage client system power settings. All of these capabilities help to realize energy and cost savings.

Intended for technical decision makers, and other IT professionals that are interested or involved in environmental sustainability, or Green IT initiatives, this paper describes the Configuration Manager 2007 architecture that Microsoft leveraged to enable the solution. This paper details the Configuration Manager 2007 R3 deployment, placing special emphasis on defining the power management strategy, and the realized benefits of implementing an enterprise-wide power management solution.

It is important to note that this document should not function as a deployment roadmap. Organizational operational environments differ, and the unique needs of individuals and operational criticalities should be considered. The goal is to define a suitable power management strategy that produces net power savings, without compromising user productivity.


related post

Facebook comments:

  1. No comments yet.Be the first ?
  1. |
    novembre 8th, 2010 at 15:44 | #1

    [...] in this document?…For read the complete post, click HERE Published Nov 08 2010, 04:43 PM by mbertuit Filed under: Monitor, and Report: Implementing a [...]

Comments feed