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.
We love to hear about how well our products work. More importantly, we love to hear that our products are doing their intended job of saving our customers time, money and resources. And yet, there’s even an additional component that is key to our products’ successes: the ability to define key partnerships that allow us to give our customers a complete solution.
Today, we want to highlight a recent 1E case study with Ford Motor Company that actually comprises each one of these principles. It shows how Ford expects to save over $1M per year just by combining the power of Configuration Manager with 1E’s NightWatchman. And if that's not enough, by utilizing this combined solution, Ford expects to reduce its carbon footprint by an estimated 16,000 to 25,000 metric tons a year.
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