We don't use the service desk feature at all. We use Zendesk, but I've been trying for years to get them to roll over and put this all in one, utilize the service desk, and just drag over what's in Zendesk into KACE. Unfortunately, I can't get them to listen.

They're hooked on Zendesk and they love the macros. This makes it hard to get them to change their process. You have to change the culture in that environment, and they're not ready to do that, yet.

We did not have anything.

We used Microsoft Deployment Toolkit (MDT). It just wasn't scalable enough for us, and it also wasn't customizable enough for us.

We used SCCM as well. It is much more complex, and it takes a lot of end-user training. That's why we decided to go with KACE.

After using other products, we want to stay with KACE. Earlier, we had a separate Request for Change application and a separate support system. We merged all those into KACE. It saved us a lot of money and a lot of time, and everything is central for our client base. They go to one spot in the self-service user portal, and everything is right there. This consolidation has probably saved us a couple hundred thousand a year. It is hard for us to do money points because anything that's Microsoft, such as MDT, SCCM, we get free through the Department of National Defense Microsoft Enterprise agreement. For us, there are no costs.

For patching we used WSUS and we always had issues with the patches not being applied and or reboots happening - causing end users to lose data. etc.

Spiceworks is simple, and we just we can integrate with the GPO. But all the best parts with Spiceworks are to download the documents with how many computers I have.  

The good part of KACE is that it can integrate with KACE, and we can manage the computers and the software. It offers remote access to know which users are on the computer. It is very fast.   

We did not have a previous solution.

n/a

We don't use WSUS in our environment anymore. However, we also don't use SMA for Windows updates. We use the Windows updates on the Microsoft website.

We used to use straight SCCM and found KACE way better because SCCM is all Microsoft. A lot of times Microsoft is not intuitive at all on third-party software, so you can only really update the Microsoft software. When we went from a SCCM to KACE, it was way easier because it's easier to update a software or even install a brand new software.

KACE has made our life much easier since we got off the Microsoft solution. The Microsoft solution was a lot harder to image over different ports and stuff. They would only have this one place where we could do all the imaging. Now, we have a whole building where we can image from. This means that we can image from our storage area, where we have a place to do our imaging. We can also image right at our desks, which is a lot easier. Once I get up to speed on updating the image and adding new software, then it will be so much easier for everybody else because the Microsoft solution always did the image in a weird way. They didn't have all the drivers for all the things that we have. With KACE, you can actually insert the drivers and make it work.

The SCCM solution for imaging was a nightmare. It wasn't a very good solution at all. With some of Microsoft items, we would need to just make a whole image of that model, which would take up more space on the server. With KACE, you just use one or two images. We have one department who uses this one model in all their trucks. They like it to be a certain exact way, where the icons and in the exact place with all the same this and that. For that one, we just make an image of that whole thing. Because we have the terabyte solution, it doesn't put a dent on the storage at all. With the terabyte solution, because we have that on the patching too, we don't have to think about whether we are using up too much space. I can go there once a month and clean up everything instead of having to be on top of it. It is just way better.

We still use SCCM for certain things that we have to do which need to be blanketed out and are easy enough solutions for them.

We did not previously use another solution. We only have experience with KACE Systems Management.

Prior to KACE, we had a piece of software, which is no longer around, called eSMART. It was developed by a company called ASAP, which was acquired by Dell. Dell purchased ASAP, decommissioned their eSMART product, and then wrapped up the functionality of the eSMART product into KACE. This is what led us there.

We use an internal application. For ticketing or our change management process, we don't use any solutions such as ServiceNow, Remedy, or Magic.

I'm not involved in networking. I work in internal IT. As a result, they use Palo Altos and Ciscos.

WSUS and KACE are currently in use.

At my previous job, I used SCCM, System Center Configuration Manager.

They did not use a similar solution prior to Quest KACE.

When the person who set up Quest first joined the company, he wanted to modernize things. People were leaving post-it notes or written notes on everyone's desk, and he wanted to implement a system to improve the clinic's way of doing business.

When he implemented the system, he implemented it with Active Directory to make it more fluent so that when something happened, they didn't have to go from one desk to the next desk.

We did not use another solution. Once we got KACE, I just don't understand how we held on for so long without it.

Before I came to the IT department, we used software from CA. It was a pain. But we switched because of the price. Also, the support wasn't that good from CA, as far as I remember. That was before my time. I moved to my current position after we shut down the CA software deployment.

We used Track-It! for some of our components previously, which definitely didn't do everything. In that case, it was just for asset management, not even for the help desk stuff. We switched to Quest KACE for what it offered and all the capabilities of what it did.

We previously used Acronis to do very basic duplicate systems.

We had a few different solutions. We had an access database we were using for ticketing and inventory, and patching was manual. Imaging was with a product that required an image for every different model of computer we had.

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

When I first started at my office, everything was done through Novell. At that time, we didn't have the ease of pushing software and remoting into the devices as we did with Quest KACE.

We also used another solution that wasn't exactly secure - it was touted as a secure solution but there had been some issues. It had been hacked before. And we were starting to get into an area where we were having outside vendors ask us for access into our network, so that started to become a concern for us.

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.

Active Directory would have been the main solution for asset management. For a ticketing system, we used Track-It!, but it wasn't that good at all.

We did use something that KACE replaced, but I don't even remember what it was.

SCCM is what we use for workstations, but not for server patching. We do have WSUS (Windows Server Update Services) running as a backup in case we want to use Windows Update. We do have other options available, but for servers, KACE is the primary patching system.

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.

We did not use another solution prior to this one.