Configuration Management for the non SCCM admin

DCM was a feature in SCCM 2007 that got renamed to Configuration Management in System Center 2012 Configuration Manager.  IN 2007 It saw little use outside of FEP.  I encourage customers to take another look at it with SCCM 2012. Now it not only monitors settings and reports back on drift, but there is auto-remediation built in so you can have machines monitor settings for corporate compliance and rest themselves to standards if something gets changed that shouldn’t have.  I will be honest, it has a little bit of a learning curve to get your head wrapped around to get it working the way you like, but there are several examples out there to help get you started.  The latest example was done by one of our platform PFEs and I encourage you all to take a look and see if you might be interested in doing something similar to get more value out of your SCCM installation.

Comments (1)

  1. danovich_ says:

    I highly recommend taking a look at Microsoft Security Compliance Manager 3.0 for helping to create the configuration baselines, then import them directly into SCCM 2012.  


Skip to main content