From today I’ll be writing a series of posts regarding my experiences with deploying and managing Microsoft System Center Configuration manager in my test lab scenario.
Before I start today, I would like to give a brief description about System Center Configuration Manager and what it does:
Microsoft System Center Configuration Manager 2007 (ConfigMgr) provides a comprehensive solution for change and configuration management for the Microsoft platform, enabling organizations to provide relevant software and updates to users quickly and cost-effectively.
Configuration Manager 2007 provides the following features:
■ Collecting hardware and software inventory.
■ Distributing and installing software applications.
■ Distributing and installing updates to software, for example security fixes.
■ Restricting computers from accessing the network if they do not meet specified requirements, for example having certain security updates installed.
■ Deploying operating systems.
■ Specifying what a desired configuration would be for one or more computers and then monitoring adherence to that configuration.
■ Metering software usage.
■ Remotely controlling computers to provide troubleshooting support.
Please see the following figure to understand where does the SCCM fits into the System Center Solution:
Configuration Manager provides a comprehensive solution for change and
configuration management, enabling organizations to provide relevant software
and updates to users efficiently. Configuration Manager features provide solutions
for many key issues that IT administrators face while managing Windows-based PC
So now we have a overview of what exactly Configuration manager does and how it helps managing Windows based IT infrastructure, we’ll go into deploying it into my lab.