Somewhere between the physical and the virtual
System Center Blogs
Configuration ManagerThe team that supports Configuration Manager.
OrchestratorA blog by the teams who make and support Orchestrator.
Operations ManagerThe folks who make and support Operations Manager.
Data Protection ManagerBlog done by the Data Protection Manager product and support teams.
Service ManagerCommunications from the System Center Service Manager team.
Virtual Machine ManagerThe team that makes and supports Virtual Machine Manager.
System Center HomeThe home page for System Center on the Web.
System Center on TechNetTechNet's agglomerated resources on System Center.
myITforum.comRod Trent's Web site primarily focused on systems and configuration management.
SystemCenterCentral.comThird-party site that pulls together stuff across the SC suite.
Deployment ForumCommunity site about Windows deployment matters.
The Blogcast RepositoryWhere you'll find technical videos, blogs, forums and more on Config Manager as well as other System Center products.
FAQShop.comHints, tips, answers, FAQs on Microsoft's systems management products.
Virtualization FeedMaster aggregator of blog posts and twitters on virtualization.
Virtualization HomeFor all pertaining to the Microsoft Virtualization story.
For many years, IT client power management has been an area of challenge for many organizations. While energy-saving desktop and laptop hardware has been available for some time, power-saving settings are often disabled out of fears of data corruption, to support nightly IT operations, or simply from force of habit. The U.S. Environmental Protection Agency estimates that no more than 10 percent of all Enterprise PCs in use have their power management capabilities turned on—a staggering statistic considering the headway that has been made in other areas of power reduction in the data center and in building facilities. At the same time, over 80 percent of desktops in most organizations are completely idle after 6:30 P.M. Quite literally, “The lights are on, but no one‘s home.” All of this contributes to the inability of organizations to take advantage of the energy savings, carbon output reductions, and significant cost savings that are possible with enterprise power management.
System Center Configuration Manager 2007 R3 provides a comprehensive set of power management tools to enable centralized client power management. Configuration Manager 2007 R3 tools allow organizations to monitor current power usage patterns, develop intelligent power management policies, apply and enforce those policies, and provide robust reports against subsequent power savings and carbon footprint reductions.
With these tools, organizations are also able to develop flexible power management strategies that make sense, giving them the ability to think about how and when their users work, create policy exceptions for critical systems or tools to enforce different power settings for peak and non-peak periods.
Conserving power at the desktop level translates not only into potential cost savings through power consumption reduction; it also has the side effect of helping to reduce the overall carbon footprint of an organization. This, in turn, provides for greater movement toward green IT principles and, in the process, can help to make many organizations eligible for utility company rebates and refunds that may apply.
Client power management with Configuration Manager 2007 R3 can yield immediate and substantial cost savings with minimal effort and expense.
Why Is Power Management Important?
Energy Cost Savings - The most common driving force behind power management in many organizations is simple economics. Workstations use energy to spin hard drives, light monitors, and burn CPU cycles when not in use drain unnecessary power, resulting in higher energy bills. For a significant portion of the day, this equipment is unused and simply draining unnecessary power. Being able to manage the power settings of client systems centrally, making intelligent decisions about when a system needs to be powered or when power consumption can be throttled down can have a significant positive impact on the bottom line of an organization, particularly in a global economy where energy costs are significantly increasing.
Carbon Footprint Reduction - While often not the primary driver, a welcome benefit to overall energy reductions is a subsequent reduction in the carbon footprint that an organization places on the environment. The majority of power generated requires the release of carbon dioxide (CO2) in varying amounts, depending on the process used to generate the electricity. Wasted power subsequently means that more CO2 was released into the atmosphere than may have been required. Power management can subsequently allow an organization to demonstrate that it is making strides toward reducing its carbon footprint and implementing greener IT practices.
Energy and Utility Rebates - For many organizations, local power utilities have programs in place that offer electricity power reductions when specific energy reduction thresholds have been met or when implementing power-saving mechanisms such as client power management. For many of these utilities, there is a reporting aspect to the rebates which must be satisfied, and some require up to three years of reports to comply with the rebate requirements. Implementing power management techniques that allow for long-term reporting is required for the realization of these benefits.
Look for more to come on this topic, have a great week……..
Some resources for you:
Jeff Wettlaufer Sr Technical Product Manager System Center, Management and Security Division
Is there any ETA on the RTM date of R3?
I want to known when MS will release R3. Cheer
I have not yet seen any indication of whether or not an in-place upgrade from R3 RC to R3 RTM will be supported.
Comments in this blog are open and monitored for each post for a period of one week after the posting date. If you have a specific question about a blog post that is older than one week, please submit your question via our Twitter handle @System_Center