System Center Configuration Manager (SCCM) Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
134 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.9 out of 101

Do you work for this company?

TrustRadius Top Rated for 2019

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (26-31 of 31)

No photo available
January 16, 2018

SCCM - Is it worth it?

Score 5 out of 10
Vetted Review
Verified User
Review Source
SCCM is being used to deploy new workstations, maintain workstation inventory, and apply patches and updates to operating systems and software. Our primary use is new workstation deployment and patching. We also use CM to deploy and manage Microsoft Endpoint Protection on our workstations. This software was purchased to optimize our hire on process.
  • Integration with active directory.
  • Integration with Windows workstations
  • Cumbersome and difficult to configure and manage.
  • Very few ways to manually process tasks; constantly waiting for CM to assess a system and determine if an update is necessary.
  • Requires far too much effort from a technician perspective compared to alternatives. Updating deployment packages, etc.
Large organization where you have enough technicians and can dedicate serious time to managing the system and keeping packages up to date.
Read this authenticated review
No photo available
January 16, 2018

SCCM 2012 Review

Score 8 out of 10
Vetted Review
Verified User
Review Source
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.
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.
Read this authenticated review
Lawrence S. Patterson profile photo
October 13, 2017

Microsoft SCCM Review

Score 8 out of 10
Vetted Review
Verified User
Review Source
SCCM is being used to manage users and computers. In coordination with Active Directory, software deployments, updates, device creations and deletions, user account creation, OU management, policy management are some of the activities performed through SCCM. SCCM is being used across the organization for application deployment and reimaging desktops when necessary. Multiple software installations can be performed by creating collections of computers and pushing the installations through the network. Other business problems include inventory of devices and remote connection to resolve troubleshooting matters.
  • Inventory reports can be created for specific O/S, microprocessors or connected monitors can be accomplished for annual computer refreshes.
  • Collections can be created to manage changes to multiple desktops.
  • Policies can be applied to user group for security and other purposes.
  • SCCM doesn't have some of the options that Active Directory provided for managing users or computers. It does have a great deal of flexibility and accessibility.
SCCM is a great tool for managing the application, computer and end-user environment. In coordination with Microsoft Active Directory, LANDESK and SQLServer most tasks are covered and easily accomplished.
Read Lawrence S. Patterson's full review
Scott Strader profile photo
August 31, 2017

Microsoft SCCM

Score 6 out of 10
Vetted Review
Verified User
Review Source
SCCM allows us to manage and deploy machines on our network. This is a nice tool to have in order to centralize things for updates and deployment. We also use this for imagining new computers as they come in from Dell. We use it across the whole organization to manage the systems on the network.
  • Image computers from a standpoint of having everything in a centralized location for deployment
  • Deployment control of updates managed by IT system admins
  • Overall Management of computers in the network
  • Deploying Software seems to be a challenge and has a low rate of success when pushing through SCCM
  • Imaging can be cumbersome and depend on updates and current status of the machine there can be many roadblocks in the imaging process adding several hours to the process. It also takes a decent amount of time to keep the image up to date with current standards.
  • Having the machine join as a client does not work consistently. Have to manually check each machine after the image to ensure that this task has been completed successfully.
The whole idea of SCCM is great. Just wish that the features that it has actually work seamlessly. It seems we are always having systems fall off from being a client and/or they are not able to be updated. I am yet to have any success in deploying software and having it actually make it to the host machine.
Read Scott Strader's full review
Ben Tusa profile photo
Score 1 out of 10
Vetted Review
Verified User
Review Source
I am not part of the team that owns SCCM rather I am impacted by SCCM on the servers and desktops that I do manage. We use SCCM as our primary means of patch/audit/software deployment solution for our desktops and servers.
  • SCCM doesn't do anything particularly well that I know of.
  • SCCM could be improved everywhere. IF you manage to get your patch collections configured it does seem to patch servers most of the time.
It's pretty bad in a VDI environment. If you are using 20 year old IT techniques I guess it wouldn't seem so bad. If it's primary purpose is to make managing systems easier it completely fails at the make things easier part. It just seems to introduce complexity at every turn.
Read Ben Tusa's full review
No photo available
Score 7 out of 10
Vetted Review
Verified User
Review Source
We use SCCM to deploy software packages and images, manage anti-virus solutions and track individual clients on the network. The IT department manages SCCM but all of the clients in the organization are connected and managed through the system. We were able to build some solutions that allowed tech support to instantly pull up information on a client and see vital stats at a glance. This makes software and hardware troubleshooting easier for the techs that have thousands of clients to support.
  • Deploy Images
  • Monitor network and system health
  • Deploy software packages based on user permissions
  • Imaging takes longer than it did with previous solution.
  • The client-side setup takes a long time to establish a connection after an image, delays software deployment
The amount of details we can gather about individual clients is pretty incredible. We know when the last virus scan happened and what items were flagged as suspicious. We can specify what users get access to which applications based on where their computer resides in the organization. We can connect to clients remotely to help troubleshoot issues.
Read this authenticated review

About System Center Configuration Manager (SCCM)

Microsoft System Center Configuration Manager (SCCM) is a system monitoring and management platform that can be deployed as an agent, via the cloud, or on-premises. SCCM can manage systems across OS types (Windows, Mac, Linux), as well as multiple environments, including servers, virtual environments, and mobile devices from a single management console. SCCM supports scaling capabilities, such as future application delivery.

SCCM also provides extended system monitoring services. The platform includes a customizable reporting tool to inform future business software decisions. It also enables endpoint protection from malware and vulnerability identification within the monitored systems and infrastructure.

System Center Configuration Manager (SCCM) Integrations

System Center Configuration Manager (SCCM) Technical Details

Operating Systems: Unspecified
Mobile Application:No