Has anyone switched from SCCM 2012 to KACE?

I just started working for a non-KACE shop recently, and right now we're at a fork in the road. The choice is to upgrade the existing SCCM 2007 to SCCM 2012 or look at other options such as KACE. This is a smaller environment with maybe 400 nodes mixed across windows, macs, and Linux. I am wondering if anyone has had to do a recent evaluation of both solutions and what drove the decision to chose one over another. I'm already well aware that KACE has advantages such as ease of use, ower TCO, and less extensive training to drive, but I don't want these to be the only metrics I use to drive the decision. What helped you make your decision, and what did you decide on?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Hobbsy 7 years ago
Red Belt
I needed some information to see how Landesk and other solutions stacked up and downloaded this doc earlier today, I think you will find it of use.


Posted by: zookdj 7 years ago
Second Degree Blue Belt
Price, ease of use, low maintenance overhead, excellent tech support, and the support desk functionality were all big factors in our decision to move away from System Center about 6 years ago.  When we were using SC I spent more time just trying to get it to work.  It was actually more of a time sink for us than a time saver.  With the KBox, even though it isn't perfect, it is still much less work to get it going and start reaping the benefits compared to using Microsoft's complicated systems management solution.  (Microsoft seems to love making things overly complicated, whether it is systems management, licensing rules, you name it.  :-)

TL;DR: For a small shop like us (around 140 nodes) it didn't make any sense to use Microsoft's solution, and the KBox made a huge improvement in our IT efficiency.

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ