Quest KACE Systems Management Appliance (SMA) Reviews

We use the KACE solution for endpoint management, since our posture is based on endpoints. We have almost 2,000 endpoints.

We have two KACE boxes. It's not a virtual appliance, it is a physical appliance.

It's not only saving time but increasing IT productivity. If you have a KACE box, you're going to save a lot. Having KACE is a blessing for IT administrators for endpoint management. They can do a lot of work remotely, as well as troubleshooting, mass deployment, and mass uninstallation. KACE is very intelligent and it has its own uninstaller.

An example of how KACE helped is that there was a McAfee service-provider who was visiting us to do a McAfee upgrade for our antivirus system. They are experienced people, the subject matter experts for deploying McAfee, the client, the agent, et cetera. He was having an issue uninstalling a McAfee firewall client. If you deploy a McAfee in your network, the uninstaller should be from McAfee, but the uninstaller from McAfee was an outdated version. Uninstalling the firewall client from McAfee requires a lot of effort. It's not impossible, but it's time-consuming and if you try to uninstall from the control panel, of course it won't allow you. There is a popup for the password and, without that, a lot of problems are going to occur. 

He told me he was facing this issue. The solution for uninstalling it was provided by KACE. I demonstrated it to him for one of our clients and he was shocked. He started writing that command, and the next day he sent me a text message, saying, "Thank you. You made my life easier." He gave that command to another customer, a client of his who is an IT administrator, to run that command via a batch file to all the end-users, because they didn't have KACE. 

For an IT department in any organization that pays for endpoint management, KACE is really a blessing for them.

The most valuable feature of KACE is the mass package deployment. There are a lot of endpoint management solutions in the market. The way KACE responds is with the installation management feature, which is done in a very intelligent way, as well as scripting. It's wow. It's really wow. On top of that, there is a mass undeployment feature as well.

For example, we had an issue a while back where there was a plugin for the SAP module being deployed to almost 1,800 computers. It was taking a backup, restarting the machine, and updating it automatically. Our end-users were complaining every day. We were receiving hundreds of calls. We found out that the issue was this plugin. It was updating and restarting machines without informing the users. When we did inventory, we started finding this application, but we didn't know about the history of that application. Luckily, KACE gave us an uninstallation path, the command line. When we deployed it, believe it or not, it worked as a massive uninstallation feature and it took care of almost 1,800 computers within one hour.

It's really very time-saving stuff. It's all up to you, how you are going to utilize KACE, but if you know the way, the features are very user-friendly and it does not require scripting. There are built-in features where you can build your own script and execute it remotely through KACE. 

I have never officially worked on the service desk model of KACE, but when I went through it, it was fine. It's good for a small IT department. It's more than enough. It has asset inventory and printer inventory. You enable the SNMP features and you can get reports on printers and even printer cartridge utilization reports. It's a very handy tool for organizations that have a lot of endpoints in place.

We also used the Systems Deployment Appliance for Windows 7. Now, we are planning to use it for the Windows 10 upgrade for the rest of our machines. If you're going to capture the image of a machine and re-image that machine, it's great. Over the network, it took us 18 minutes to deploy 19 GB of images. And that was not on the same campus. It was a remote campus. For the same campus, we also used it to deploy and it took us, I think, 16 minutes and a few seconds for almost 18 GB of Windows 7 images.

There are a lot of nice features.

There is a module for agent management when you right-click on the inventory. If you want to connect remotely you can do so. But sometimes the agent check-in does not happen. You can do the first check-in through a script, at the same time. 

But there should be a mini toolbox, like the competitors of KACE have, with the small features for KACE administrators. That would make their lives easier. If you are troubleshooting a specific endpoint, remote control is available as is Wake-on-LAN. But if you want to execute some commands, you have to use a third-party tool, the PS tool. If they would integrate those small things, it would make KACE more powerful.

I have been using Quest KACE Systems Management for almost five years.

Initially, four years back, we were having a lot of issues with the KACE agent. But as the solution has grown, the maturity level has really increased and the stability and the reliability have as well. My KACE machine has not been down for a single day in the last five years. It's a very stable product.

It's really reliable now and very intelligent on top of that. When we do a mass deployment, there isn't a single day when my network admin asks me, "Why are you deploying this?" I deployed Office 2013 with KACE, in a massive way, and our network guys never said, "Oh, we can see there is a bandwidth spike." The way that KACE intelligently deploys and manages installation is great. It's really kind of a miracle. I believe that they select a group, copy the file over the network to the cache of the local machine, execute the command, and then install the media file on the local machine.

KACE is very scalable.

We started with 700 clients and today we are at almost 2,000 clients. There hasn't been a single day where I have been concerned about the scalability or the of KACE. 

Quest Support for KACE is good. They are responsive and they always give you a solution in a  timely manner. 

We faced a problem two or three years back, an issue with the inventory of Forescout Secure Connector. We could not find out how many machines had Secure Connect Connector because it's installed as a service. It was a very complex problem for us and KACE support came up with a solution: Create a new, customized inventory to get Secure Connect to be considered as a process. On that basis, we had a new entry and this solved our problem.

We have not used another asset management solution in this organization. I did use SCCM in my old company.

For us, the initial setup was not complex. The problem was that the environment, the network we work in, is a very restrictive environment. We have a lot of firewall policies and a layer of firewalls across the network. Because of the complex network architecture, we struggled a bit with the network discovery of the endpoints. We used one of the best practices: Do auto-discovery and then apply the agents.

At that point in time, I didn't really know KACE. It was a new box. I started discovering what would be next. The next thing that happened was another blessing from KACE which was having it do the Active Directory group policy deployment for the agents. I deployed it and that discovery was running for almost a week, but we started installing the agent within about four to five days. It was time-consuming. It took us two weeks because we ran it organization-to-organization because it would have slowed down the network. We did not want to take any risks. If we had taken the risk, it wouldn't have been an issue, as far as the KACE agent deployment is concerned. 

Now, whenever a new machine comes into our network, the KACE agent is automatically installed. Right after that, KACE is installing one of our NEC client agents automatically. Then, KACE will discover that this machine is a part of the McAfee agent, and if it is not, it will automatically install the McAfee agent. Then I configure McAfee to sync with Active Directory. 

So for us, when a new machine is joining, the desktop engineer will run only one command, GPUpdate. The machine will restart and then all the group policies, the KACE policies will be deployed. KACE will then install all of our small plugins automatically and they're good to go.

One of the best parts of KACE is when you go for a version upgrade. Once you do a version upgrade for any KACE module—any KACE virtual appliance or physical appliance—it's very user-friendly. In addition, the agent upgrade is a miracle. When you do the agent upgrade for the KACE appliance for the first time, it's "super-wow". The last upgrade I did was for almost 1,900 PCs, and all the agents were updated automatically when I upgraded the agent package. It took only 24 hours.

I am the only KACE administrator in our organization, but there are desktop engineers who log in to KACE. They review machines, but I do all the administration and configuration. They use it to take inventory or check the memory and see what replacements are required. They are read-only administrators.

We have seen a lot of return on our investment in KACE. One area is headcount. We are a military hospital. Imagine having 2,000 computers on the ground in different remote locations, yet having only seven desktop support engineers. If you do the math, there should be no way that seven desktop engineers can support 2,000 endpoints. Even the best-case scenario is one engineer working with 100 desktop machines, max. That gives you an idea of the headcount savings.

We are also saving on the licensing fee, compared to other endpoint management solutions.

KACE is very easy to use and user-friendly compared to the other endpoint management tools, like Microsoft SCCM and other third-party tools, in terms of IT administration. Compared to its competitors, it's easy to get machine inventory.

If any organization wants to manage its endpoints, having KACE, as I said, is a blessing for the IT administrators.

I would give it an eight out of 10. I am being demanding because there are some more improvements that can be made. But KACE can be a superpower in endpoint management.

We use this solution to manage our workstations and desktops. We can manage our hardware inventory and licenses, remotely install software, update software, and generate reports.

We do not use it to manage servers, only workstations.

We have a lot of different machines and devices in our environment. When I need to upgrade or install specific software applications, they can be deployed en masse and over a short period of time. It saves us a lot of time, which is the biggest help that KACE provides.

This product has helped our IT operations increase productivity. We have been able to create labels for machines and users, which has been useful. Also, we have been able to create rules in KACE that segregate software according to each area. Using this capability, our team management has improved as well as our customer relationships. 

This solution makes it easy to control assets and upgrade all types of software.

The mass deployment of software is easy to do.

KACE is very intuitive and easy to use. I am new to using the KACE Systems Management solution. Today, I was amalgamating software for the first time. It was easy to do. The employee that I was helping liked the way that it resolved the problem. It is also easy and fast to transfer my knowledge of KACE to another person.

This product provides good visibility into our machines, which is useful. It provides details about the software, hardware, and what is connected to it. It is very easy to use.

I would like them to implement VBScript language in KACE Systems Management. Currently, we can only use PowerShell.

We recently updated to the latest version, and we haven't yet seen all the features that it previously had.

I have been using Quest KACE Systems Management for between three and four years. It was deployed several years before I joined the company.

Stability-wise, it is fine. I have never seen this product crash or timeout.

If the server is working, then KACE Systems Management is fine.

We have four help desk staff who work with it. We don't manage servers with KACE; we just manage stations. We do not use it in our daily routine.

As our company and environment have grown, scalability has not been a problem. The scalability of the tool seems to be good. We currently manage 639 endpoints.

We use Quest Premier Support and contact them a lot. They have a Brazilian analyst who is very good to work with. He is skilled, has complete knowledge of the product, and has helped to resolve several problems that we have had in our environment. He never leaves us with big problems.

I would rate technical support a ten out of ten.

Positive

I have worked with SCCM, which is quite like this product, but the KACE Systems Management interface is better. 

KACE Systems Management makes it easy to find information because it is intuitive. 

The pros of SCCM are that it has more integrations and APIs with Microsoft software. This is useful when it comes to managing an environment. Because it is a Microsoft product, it has more integrations than other competing software.

I was not involved in the initial deployment.

KACE saves us time when it comes to maintaining our machines. For example, we sometimes need to retrieve information from the operating system of our machines. Normally, this has to be done manually, and we move from station to station to complete the task. With KACE filtering the results, we can do it in 20 seconds.

The pricing is fair.

KACE is a useful product for us. As I am new to it, I don't have very many suggestions for improvement. Rather, it has been very good, useful software.

I would rate this solution as eight out of ten.

We have several use cases for KACE and a lot of them are related to the helpdesk. For example, they provide assistance with modifying the helpdesk, client distribution, and maybe a tad bit in scripting on how to use it.

I've used the KACE tickets a lot.

This solution provides us with compliance management. We used it for security updates including Windows security, Dell, and other products. Another feature that we use is patch management. In fact, we patch other products all the time using KACE. I have Windows and Dell updates running bi-weekly, whereas other products are done weekly. Microsoft servers are an example of something that we regularly patch.

The combination of the features is important, although I'm just happy that it all works. It's fairly easy to use once you figure it out.

The system helps a lot when it comes to updating and configuring everything the way we need it to be in our environment. In particular, their support engineers are really good, although the system usually configures and updates mostly on its own. 

Price to using KACE, we were using emails. Now that we have a ticketing system, everything is monitored and everything is saved. For example, with the service desk portion, it's a lot easier to track because of the OSV files. They take up a lot of storage and as such, they get stored in archives. This means that it's hard to find those emails, so it's difficult to see what people said. Something we would look for is how we resolved an issue by following steps X, Y, and Z. This information is all available in the description of the ticket and by using KACE, we can find it easily. As far as the service desk operations go, this solution has been A one.

Using this solution saves us lots of time, especially when it comes to performing updates. We only have one on-premises server, and we have somebody that updates it, but prior to using KACE, there were lots of errors that would occur. For example, one update superseded another. Now, it is put on the automated run with a smart ticket and the server is always up to date. I estimate that we're saving at least 40 hours per month, based on the fact that we have 170 computers. It takes a long time to push all of the software updates to every one of them.

When we consider patching and software application updates, our productivity has increased by at least 80%. This has been major for us, especially with COVID and since people started working from home. It's been tougher to manage everybody but with KACE, it's made the job a lot easier. For example, the KACE agent looks at the client and it updates everything automatically.

The system gives us visibility with respect to whether a user is online, or the last time they were online. While online, it also gives us real-time status updates.

The only feature that we aren't using yet is asset management, and that is something that we are working on.

This solution is easy to use. None of it is very difficult, although I had to learn it from the ground up and it wasn't very easy when I first started with it. However, progressively, as I put in tickets and began using the service desk, the Quest help, and the technical support, they showed me how it works. Usually, after they showed me one time, I was able to understand what I needed to do. Eventually, it was really easy to use.

The inventory is really good, where it automatically updates catalogs. When I check on things, it's right there, and it even has zero-day patches. When you fine-tune it and set up the automation, it makes life much easier.

The patch management security is also A one.

It would be nice if the asset management capability was a little more intuitive.

The software asset management functionality is an area that needs to be improved. It could be more automated because when connections need to be made, such as when I connected Adobe and my malware remover, the process was pretty much manual.  For example, I have to tell it which and how many licenses we have, and I have to keep updating it. KACE has what they call Smart Labels and they are supposed to automatically detect things, but it seems that they don't detect anything. I put all of the information in, and it still won't do it. It makes you wonder why you're putting the information into the system in the first place.

I have not been able to connect to Active Directory, which is a ticket that I've had open for several months. It looks like the problem may be on our side. I've been working with the firewall team, which is a third-party vendor, and even their developers can't figure it out. Each vendor is pointing fingers at the other. I just want it to work.

I have been using Quest KACE Systems Management for approximately two years.

I like the stability a lot. It doesn't crash. We've had a few hiccups but it's definitely not worse than some of our vendors. The downtime is near 0%. Some of our vendors have a lot of downtime.

Scalability-wise, this product is great.

When we first implemented KACE, we had approximately 80 computers that we needed to install it on. We now have 170 computers.

We will continue to use this solution going forward. Every time we stage a computer, we make sure that we put KACE on it. Once we do that, we pretty much don't have to worry anymore. We're setting up more PCs and we're going to be hitting the 200 mark, probably at the end of the year. We have been hiring a lot of people and I expect it will continue.

There are three people who use KACE but I am the primary one. I'm the only person that makes changes and monitors the system regularly.

The technical support is pretty good but we still have cases pending. There is one case that we have had open for several months and I'm not the happiest about that, but for everything else, the assistance has been pretty spot on. It's hard to complain about the support.

Sometimes, I figure it out myself after opening a ticket but usually, they can get the job done. They are much more responsive than most vendors. I don't know if they have SLAs but if they do, then I would say that they're meeting them. They usually contact me either the day of, if it's early enough, or the next day, which is nice.

If I speak with any one of them, it doesn't matter. I've worked with multiple support engineers from KACE and they all seem to know what they're doing.

Usually, I have to contact them for the higher-level stuff. For example, I didn't know about how security certificates worked because I had never used one before.

The vendor has Premier support available, although we do not use it right now. We haven't looked into it yet but because we're growing and don't have enough IT people, Premier support might be ideal. For example, I have read that they help with VBS scripting, and I don't know it, so that would help me to learn it a little bit faster. Also, they save certain things for Premiere support. I had asked the service desk if I can change the category of a service ticket and they told me that I could, but it was a custom option. For that kind of thing, you need to have Premium support. I plan to call the vendor and get a quote for the service. That said, for everything that's not custom, they help a lot.

Overall, they're very proficient and they're very knowledgeable about the product.

We were using Datto RMM before, and KACE is much easier to use. I wasn't the most familiar with the old solution but with KACE, I can do things beyond monitoring. For example, I can do distributions or use security updates. With Datto, I basically used it to see what PC people were on.

Before I was hired, an IT company used to manage our infrastructure and they were the ones using Datto. We moved away from the IT company, which is why we switched.

We have not used any of the freeware products that are available or tried SCCM to achieve the same functionality.

It was definitely complex but that is because I'd never seen anything like it before. It wouldn't be a fair assessment to say that it was the most difficult thing, but it was a lot of information and I'd never used smart labels before. I was very confused at the beginning.

But, after I put in tickets, they did take the time to go back over it with me. After they showed me maybe once or twice, I understood what a smart label does. From that point on, it was very easy to create smart labels and automate the system.

It takes perhaps five minutes to install KACE on one computer. The longest part is pulling it down from the server. Once it's copied to the local machine, it only takes a minute or 90 seconds to install.

We completed the deployment in-house.

The pricing is great. It's billed annually and it's very reasonable.

My manager was already very familiar with this solution, which is why it was chosen. We didn't evaluate other options.

I have seen other monitoring tools that you use with a PC, where they are part of the assets. With this one, you have to run a custom script and you have to do a lot of custom stuff. When you do custom work, you have to pay more money, obviously. It means that there is an extra cost but other than that, it's pretty good.

KACE provides capabilities for mobile device management, although we don't use the feature. We also don't really use the monitoring system at this point.

My advice for anybody who is looking to implement KACE is that it's fairly easy to use and once you learn it, it's a very simple product. It's not simple in function, but the ease of use is there and you can very quickly learn what you need to do to get things done.

Also, if you know a little bit more about VBS, you get stuff done a lot quicker. 

Overall, it's a great product, I'm really happy with it, and I feel like it gets the job done.

I would rate this solution a nine out of ten.

My company had bought some new machines. We used the tool to do some basic settings to ship every machine the same way and undertake the Windows deployment. We did the scripted installation. The tool helped us deploy custom software for specific departments. We also did Windows updates with the product. 

We like the tool's most features. It is a straightforward tool that is easy to use. 

We had issues with the tool's support. We are a Dutch firm and everything has to be in Dutch. We were not able to do the alerts. You were required to tweak them a lot to get them in the language that you preferred. The solution's support depended on the person that you got online. Sometimes, the response was fast and other times you needed to wait a long time. The support also depended on the levels of support that you had requested. 

I have been working with the solution for 10-15 years. 

I would rate the product's stability an eight out of ten. 

The tool is perfectly scalable. 

When we setup the product, a technical engineer from Dell supported us. I am not sure if there is the same level of support these days. 

The product is reasonably priced. 

I would rate the product an eight out of ten. I find the product very useful and helpful. The tool has everything like Mobile Device Management that is needed to service a company. The tool has communities where you can seek help. You can visit their support site for technical support. You can also avail support through settings. 

We primarily use this solution for the help desk, but we also utilize the scripting portion of it to automate things that would otherwise take us a long time to do manually. We're just now trying to start using the asset management portion of it as well, tying users to various equipment.

In addition to these things, we use some of the reporting and some of the file synchronization features.

An example of automation is pushing patches out to users. For example, I just finished creating a bunch of patch schedules.

All of the features that this product offers play an important role in our company.

We have a K1000 and it offers a single pane of glass for endpoint management. It would be nice to have a K2000 because it would then include image updates for hard drives, which our version does not. Otherwise, as far as endpoint management is concerned, it is complete.

We have utilized the IT assets but have been largely unsuccessful in using the modules for licensing and warranty.

When it comes to updating and configuring everything the way we need to have it done in our environment, it takes care of 90% of the work. It would be nice if it had a packager for software when we're dealing with executable files because not everything has a managed installer, unfortunately. It means that we have to trick it into doing what we need to do sometimes. For the most part, it does what we require.

The most valuable feature for us is the helpdesk. Just being in the IT industry in general, we have to have something to track what we're doing day in and day out, whether it be a project or end-user support. It helps us keep all that together in one place. The help desk is what everybody in our department uses it for the most.

The scripting is a very valuable feature, as it saves us time on pushing certain things out to the users, such as software and patches. The patches definitely need some help.

When you get to patch management, it's complicated. I have had to call technical support about it several times. The labels can get kind of confusing as well. I know that there are a lot of them and if I spend more time in it I'd probably understand it better, but anytime I have to create a label for something, I just get lost in a rabbit hole.

We tried the licensing a few times, but we never got it to work properly. It's always really buggy. It is a similar situation with the warranty information; it doesn't always pull that information accurately. It would be helpful to have those pieces addressed because we can't use them. It's been a few years since we touched it, so they may have been addressed by now, but every time we updated, we would go and test it and it just wasn't keeping track correctly.

The KACE Go Mobile App crashes a lot, and it always has. I would love to see that get fixed because it's very convenient when it does work properly, but most of the time it does not. This experience is uniform across multiple devices that we've tried over the years. I've read the reviews on the app store and all of the different messages being sent to the developers about how this needs to be fixed, and nothing ever happens. This is an area that could use some improvement, for sure.

It needs to have better Unix crontab options for patch management. We want to have the ability to use expressions because we would like to do our patches every two weeks. As it is now, with the way it's formatted, it won't allow us to do that. Essentially, we need more customization as far as the schedules are concerned.

We had a report where there were some custom fields in KACE, and we would be able to fill those out and utilize them for reporting. In one of the updates, those fields were removed. They were custom-built and they still exist in KACE, but from what I understood from the release notes and from speaking with a support rep, those fields are no longer available in reporting. Without being able to report them, it defeats the whole purpose of having fields there in the first place.

We are still able to do some customization in the reports, but the custom one, two, three, and four fields in the user details are in the appliance, but we can't find them on a table anywhere inside of the database.

Another thing that we would like is to have at least a limited degree of write permissions for the databases. It would make it a lot easier for reporting or even certain things that can't be exported, to have at least some kind of write control to the databases. I understand, as a company, why they don't want to give that ability to some people because of the can of worms that it opens, but it would just be really helpful to be able to automate some things, rather than have to go in and update the stuff field by field.

For example, the help desk configuration, where you have your categories and subcategories, and you can go in there and assign users. We have more than 100 of those line by line. Anytime we get a new help desk person or we make a change to who the owner is of a certain category, we have to go in there and manually set it, each and every one of them, and it takes hours to do.

Essentially, we would like to have more control over it and assume responsibility for problems should they occur. If we break something then it's our own fault.

Since we upgraded to version 10.0, all of our reports are broken. I haven't yet called in about that to find out what the problem is. At this point, we get a bunch of unknowns and question marks whenever we pull a KACE report off of our report server. It may not be a serious issue.

I have been using Quest KACE Systems Management for almost seven years. At the company, it has been in use since before I started.

The stability is great. We've only had it crash once, and that was because of a power outage. Otherwise, it's been awesome.

It used to be slow at some points, but over the years, through the updates, it's gotten a lot more responsive. There are still a few things here and there that take a little bit longer than I think they should to load, but it's not worth mentioning.

For the most part, this product grows with our needs. Back in the day, when we first got it, it was owned by Dell. All of our equipment is from Dell, including our servers and our laptops and computers, our workstations. It fits together very nicely.

All of our end-users use it, if they need to put in a help desk request. As far as the daily use of it, the ins and outs, I'm the administrator and I make sure that all the updates are done. I check on the patch schedules.

In IT, there are three of us. Aside from me, we have an IT admin that uses it to track his projects, as well as some tickets that get assigned to him for reporting requests.

On top of tracking these items, he uses some of the scripting functionality, when it's server-related. As an example, last week, he used it to handle changes that we had made regarding a print server. We changed our print server over to a new one, and he utilized scripting to remove the old server and add the new one. That's what he mainly uses it for.

Our IT director doesn't really use it for much of anything, other than his project-tracking and being able to look at everybody's queues, like mine and my IT admin's, just to see where we're at during the day in more of a supervisory role.

My experience with technical support goes back a long way and the service has changed over time. Overall, it's been a mix, based on luck of the draw. It depends on who I get on the phone. Some people know exactly what they're talking about, and some people don't, and we have to go through several emails or several phone calls just to try and figure it out.

Whenever you call in and you request a callback and the representatives say, "Okay, yes, we'll have a technician call you within the next couple of hours," it's about a 50/50 shot whether they actually call you back or not. Sometimes, they just send you an email instead of calling you. This can be a problem because I have all my emails filtered, so, if I'm looking for something important, I can get to it quicker. However, if I'm expecting a call from KACE support, I'm not going to be looking for that email. That's been a frustrating experience.

Over the years, it's gotten a little better, but it's still the same thing with the emails and the time it takes for them to get back to you. Or, if they just don't happen to be there the next day and somebody else has to take that ticket, that is another thing that can be frustrating. There is room for improvement there, as well.

We did not use another solution prior to this one.

It was implemented before I arrived but I have been involved in the upgrade process ever since I joined the company. It is straightforward most of the time but there can be some complexity and it can vary. For example, getting the backups done can be complex, as can things be when changing from version to version. However, for the most part, it has been as easy as just pressing a button and doing an update.

I would say that overall, it is 75% straightforward.

The help desk is super simple to use and we saw our return on investment a long time ago, just in man hours alone.

We used to use a spreadsheet to track all of the things that came through IT, and that is cumbersome. It takes 20 times longer to do. You have to make sure that somebody else doesn't have the spreadsheet open. There are only so many ways that you can put in different columns and rows to get all the information you need, especially when you have to do updates. It was really clumsy the way it was done in Excel.

Another example of where it saves us time is with the scripting, whenever we have to do an update to our transportation management system. It is the biggest piece of software that we have, it's the most complex, and there's a lot of moving pieces to it. We used to actually have to go to each individual computer in the company, of which there are 100 or more, and manually update the different pieces. Now, we can do it with the click of a button in scripting, and then just go around to the few people that it may not have hit properly and manually do it there. It saves a lot of time.

We pay annually for technical support.

I looked at Spiceworks at one point just to see what their solution was like. We didn't fully implement it. Rather, I added a couple of computers on it. It was mostly for watching the network and I didn't evaluate it to the point where I could compare it with KACE.

My advice for anybody who is implementing this solution is to be ready for a lot to come at you at once because it does so many things. It's a blessing and a curse at the same time. Also, if you're going to go with a solution from KACE, I would suggest the K2000 rather than the K1000, just because it has more.

We do not plan on changing solutions anytime soon.

I would rate this solution a six out of ten.

We use KACE for patching. 

I am impressed by the service desk ticketing and asset management.

I've had some issues with patch catalogue, which seems to have expired. Quite a few people have reported that they are struggling with it.

I have been using Quest KACE Systems Management for three months now.

The program is very stable.

We only have three people using this program in our company, but I believe it is scalable. I don't think we will increase our usage soon, though.

The technical support is good.

The initial setup was quite complex and I really struggled. It took me around 15 minutes to complete the setup, because it was a trail-based version.

I rate this program an eight out of ten. I will recommend it to others because it is simple and understandable.

My primary use case of this solution is to help us obtain accreditation in the UK of Cyber Essentials Plus. It is a program that is sponsored by the UK government which encourages UK companies to obtain a certain level of cyber-security within their cyber environment. The Quest KACE product helps us get an overview of all IoT(Internet of Things) devices that are accessing our environment.

The most valuable feature is the ability to have an overview of all devices that are accessing our environment.

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 initial setup was straightforward. There were some excellent step-by-step instructions sent to us. The instructions were also accompanied by videos, which were very informative.

It was a very attractive price. This is a huge feature of this product. If you would "credit score" this product versus others out there on the market, this one has a very attractive price.

We also looked out VMware Airwatch and MobileIron. But, we chose KACE. It just made more sense for us.