What users are saying about
92 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
Top Rated
123 Ratings
92 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.5 out of 101

SCCM

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
Top Rated
123 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

Likelihood to Recommend

Ansible

Great for automating groups of servers and ensuring updates are pushed to all of them (simultaneously if needed). It's hard to manage large groups of servers, and this tool makes it almost too simple. If there is only one server that is unique from the others, Ansible will not be as useful, but can still help track your changes.
Dylan Cauwels profile photo

SCCM

I know many people have a great experience with System Center Configuration Manager, but it is not suitable for organizations that cannot commit a significant amount of time to configuration and deployment. For example, my organization uses Jamf Pro for Mac management. It took me a couple of days to configure every setting needed for an adequate Mac deployment. System Center Configuration Manager took way longer. Most MSPs in our area do not want to deal with it due to its complexity either. A big organization will find the product more suitable, as configuration tasks are the same whether an organization has 1000 or 10,000 computers, the installation will be more useful with scale. In my case, trying to deploy System Center Configuration Manager as a personal project while doing other tasks was not a success.
No photo available

Pros

Ansible

  • Agentless. For our implementation, this is the single biggest factor. If we have to touch the machine and install an agent before we can start managing it, that's already too much effort and slows us down.
  • Re-entrant. This is not unique to Ansible, but certainly a huge improvement over custom scripts and such. Because it's such a huge effort to make scripts re-entrant, most of our scripts did not allow an elegant way to recover on failure. Manually cleaning up the half-attempt and re-trying is still too cumbersome, and being able to just re-run Ansible is a great improvement!
  • Infrastructure as code. This is new to Ansible, and there are still a few minor bugs with their AWS modules, but it's been a huge help being able to define our infrastructure in an Ansible playbook, commit it to source control, and use one tool for all our DevOps tasks.
John Grosjean profile photo

SCCM

  • Remote Control works well and does not require a lot of configuration. It must be understood that the Remote Control feature of System Center Configuration Manager is different from RDP, as it does not establish a separate user session and allows a tech to troubleshoot issues in a way visible to a user.
  • It is easy to add client devices for management, and multiple options are available (push, Active Directory, etc.)
  • It's modular and extensible. For example, a third-party company, Parallels, makes a System Center Configuration Manager plugin to manage Macs from the same console.
No photo available

Cons

Ansible

  • There are conflicting stories on how best to organize a role's structure. Old documentation exists, and as Ansible has grown directions have pivoted a bit. This should be trued up.
  • Pull-based Ansible is a compelling use case. Ansible should come up with a pattern which supports this configuration.
  • How to integrate ServerSpec infrastructure integration testing is sorely lacking. Ansible should curate practices and docs around this.
No photo available

SCCM

  • Complexity of initial deployment requires 6 to 8 months of planning and preparation. This is one of those projects that will take a year to implement.
  • Managing user roles in the system can be made easier with use of templates and a more robust role management tool.
  • System and agent upgrades as well as patching the SCCM back-end systems should be easier.
  • Offer a hybrid cloud-based solution with pre-built models and templates for faster deployment and appeal to mid-size enterprises.
No photo available

Likelihood to Renew

Ansible

No score
No answers yet
No answers on this topic

SCCM

SCCM 8.0
Based on 1 answer
Will renew as it is part of our core set up for patch management and software deployment
No photo available

Usability

Ansible

No score
No answers yet
No answers on this topic

SCCM

SCCM 6.0
Based on 3 answers
The console is not intuitive and does not work well often. Due to the complexity of the product, documentation can be confusing. When properly configured, routine tasks like OS deployment, remote control, and software deployment are easy to do. Troubleshooting of System Center Configuration Manager issues is hard, as there are various logs, and their content can be hard to understand.
No photo available

Performance

Ansible

Ansible 8.4
Based on 5 answers
Out of the box, Ansible can be slow over a bad connection, as it's establishing an SSH connection to the target server for each little task. There are some adjustments you can make to the defaults that greatly improve performance. And if you run Ansible on the same network as the target (i.e. by using a jump box or Jenkins server), then it can be crazy fast. I'd give it a 10 for speed except that it does require these adjustments first.
John Grosjean profile photo

SCCM

SCCM 7.6
Based on 14 answers
Due to SCCM being developed by Microsoft and meant to work with other Microsoft products, there has been no performance issues on servers nor client devices. We have done two upgrades without any unplanned downtime or issues, and there has been no requirement to roll-back any deployment or updates of SCCM due to any bugs or vulnerability found later. This is a well made product for specific use and specific platform. Other competitor products can do more and compatible with other Operating Systems, but if there is no requirement for that, SCCM is the best of breed.
No photo available

Support

Ansible

No score
No answers yet
No answers on this topic

SCCM

SCCM 8.0
Based on 3 answers
Support is good and gets the work done.
No photo available

Implementation

Ansible

No score
No answers yet
No answers on this topic

SCCM

SCCM 8.0
Based on 1 answer
Need documentation, prior experience, and training for successful implementation.
No photo available

Alternatives Considered

Ansible

In the time of integration, we chose Ansible instead of Puppet because it was simpler to use, based on Python and didn't require additional server environments to run. Of course, there are a lot of different alternatives like Chef or Salt Stack.
Blagovest Petrov profile photo

SCCM

Well, both of them work with the same objective basically. I would say that what makes Microsoft System Center Configuration Manager stack up against the Ivanti Endpoint Manager is the number of features and where the product focus its attention. Other than this, both applications have the same value and work great.
No photo available

Return on Investment

Ansible

  • Ansible is a great investment if used for its well-suited scenarios. It has had a positive impact on my clients who used it to modernize their application deployment process. Ansible has 1) increased the reliability of the deployment process and 2) reduced scripts maintenance overhead.
  • Since Ansible is simpler and faster to get started with - compared to centralized configuration management solutions - it can be tempting to use it initially for simpler applications/infrastructure that are anticipated to evolve to complex ecosystems, you may find yourself having to rewrite in another tool in such cases.
Aiman Najjar profile photo

SCCM

  • It had a positive impact on saving IT some time with deployments.
  • It had a positive impact on saving IT some time with patching tools.
  • It had a positive impact by allowing us to keep track of deployments.
No photo available

Pricing Details

Ansible

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

SCCM

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison