Quest KACE Systems Management ROI

Kevin Baldwin
PC Technician at Cape Fear Community College
If the professionals make a recommendation, consider it. Really, seriously, consider it, because there were some things we didn't do with Quest KACE that we should have, and it really hurt us in the long run. Even going back as far as active directory, there was some things that we didn't do with active directory that we were told by Microsoft engineers that this is what you need to do with active directory. Six, seven years later, we're looking at a network of two hundred almost VLANs. So, implementation of KACE was fairly smooth for us. If we would have done things exactly the way they would have told us to, which would have included flattening the network, like the Microsoft engineer told us to do when we went to active directory, things would have been even more smooth. We wouldn't have problems with wake-on-LAN, we wouldn't have problems with our scripting, we wouldn't have had problems with our SAMBA share. It would have been so much easier down the road to listen to the professionals and do exactly what they suggested we do, but because we had people who thought they were smarter than the professionals, we had some pains with implementation. View full review »
Find out what your peers are saying about Quest Software, Microsoft, Red Hat and others in Configuration Management. Updated: May 2020.
418,901 professionals have used our research since 2012.