1. Home
  2. Unified Endpoint Management (UEM) Solutions
  3. Microsoft Intune Reviews
  4. User Review of Microsoft Intune
SCCM 2012 Review
January 16, 2018

SCCM 2012 Review

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Microsoft System Center Configuration Manager

We use SCCM for image deployment, windows update management, anti virus management with endpoint protection and as a backup remote management tool. Only the IT help desk is using this currently.

We got this in our origination, because Microsoft wanted to assist us in upgrading all of our machines to Windows 10, to move away from Windows 7. We are currently only licensed for workstations and do not actively use it on servers currently, but I believe we will in the future.
  • Anti-virus management. Deploying, managing and removing end point protection is simple. Compared to other products like Symantec, Webroot, Vipre and Trend Micro, threat protection was good and updates were easy. When it was time to remove, it was simple and did not require additional tools to remove the product.
  • Patch management was good. Works well with WSUS and reporting was decent and helped us get caught up on patching that we were lacking.
  • Image management. We have Windows 7 and 10 deployments set up and use SCCM to configure everything for capture and deployment.
  • I would like to see better training and explanation for configuring SCCM to import existing images that have been stood up. While I did manage to get it working, the documentation from Microsoft itself is lacking. I've found that I have to spend a lot of time researching from 3rd parties that have stumbled through it.
  • Remote access to workstations. SCCM remotes in to a machine via the IP and we have found that in an environment where there is wireless and wired and sometimes machines flop back and forth, we cannot always remote in to a machine. If they were able to use the SCCM agent or go by system name, we would be able to remote in to a PC easily and replace the 3rd party tool we have with Dameware.
  • Access restrictions. Doesn't provide an awesome way to lock down what a user can and cannot do within SCCM. We have some level 1 techs that we need to be able to modify a task sequence, but we don't want them to have full admin access.
  • Cannot comment on this. Even though I am a manager, I am not involved with this particular information.
We are using SCCM because it was given to us for free and we are currently inbetween a tool system that was not fully deployed and selecting a new system. We currently have Landesk, that was managing images, our ticketing systems, patching and remote management. Unfortunately, it was not fully deployed correctly, so not all areas are working. The other issue is that Landesk was bought out by Ivanti and will not be continued in the future. We are going through a RFP process currently, deciding what tool will take these tasks over permanently.
Really good for internal IT. Would never work for a company that would use it to manage clients. Unless they stood it up per each client and maintained it, this works best for an IT department to manage itself.