Try our new research platform with insights from 80,000+ expert users

Microsoft Configuration Manager vs Quest KACE Systems Management Appliance (SMA) comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 15, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Microsoft Configuration Man...
Ranking in Patch Management
1st
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
81
Ranking in other categories
Server Monitoring (7th), Configuration Management (4th)
Quest KACE Systems Manageme...
Ranking in Patch Management
10th
Average Rating
8.8
Reviews Sentiment
6.8
Number of Reviews
39
Ranking in other categories
Client Desktop Management (3rd), Endpoint Compliance (8th), Remote Monitoring and Management (RMM) (12th), Unified Endpoint Management (UEM) (8th)
 

Mindshare comparison

As of July 2025, in the Patch Management category, the mindshare of Microsoft Configuration Manager is 12.8%, down from 17.3% compared to the previous year. The mindshare of Quest KACE Systems Management Appliance (SMA) is 4.4%, down from 6.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Patch Management
 

Featured Reviews

MikeNelson2 - PeerSpot reviewer
Deployment recovery works well but requires configuration improvements
While I do not use the product frequently, many issues were due to configuration rather than the product itself. I cannot give an exact recommendation as it is not my area of responsibility. The team that uses it finds it adequate. It is presently good enough for us not to investigate other options. Overall, I rate the product a six out of ten.
Scott Tweed - PeerSpot reviewer
Low maintenance, reliable, and easy to create packages
I like how when you click on the device, it shows you everything that has changed as well as the software versioning. I am really enjoying the inventory aspect of it. The deployment process for both deploying and creating a package is straightforward. I believe the inventory in KACE is superior to SCCM's. I know with SCCM I could do things like remote console into machines via the agent's remote console, but that is not a feature that is provided in KACE. I know that at least in the Systems Management Appliance, I can't get to it. I'm not sure how distribution works, with distribution points. I'm not sure if KACE has that feature. You could use an SCCM to set up distribution points at remote sites so that they don't have to download patches or software from across the country. If you have a DP or something similar, they could pull it down.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution is highly scalable."
"Microsoft Configuration Manager is integrated with other Microsoft products."
"There is a faster time to rollout. If we get a new PC, it can be ready for productivity right away."
"SCCM is a stable solution."
"The product is very stable compared to older versions."
"Microsoft Endpoint Configuration Manager is very scalable."
"Patching is the main feature because SCCM is made to control the entire environment without manually interpreting. So it is good to use for patching."
"The most valuable feature of Microsoft Endpoint Configuration Manager is patch management."
"This solution makes it easy to control assets and upgrade all types of software."
"You don't have to be an advanced user. Rather, in terms of ease of use, this product is right where it needs to be."
"I like how when you click on the device, it shows you everything that has changed as well as the software versioning. I am really enjoying the inventory aspect of it."
"KACE’s knowledge-based articles are very good."
"This product made the job easy to do without having to go put hands on the machines."
"The most valuable feature is the ability to monitor updates—the software versions—on machines so that we can keep everything compliant."
"We're able to deploy software and push out fixes to endpoints faster than ever."
"The big pros of Quest KACE Systems Management are its simple interface, and simple, direct management. It's very easy to maintain and manage the device, and it's easy to get it up and running. You can have it up and running in an hour..."
 

Cons

"Regarding this, I'd like to mention the agent situation. When the agent on an end-user device is not functioning correctly, it can be quite problematic. It would be highly beneficial if there were a self-healing mechanism in place. Essentially, if the agent becomes corrupted or encounters issues, it should be able to rectify itself autonomously. This is particularly critical because, in order to utilize a tool like MECM (assuming you're referring to Microsoft System Center Configuration Manager), we need to deploy agents, known as AsMs, on all the devices we use, such as Windows 10 or Windows Server. Sometimes, when we deploy configurations or updates, they don't apply properly due to agent issues. This issue has been present since we began using MECM around 23 years ago. Unfortunately, there is currently no built-in mechanism for the agent to detect its own problems and initiate self-repair. Microsoft doesn’t have any feature to scan vulnerabilities and hence, they could include those."
"The solution is on-premises. The cloud version of the product, if a person needs to be on the cloud, would be InTune, which already exists as an option. SCCM doesn't need to offer cloud features for this reason."
"There's no way to say, "I want this maintenance window to be on the second Tuesday of the month." It's strict. This window is this and that's it. You can't fluctuate."
"Microsoft Endpoint Configuration Manager can improve by allowing us to schedule the scripts, we don't have a script scheduling option and have to do it manually."
"Not everything is readily available, and there are a lot of commands that are only executable via PowerShell."
"There is a reboot issue with the patching. Sometimes, if patching runs into any issue whatsoever, it doesn't reboot but it doesn't tell you it errored out. It just sits there and we don't find out until the next day whether it patched or not. That was a big issue for us. We're working through that. They added some stuff in there now where you can actually tell reboot is pending. But we still need some kind of notification that if something fails or is pending, we know. We shouldn't have to go in and look. They don't have anything for that right now."
"The analysis is something that can be integrated. Their report analysis can be improved a little bit due to the fact that most of the time complaints policies are saved by the admins. It's something that we need to look into and search for."
"On some hardware, we'd like an easier way to get peripherals attached."
"I wish Quest KACE Systems Management Appliance (SMA) would have a top-down approach since we use orgs; currently, we have to go into each org to deploy applications when we need them all across the university."
"Sometimes the information is not as real time as it's supposed to be."
"I would sure like them to be able to copy and paste out of OneNote. That drives me nuts. You can't copy from OneNote into KACE."
"KACE implemented the possibility of reducing the network speed of the KACE agent. You can set it so that it takes whatever network speed you want or you can set it to 5 Mb, to save network speed. You set it for all the computers, but it would be preferable to separate between VPN connections in our home office and the local area. It would be great to be able to set separate speeds for different VLANs."
"The K1000 doesn't communicate well with some clients without SMB. There are some issues with getting things to image correctly because they rely on SMB, and SMB is a protocol that is being removed due to security reasons. Organizations are trying to rely less and less on SMB. I know Quest is aware of it. They've talked about having a new version that wouldn't rely on SMB for connection to the clients, but they haven't gotten there yet."
"I think it should have the ability to have the applications automatically update. It would be really helpful if this would override what the user might choose to do."
"The problem is that it's harder to directly emulate a lot of the stuff that the group policies do, using the KACE solution. With regular group policies, you just specify the various settings you want to change on the workstations, and then you specify the workstations and—while it's kind of an ugly mess—it does it. Whereas on KACE, you really have to know what you're doing with scripting to effectively script those exact same changes."
"The solution needs to have the ability to push out managed feature updates from Microsoft in a more seamless way."
 

Pricing and Cost Advice

"Overall, I think it's fine. It's pretty much in-line because there are ways to offset it with the Office 365 licensing."
"Microsoft provides a steep price for their enterprise products, but they offer very competitive pricing for their legacy customers."
"We use the tool's free license. It is expensive."
"Along with buying a license for MECM, we also have to buy a service called CMG (Cloud Management Gateway) which is a virtual machine in the cloud with which you can link your MECM to the Azure tenant so as to manage teleworkers."
"The price is competitive and reasonable."
"Pricing and licensing are a downside of SCCM. It's expensive. I'd have to confirm this, but I think they changed the licensing to core-based instead of socket-based. It's not cheap, because you have to buy the software, you have to buy SQL. Another thing we learned from talking to Microsoft is that they provide you a license for SQL if you run it on the same box as the primary server. If you run it outside that box, you have to buy SQL. Microsoft does recommend you running it on the same box because of performance. But then, in order to run SQL, SCCM, and everything on the same box, you better have some resources. It's an expensive solution. There's no doubt about it."
"I would rate the cost as eight out of ten."
"The price of Microsoft Endpoint Configuration Manager is expensive."
"We pay annually for technical support."
"Their pricing is per end-point device. There is an initial cost for the license for the server, which is pretty low, and then there is a per end-point device license, which is also fairly low. So, the pricing is still reasonable."
"The pricing is fair."
"Licensing is done on a per device basis, so it's dependent on how many agents you've got installed."
"There are no costs in addition to the standard licensing fees."
"The pricing is great. It's billed annually and it's very reasonable."
"We are a university. So, we have a very good price for the system. I think the price for the system is worth it because of the security patch management. The security patch management is very important for us. The price is very good for KACE SMA, the functionality you get, and the patch management."
"Licensing is very straightforward. They don't overcomplicate it. This is not a Cisco product where you have to have 30 different licenses just to open the box. It's pretty much set-and-forget. You pay an annual license... The cost is in the mid to upper range, but the ROI exceeds the outside cost, especially once you've had the system for a while."
report
Use our free recommendation engine to learn which Patch Management solutions are best for your needs.
860,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Government
10%
Computer Software Company
10%
Manufacturing Company
8%
University
11%
Computer Software Company
10%
Government
10%
Financial Services Firm
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

How does Ansible compare to Microsoft Endpoint Configuration Manager (SCCM)?
Microsoft Endpoint Configuration Manager takes knowledge and research to properly configure. The length of time that the set up will take depends on the kind of technical architecture that your org...
How to choose between ManageEngine Desktop Central and Microsoft Endpoint Configuration Manager (formerly SCCM)?
ManageEngine Desktop Central is very easy to set up, is scalable, stable, and also has very good patch management. What I like most about ManageEngine is that I can log on to every PC very easily a...
What do you like most about SCCM?
One of the standout features of SCCM is its application management capabilities. It allows us to create packages efficiently and deploy them to specific groups within our network. This streamlined ...
What is your experience regarding pricing and costs for Quest KACE Systems Management?
The pricing is in the middle range of the market, not too expensive but not the cheapest either.
What needs improvement with Quest KACE Systems Management?
The user interface needs improvement as customers have mentioned they do not like the interface since it is not an SMA-based interface and lacks a manual configuration option.
What is your primary use case for Quest KACE Systems Management?
The main use cases for Quest KACE Systems Management Appliance are touch management, software and hardware inventory, and software delivery.
 

Also Known As

Microsoft Endpoint Configuration Manager, System Center Configuration Manager (SCCM )
Dell KACE Systems Management
 

Overview

 

Sample Customers

Bank Alfalah Ltd., Wªrth Handelsges.m.b.H, Dimension Data, Japan Business Systems, St. Lucie County Public Schools, MISC Berhad
Waypoint, Mattos Filho, Meetic, Gems Education, Green Clinic HealthSystem, Service King
Find out what your peers are saying about Microsoft Configuration Manager vs. Quest KACE Systems Management Appliance (SMA) and other solutions. Updated: June 2025.
860,592 professionals have used our research since 2012.