Overall Satisfaction with Microsoft System Center Configuration Manager
We use MS SCCM in our organization to deploy and manage System Center Endpoint Protection. We also use it to deploy known good configurations of operating systems and programs for new machines to our network. We use SCCM to report and alert on the health status of servers and endpoints. We also use it to manage Windows and third party applications.
- Patch Management
- OS Deployement
- Health Status Reporting
- Application Deployement
- It can be a house of cards at times. If one little thing fails it seems like the whole thing comes crashing down. SCCM is NOT for the faint of heart.
- Setup is quite a chore. The setup process it NOT straight forward and relying on a third party walk-through is essential.
- Diagnosing what is wrong with SCCM can be a daunting task. Again... not for the faint of heart.
- A positive impact we had when we implemented SCCM was that it streamlined OS Deployment.
- A positive impact was that it helped us get a handle on which clients were patched and which still needed their patches.
- When the patch management portion stopped working on our SCCM instance it caused us quite a headache and broke a lot of endpoints having them automatically upgrade to windows 10 without us being able to stop it.