concept Configuration Manager in category system administration

appears as: Configuration Mager
Learn System Center Configuration Manager in a Month of Lunches: Covers SCCM 1511 and Windows 10

This is an excerpt from Manning's book Learn System Center Configuration Manager in a Month of Lunches: Covers SCCM 1511 and Windows 10.

I jumped online and researched options, and Configuration Manager (ConfigMgr) came up time and time again as the best-of-breed solution for Windows deployment. The next day I spun up a server and spent the next two weeks trawling through TechNet articles and blog posts about how to set it up, configure it, and get Windows deployed.

Back in the days of Configuration Manager 2007, many admins made heavy use of so-called health-check collections. These were device collections that reported on different aspects of client behavior, such as how many clients had failed to send through inventory or how many reported having the client installed but were marked inactive.

With Configuration Manager 2012 and later, you don’t need to use health-check collections anymore, because the console gives you an easy way to keep an eye on what’s going on, and because the client has a self-healing function, designed to keep things running smoothly.

These approaches are fine, but are generally inefficient. In both cases, you need to start digging into the root cause of the problem, and often this process involves disrupting the system’s user. To streamline the process, you’ll use the Client Center for Configuration Manager.