Try our new research platform with insights from 80,000+ expert users
System Administrator - Desktop Operations at Manhattan College
User
Great Powershell support and managed installations with excellent reliability
Pros and Cons
  • "We're able to deploy software and push out fixes to endpoints faster than ever."
  • "We'd love to see support for larger dependencies in the scripting feature."

What is our primary use case?

We primarily use our KACE system for imaging, deploying software, and deploying fixes to Windows computer labs. 

We don't use the active directory in our environment, so pushing out changes to local group policy is something we use our SMA for often. 

Additionally, managing over 1000 Windows endpoints of varying models and manufacturers is no easy task. Management of these endpoints involves utilizing the inventory and scripting features on the KACE SMA. 

We even use KACE SMA on our VDI infrastructure, helping to maintain and track those endpoints.

How has it helped my organization?

The KACE SMA has helped make our endpoint team work more agilely, efficiently, and productively. 

We're able to deploy software and push out fixes to endpoints faster than ever. 

Our turnaround times for new software installation in our numerous computer labs on campus have never been quicker. 

With KACE, as soon as a request comes in or a report of a broken bit of software, we can quickly prepare and deploy a fix with the SMAs scripting feature - which has proven invaluable to our organization. This makes my team's day easier and our clients even happier.

What is most valuable?

The Powershell support in the SMA has proven invaluable time and time again as an organization that doesn't use Active Directory. We can easily make changes to our endpoints via Powershell scripts with the SMA, empowering us to make changes to our endpoints not always capable to a non-windows shop. 

Managed installations is also a great tool. Managed installations give my team a quick and efficient way to deploy software to many computers all at once, without the need to manually go to each computer and tediously and manually install the software. 

What needs improvement?

We'd love to see support for larger dependencies in the scripting feature. We sometimes use scripting to copy large files (5GB+) to 30+ computers at a time, and having a way to do this directly through KACE without breaking up the files into smaller ZIP files would be great. 

Additionally, we'd love to see the return of the 5-second auto refresh. We've found that 30 seconds between auto-refreshes in the KACE UI is sometimes too long. 

Other than that, the SMA is a fantastic product that makes life easier and keeps clients happy!

Buyer's Guide
Quest KACE Systems Management Appliance (SMA)
October 2024
Learn what your peers think about Quest KACE Systems Management Appliance (SMA). Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,485 professionals have used our research since 2012.

For how long have I used the solution?

I've used the solution for five years.

What do I think about the stability of the solution?

KACE is an incredibly stable product. We have had very, very few stability issues, most of which are isolated to old hardware and versions.

What do I think about the scalability of the solution?

KACE is incredibly scalable to many, many devices.

How are customer service and support?

The Quest KACE support team is the best in the business. I always come out with an answer, and the support engineers are kind and professional always. I can't speak highly enough about them.

How would you rate customer service and support?

Positive

How was the initial setup?

I was initially a bit scared of the complexity of setting up the KACE environment, however, in the end, it was very easy.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Director of Technology at Unirede
Real User
Reduces the effort and time for providing a new installation and maintaining the environment
Pros and Cons
  • "Asset management is most valuable. It is essential for all customers. The other features are also useful, but asset management is most important."
  • "Its dashboard needs improvement. Currently, there is no way to modify the dashboard. There should be more flexibility so that we can create views according to our use case."

What is our primary use case?

We use KACE internally in our company to deliver and manage services for our customers. We access it every day. We are on the support page every day. KACE is open in my browser all the time.

We provide our own KACE services to customers. We are managing more than 85,000 machines by using KACE. In terms of the setup, sometimes, there is a shared environment, and sometimes, there is a dedicated environment. 

Our customers are in retail, power, healthcare, and education. We have more than 20 customers with recurring contracts, and we have had many customers for one-time projects. 

Our customers use KACE for inventory and software delivery and distribution. They use it to apply policies and generate reports. We have some customers who use it for Service Desk. We have done some customizations on Service Desk for ITSM in terms of assets and CMDB to maintain all information related to IT assets.

How has it helped my organization?

It provides IT asset management, compliance, software asset management, mobile device management, and patch management. We don't use mobile device management and patch management internally, but we do provide it to our customers. We have some customers who use MDM and patch management. Having all these in one solution is very important for us because Unirede provides monitoring to customers. By using the KACE solution, we are able to provide endpoint management for our customers. This is a gap that KACE filled for us. It is very important for us. We get more than 30% of the revenue through endpoint management for our customers.

It saves time, which is its most important benefit. When you automate tasks, there is a lot of time-saving. Based on the feedback from our customers, it has saved more than 50% time.

It provides what we need for updating and configuring everything the way we need it to be in our environment. For me, it is very easy. It is not a big deal to update when necessary. 

We use Systems Deployment Appliance (SDA) for Windows and Linux devices in our environment. We have used SDA for internal use, for training, and for our customers. We have a few customers who have SDA in place on-premise. We sometimes also use the product to migrate the environment. For example, we use it for migrating from Windows 7 to Windows 10. At the beginning of the pandemic, some of the customers bought a lot of notebooks to make their employees work from home, and we provided migration services to them. By using SDA, we are able to do implementation in a short period, such as one, two, or three months. It is very good for automating the deployments, but, of course, it can be improved. Improvements are always welcomed.

It has increased IT productivity. With SDA, we can reduce a lot of time to provide a new installation. From hours, it gets reduced to minutes. Some customers have told us that their technicians used to spend the whole shift deploying one machine, whereas, with SDA, they could do it in less than one hour for one machine. They were also able to provide a new installation in 30 minutes.

We use machine profiles. We have profiles for the HR department, technicians, etc. We create smart labels related to this information, and we associate the tasks for software, scripts, installation, updates, etc. When the computer is turned on and has the agents installed on it, we detect the profile, and we install and run everything in a few minutes. This is another way to reduce the effort to keep our environment up to date and do automatic installations.

What is most valuable?

Asset management is most valuable. It is essential for all customers. The other features are also useful, but asset management is most important.

Everything is easy to use. KACE was created to be easy. It is very easy as compared to other solutions such as System Center, but it is important to have knowledge of some of the important concepts. For example, the knowledge of smart labels is critical. If you don't have knowledge of smart labels, you won't get its 100% benefit.

We use the Cloud MDM functionality. Its Windows and Mac enrollment capabilities for allowing IT admins to bypass manual device setup are fine. We provide management as a service to some customers, and they have Windows, Linux, and Mac. We also use it for our internal use in the company.

What needs improvement?

Its dashboard needs improvement. Currently, there is no way to modify the dashboard. There should be more flexibility so that we can create views according to our use case.

They can add some tips in the UI to help with the configuration. It will make the interface more user-friendly.

Its reporting also needs to be improved. Its reports are just textual, but we need a graphical report. We should be able to create dashboard views by using different types of graphics, such as pivot graphics. This functionality is currently missing.

We use the Cloud MDM functionality. Its interface is a little bit different from the SDA interface and the SMA interface. The concept related to the labels is also a little bit different. The SDA interface could be changed a little bit to have the same functionality as MDM. It is easier to create smart labels in MDM than in SDA. 

It can also be improved in terms of the consumption of resources or the size of the virtual machine. Currently, we are using a lot of memory and CPU power, and these can be reduced, but it is not a big deal.

For how long have I used the solution?

I have been using KACE for more than 10 years. I have so far handled 600 implementations of K1000 and K2000 in Brazil and Latin America. I have delivered training for more than 5,000 hours.

In 2010 or 2011, I was trained at KACE headquarters in the USA, and after that, I was in charge of supporting customers in Brazil. I helped them with project implementations, training, and quick starts. In 2016, I joined Dell, and I was in charge of all services related to KACE in Brazil and Latin America. In our company, we started using KACE four years ago.

What do I think about the stability of the solution?

It is very stable, but your infrastructure should meet the requirements for stability. To have stability, you need to meet all the requirements. You need static file systems. If you are using dynamic file systems on the Hyper-V or VM, you might have some issues with stability. You also need to take care of certain things related to the network.

If you have met all requirements and you have 100% compatibility as per the compatibility matrix, it is very stable. If you miss something, you can get into trouble. 

How are customer service and support?

We have their Premier Support because it is very important to have very fast support. I would rate them a nine out of 10. Sometimes, when you have a new hire or a new technician, they don't understand everything before denying some requests. They need to be more flexible.

How was the initial setup?

It is not complex. It is easy, but you need to have knowledge of various concepts, such as smart labels. It is important. Otherwise, it won't be so easy. To make it easier and more user-friendly, they can provide some tips in the UI during the configuration.

What was our ROI?

Its ease of use has helped in getting an ROI in a very short time. We sell KACE as a service, and we got our ROI within three months.   

What other advice do I have?

I would rate it a nine out of 10. It could be improved a little bit more. 

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
Quest KACE Systems Management Appliance (SMA)
October 2024
Learn what your peers think about Quest KACE Systems Management Appliance (SMA). Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,485 professionals have used our research since 2012.
Computer Support Specialist at Truckee Meadows Community College
Real User
I'm able to solve problems on-the-fly and push out the resolution across our campus
Pros and Cons
  • "The most valuable feature is the imaging of computers through the SDA... Being able to do that so quickly with the SDA, and to then use the SMA for reinstalling software, has been huge for our productivity."
  • "It took a little bit of time to figure out how to use the KACE Service Desk. I like the way that I'm able to customize it. But when it comes to how our techs are able to use it, it's not as functional as our current solution, which is BMC FootPrints Service Desk."

What is our primary use case?

Our main purpose is to image the computers we have on campus, using the Systems Deployment Appliance. After we get that set up, our second purpose is to use the Systems Management Appliance to keep an inventory of, and send scripts to, all the computers that we have on campus.

How has it helped my organization?

KACE has definitely significantly affected the time it takes to solve problems. In the past, we were spending way too much time solving minor issues, whereas with KACE we can do it on the fly. I'm solving problems quickly, in as little as 15 minutes, and then we're able to push out the resolution across campus. In the past, even if we had figured out something that quickly, it would still have taken us weeks at a time to push everything out.

As far as PCs go, and running Windows, the solution handles everything. I even have a Linux machine that I've imaged with KACE. I don't handle the Mac side of devices but I know there was a different solution that our Mac guy has used. It definitely makes it easier for us to keep inventory because, without it, our environment would be the Wild West. It would just be impossible to keep track of everything. The way I have it set up—and especially recently with COVID, we've had lots of people taking computers off-campus—I'm still able to keep everything together, even though we have computers all over the place. If we didn't have something like this, that would be an impossible task.

In terms of the amount of time KACE saves us, it's weeks of work on a monthly basis. We're able to do things in a day that used to take us about a month to do. It has also increased IT productivity because it takes less manpower to get the same amount of work done. Once a month, a classroom would go down, with some 25 computers in it. We would have to send a group of people out to take care of it. Now, we can do that work in a day, with one person. The other people who used to have to take care of that kind of issue can do other things that we need done.

What is most valuable?

The most valuable feature is the imaging of computers through the SDA. In the past, someone actually put images on CDs and walked around campus to image all the computers. We have around 3,000 computers on campus, and doing that with one disk, over and over, was very time-consuming. Being able to do that quickly is important because, on our academic side, we are re-imaging computers every summer, so that they have all the current updates. That means installing all the software on what amounts to about 1,500 computers. Being able to do that so quickly with the SDA, and to then use the SMA for reinstalling software, has been huge for our productivity.

It provides us with asset management, compliance, software asset management, mobile device management to an extent, and patch management. The combination of these abilities is extremely important. I'm able to download new patches pretty quickly and I send them out every week to all the computers on campus. That means we're constantly keeping everything up to date, and that helps, especially with the number of threats out there. Having everything up to date and being able to do it as quickly as we can is extremely important.

When I first started using the SDA, I used their default system image setup. But I do have a custom image that I created myself and, over time, I've been gradually going in that direction. It just took me some time to figure it out, but now that I have it figured out, it's super simple for me to set everything up the way I want it. It's been a great help to get everything set up that way for my environment. Obviously, everybody's environment is going to be different.

We also use the MDM functionality a little bit. We don't have any Android devices in our environment, but we do have a bunch of iPads that we were using the MDM for. It was easy to get those endpoints into the MDM for asset management. Originally, it was really easy to image them with KACE and then push all the software to those devices, even the iPads. But I think Apple is trying to push MDMs out of their environment. They want everything done the way they decide.

What needs improvement?

It's pretty easy to use. I didn't have too many issues in terms of setting everything up; that was pretty intuitive. From time to time there are hiccups with updates and I've had to contact their tech support. Something like that probably happens once a year. But overall, it's very easy to use.

Also, it took a little bit of time to figure out how to use the KACE Service Desk. I like the way that I'm able to customize it. But when it comes to how our techs are able to use it, it's not as functional as our current solution, which is BMC FootPrints Service Desk. I would like it to replace our current solution, and the only reason I haven't replaced it is that there's more functionality in our current solution.

For how long have I used the solution?

I have been using KACE Systems Management for about five years.

What do I think about the stability of the solution?

It seems pretty stable. I haven't really had any issues, except for one time, when I was building the KACE boot environment. They had to add a hot-fix to it but that happened once in the last five years.

What do I think about the scalability of the solution?

It's being used on every single computer that we have on campus, and we use it every single day, because we're always imaging or re-imaging computers. 

As of now, there is no plan to increase our use, but I would imagine that as things come back to normal, if we have more students coming to campus, we will add more computers and we will increase our use at that time.

How are customer service and support?

Their technical support has been good so far. If there's an emergency, something that we need fixed right away, they usually get back to us within an hour. They've been very helpful.

Which solution did I use previously and why did I switch?

We did not have a previous solution.

How was the initial setup?

The initial setup seemed complex at first. But as I spent more time with it, it was actually pretty easy to set it up. It is one of those things that, when you look at it, you realize there are so many things that you can do with it. It was a little overwhelming. But it didn't take that long to get the hang of everything and get into it. On a scale of one to 10, it was about a five as far as complexity goes.

It took a month or two to deploy. It took a little bit of time to get it set up the way that we wanted it. But now that we have it set up, it has been relatively easy to maintain that setup. The more I work with it, the easier it gets when I have to make a major change.

As for preparation ahead of setup, we just had to set up a server for it to be installed on. There wasn't much preparation.

I do most of the main maintenance on it and I have one other person who helps me from time to time. There isn't a lot of work there.

What about the implementation team?

We used a reseller to help with the deployment. I talked with them a little and didn't have any issues with them.

What's my experience with pricing, setup cost, and licensing?

Don't scale up too quickly, because there was a period of time where we bought a bunch of licenses but we weren't using that many. When we finally needed more licenses, we lucked into a time when they had a discount on licenses, so we bought more at that time. So hold off for those times when the cost comes down a little bit.

Which other solutions did I evaluate?

There were a few options out there that had some of the things we were looking for, such as the SDA and SMA, but KACE had more of what we were looking for. Some solutions had half of it and some others had the other half, but as far as having all of it goes, KACE was the best option.

What other advice do I have?

As far as the SDA goes, definitely look at the options for customizing your own images. I had problems with my images as far as the built-in system imaging went. But once I switched over to customizing my own images, I had fewer issues with imaging computers. And when it comes to the SMA, definitely take advantage of asset management and its scripting capabilities. They have significantly helped me and our organization.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
PeerSpot user
Works at University of Hawaii
Real User
Customizable service desk, easy management, and great for integrating existing IT tasks/requirements
Pros and Cons
  • "The service desk can be configured and customized to better serve our environment."
  • "There is always room for improvement. However, the system does most of what we need at this moment."

What is our primary use case?

The primary use of this product is for our user support (help desk).

Kace has helped us integrate all of our IT needs from inventory to imaging. Having this appliance to do everything automatically and push out software is a plus. Summer tasks are so much easier with imaging across the network that requires almost zero technicians intervention.

Managing 3,000+ computers across our campus from one single solution has made our life (and work) so easy. We are able to respond to the needs of our users always and can look into the history of the devices or the KB created to self-serve our users.

How has it helped my organization?

Our computer Inventory became more accurate, and computers were rolled out faster. Our techs adapted quickly to the new service desk, and the users can now check the status of their ticket by login into the user portal. 

As we plan computer rotations, having an accurate inventory is a key to identifying computers that are end-of-life or out of warranty. KACE can provide all of the necessary information by simply running customized reports that in turn can be provided to individuals or departments, either on-demand or on an automatic schedule.

What is most valuable?

Asset management, inventory, reporting, and service desk features work together and they are very valued in our daily operations.

When a user creates a ticket, users are in a continuous loop of communication via the service desk, user portal, or email. We are now able to set tier levels and involve other areas within IT, networking, sysadmin, VOIP, or managerial for approvals.

The service desk can be configured and customized to better serve our environment. If necessary, additional queues can be added.

What needs improvement?

There is always room for improvement. An example will be the implementation of granulated permission to run Scripts. We often find it unnecessary (and dangerous) that all technicians can see/run all the scripts created by our institution. Ideally, a Manager could assign some scripts to certain levels of support. 

However, the system does most of what we need at this moment.                                          

KACE has a website, "Use Your Voice," where users can make suggestions to improve the product or add new features. This offers a great way to improve the system.                      

KACE recently added Windows Feature Update patching to SMA. That was a considerable improvement to keep end-points secure, as many users were asking for it. 

For how long have I used the solution?

SMA was implemented in our institution in late 2008.

What do I think about the stability of the solution?

The stability is great, initially was running on a physical server, and recently migrated to a VM, both environments are very well-built.

How are customer service and support?

Support was always provided a fast and accurate response to our questions, issues, or even helping us implementing new system upgrades

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

n/a

How was the initial setup?

The setup was straight foward, and a dedicated support team was on the line while we implemented and set up the system. KACE included a follow-up online training to guide us and have the appliance up and running within the first hour.

What was our ROI?

We've seen ROI in less than 6 months.

Which other solutions did I evaluate?

We also looked into TrackIT.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Security Systems Integrator at a tech services company with 51-200 employees
Real User
We can use one image for several different instances, saving a lot of space
Pros and Cons
  • "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."
  • "They could make the booting solution easier for different things, e.g., easier to insert drivers. They could make it easier to create a new image and put it onto the server. Those would be some nice solutions. They could make it so that somebody who has no knowledge at all can do it. That would be really nice. Because every time, until I get it memorized, I still need to go back to the training, the manual, or Google it to figure it out again. If they would make it a lot easier, to where a nine-year-old could do it, that would be really cool. If they made it easier, I could have more people managing the images on the server, instead of just one or two people."

What is our primary use case?

The KACE K1000 is primarily used for patching or pushing out software that needs to be pushed out. The KACE K2000, the deployment server, is primarily used to image new and older computers.

I should be updating the image at least once a month. The reason why I am taking so long right now is because we didn't have access to it through our VPN, and I am mostly working from home. They just opened it up so I could work with it from home, which is great.

How has it helped my organization?

We keep on updating Quest KACE because we really use it. The patching is maintained by a different person, and he is constantly updating the software all the time. I should be doing the same thing too, and that's on me. However, I get busy with the email server, people calling in, etc. From now on, I am going to take time slots and mark myself up busy, just so I can do it. It's a lot easier working on it from home than when I'm at work, because people walk up on you and ask you to do stuff, then lose what you were just doing.

We always do the asset management first, then we image the computer. After it is imaged, it gets all the updates that it needs through the other KACE (the patch management). It makes life a lot easier. 

What is most valuable?

The most valuable is being able to use one image for several different instances. Because we only put one to three images on those instances, it saves a lot of space.

It pretty much provides a single pane of glass with everything we need for endpoint management of all devices. We have several different ways that we do stuff, e.g., for remoting in, we use Bomgar, and for asset management, we use ServiceNow.

What needs improvement?

They could make the booting solution easier for different things, e.g., easier to insert drivers. They could make it easier to create a new image and put it onto the server. Those would be some nice solutions. They could make it so that somebody who has no knowledge at all can do it. That would be really nice. Because every time, until I get it memorized, I still need to go back to the training, the manual, or Google it to figure it out again. If they would make it a lot easier, to where a nine-year-old could do it, that would be really cool. If they made it easier, I could have more people managing the images on the server, instead of just one or two people.

On the patching, the Systems Management appliance, I noticed whenever there is something new that the vendor has to do, he always has to call KACE for help with it. That could be made easier.

For how long have I used the solution?

We have been using Quest KACE for quite a few years, since 2014 or 2015.

What do I think about the stability of the solution?

I have never had to reboot it, except for when I have had to update the server. If it is having problems, and I have to troubleshoot, then I will need to reboot, but that is usually the image and has nothing to do with the server. The server is very stable. I have not once had to reboot because the server crashed.

What do I think about the scalability of the solution?

We have four people who have been trained on both servers: 

  • Two people are mostly working on the patching, KACE Systems Management. 
  • Two people, including me, are mostly working on the Systems Deployment Appliance.

There are 10 people in my group using the server to image. In another department, there are another two users who know how to manage the server, but they don't mess with the server networking. They only manage their image that they have on there. When I put in a fresh, new image, I inform them, saying, "Hey, I have this new image tested. You are more than welcome to start using it so I can start deleting older images."

If they would make it easier and more intuitive, then it would be easier to show other people how to do it. Right now, I have to send them to training, which costs us a lot of money.

How are customer service and technical support?

They have very good customer support and technical solutions. When I have a little issue, I call them and they fix it right away. I don't have to wait three or four weeks unless it is something out of their scope, then it takes longer. However, if it is in their scope, it gets fixed right away, for whatever I need. It is the same with the K1000. Whenever they need somebody, they have to call back that same day or the next day, depending on the urgency that we have placed on KACE.

Because I have so many different other jobs, I am still learning how to upload images, etc. I have to go over the classes, then listen how to do this and that. Instead of trying to call Quest every single time to do something, I try to just relearn it myself.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

The initial setup was very complex. It took hours of training. We found out at the beginning that we did it backwards. We were supposed to do the KACE Systems Management first, then do the Systems Deployment Appliance. We did it backwards because we didn't know about KACE Systems Management. That made it a little harder.

I would like it if they could make it easier, not a million steps to do one thing. Because once you have the image on there, it is tested, and it works, then it's great. All you have to do is update the rest of the software, but just getting the image onto the machine and making sure it works, that is the hardest part.

The initial deployment took about a week or so. We deployed it, then we had to learn it.

What about the implementation team?

I was the project manager on the deployment of the solution. I was involved in learning about it, getting a demo server going, purchasing it, and then deploying it once we purchased it. So, I have been involved from day one.

What was our ROI?

On a weekly basis, KACE saves us hours. On a monthly basis, it probably saves us a day or two. Because it is easier to use, patch, and manage than our previous solution, where I didn't even have the opportunity to be one of the people to manage it. Then, with KACE, we were able to switch it over to our service desk, divide KACE K1000 and KACE K2000, and cross-train, so we could have more people managing the servers.

Overall, the solution has increased our IT productivity as well as the other department's. Since they are using the solution, we bought them a license, which has increased their productivity immensely because they were doing everything from scratch with no imaging solution. They were just taking a brand new machine and setting it up, which just takes hours. Instead of the 45 minutes that it took to image a machine and run the patching and stuff (which may be another hour), which may take up to eight hours total to do a machine. Now, when you have all the software updated, it takes less time (45 minutes) because there is less patching to be done.

What's my experience with pricing, setup cost, and licensing?

We need it, so we have to pay the price. It is what it is. If you need a gallon of milk, then you have to pay the price for it. You don't want to buy the cheap stuff. You want to buy the stuff that is organic and good for your body, which doesn't have all this other junk in it. You want it clean for your body. Quest has done that for our deployment and management systems.

Which other solutions did I evaluate?

We did other vendors, but we didn't like them. The other solutions were too complicated and some didn't have good enough security for our system, since our security is super tight.

We first heard of a KACE when Dell EMC owned it. Then, we got more information on it. When the person who was going to do the project management couldn't do it anymore, I asked if I could be the project manager on it. I pushed it right through.

KACE promised us stuff and have kept their promise. Microsoft promises us stuff, but they don't keep their promises.

What other advice do I have?

It is a great service.

It is semi-easy to use once you have it in, but I always have to go over what I have already learned. Because after so long, if you're not doing it every day, you forget it. You have to keep relearning it.

My advice is to check it out. They are always willing to do a demo server, then you can check it out and work on it in a sandbox. 

For whoever gets trained, make sure they train somebody else along with them. They need to keep on top of it. Don't just let it sit there because it will break after a long time. The images get so old that they don't work anymore. You have to reimage it, etc. Just keep on top of it at least once a month and update everything. When a new software comes in, update that right away. You need the Management System, but install that first, then do the Systems Deployment Appliance. If somebody else is doing the Management System, keep in touch with them.

We have a system where every time there is a patch, then I get an email so I can know what patches to do, so I can update them on the deployment. Then, it doesn't have to wait for patches. That is the whole solution of doing it. You don't want to have to image something, then wait. If there is extra third-party software that you can't put on the server, then you could at least get that all installed and have it out the same day. With KACE, I have been able to image something and have it out to the customer the same day or next day, which is impressive when you are trying to serve out computers. People really are impressed when you just open a ticket and get it done.

I would give it a nine (out of 10) because it needs to be a little easier. It saves us so much time and the imaging part of it is really easy to use.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Sr. Systems Engineer at a university with 1,001-5,000 employees
Real User
Saves us significant time when patching hundreds of servers
Pros and Cons
  • "Patching is definitely the most valuable feature. It gives us good, centralized software, which comes in very handy since we are doing 400 servers at a time. It enables us to manage all the servers, and to deal with the application team regarding reboots and scheduling."
  • "One of the complications is that they don't have 24/7 support, and they're also not in our time zone... Sometimes, no matter how critical my application is, if my production server is down I won't be able to connect with anybody till 11:00 AM Eastern Standard Time."

What is our primary use case?

I usually use it for deploying patches, as well as for inventory, and sometimes even monitoring. KACE Systems Management is deployed through physical hardware. We have two of them. We use one for desktops and laptops, and we use the other for our servers.

We are part of a university, working under the president's office. We collaborate with all six campuses and have students from all six campuses interacting with us. To fulfill their requirements, we need tools for monitoring, patch management, and for inventory. KACE Systems Management is how we keep our customers and stakeholders happy.

How has it helped my organization?

The solution definitely saves us time. We try to do bulk patching, whereas before, we did manual patching. We used to have four people putting in 40 hours, and now we have one person doing it in 16 hours. That's quite a savings.

In addition, it has increased IT productivity. With one person responsible for installing patches, we have freed up the other three people to take more ownership of our applications. If I had to work on patching on a manual basis, that would be the only thing I'd be doing. But because this is all automated and scripted very well, I can use my time for other projects.

What is most valuable?

Patching is definitely the most valuable feature. It gives us good, centralized software, which comes in very handy since we are doing 400 servers at a time. It enables us to manage all the servers, and to deal with the application team regarding reboots and scheduling.

On a scale of one to 10, the ease of use of the solution is definitely a nine.

The solution provides us with compliance, software asset management, mobile device management, and patch management. This combination satisfies my needs, giving me almost everything I need on this box.

What needs improvement?

The things the solution is missing are antivirus software and monitoring software. The types of monitoring I'm referring to here are calculating data, making sure the machines are up and running, CPU monitoring, data monitoring, and SLAs.

Also, I don't think they have a good cloud solution yet. We wanted to go with a cloud-based application, but they were not ready yet. That's where everybody's going. Two or three years from now, when we have to renew the contract, if management asks for a better deal it will be embarrassing to say "Yeah, we have a product that's not in the cloud." We are taking a lot of our own machines to the cloud and creating our own cloud-based solution for our customers. I would like Quest to do the same thing for us.

For how long have I used the solution?

I've been using the KACE solution for close to 10 years.

What do I think about the stability of the solution?

The stability is pretty good, although it's not perfect. There are a lot of upgrades as they keep sending a lot of bug fixes. Any update or upgrade to a product that occurs more than once in a year is a lot. Quest releases two or three upgrades. So it becomes a little time-consuming, because we have to make other people aware of it and get change-control and everybody to sign off on them. Their upgrades come out quite often, a little more frequently than other applications.

We keep upgrading the solution. We keep up with Quest on their new solutions, every time they do an upgrade.

What do I think about the scalability of the solution?

We do patching every four months, so that's our key project. At those times, we are using it every day for 16 hours a day. But the inventory base and the little bit of monitoring that it supplies, as well as the software distribution, mean that we use it on an almost a daily basis, although not that heavily, during those times.

We have about 12 administrators of the solution, but the beneficiaries from it number about 600.

How are customer service and support?

I'm very impressed with their technical support. It's pretty good.

One thing that could be a little better is that, even though it's not 24/7 support, at least it should be available from nine to five in every time zone, or even better, from 7:00 AM to 7:00 PM in every time zone. I can understand not being able to reach somebody at 3:00 AM, but somebody should be able to call me at seven or 8:00 AM, because that's when business starts. Sometimes, no matter how critical my application is, if my production server is down I won't be able to connect with anybody till 11:00 AM Eastern Standard Time.

How would you rate customer service and support?

Positive

How was the initial setup?

I was not involved in the initial setup, but I don't think it would be that complex. I have done a lot of other setups with Quest and there are a few complications. It's not a cakewalk. The deployment took almost a week.

One of the complications is that they don't have 24/7 support, and they're also not in our time zone.

What's my experience with pricing, setup cost, and licensing?

I don't have to deal with the pricing and it does get renewed automatically for us every time. But the pricing does get confusing for me. Our system is a little complicated because we have two appliances, one dealing with just the laptops and desktops, one dealing with only the servers.

Which other solutions did I evaluate?

There was a stage where I had to evaluate other vendors. KACE had a better GUI. The front end is user-friendly, even though the back end is Linux-based. Their format and their design were much better and much more comfortable.

What other advice do I have?

I would definitely recommend using KACE. There are cons when it comes to the support and not being able to go to the cloud, and a couple of features missing, but I would definitely recommend them.

I like the solution. The things that we are using KACE for are working pretty well for us. I have had the opportunity to change vendors three times during this nine-year process, but I am comfortable with KACE. I'm not getting everything I want, but on a scale of 1 to 100, I'm getting at least 70 from KACE. So I keep signing with them.

The solution provides a single pane of glass with very close to everything I need for endpoint management of all devices. It meets my needs but for some applications we use other software, mostly for monitoring or pushing software development. But I'm happy with what I have from KACE.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Enterprise Service Desk Systems Manager at a manufacturing company with 5,001-10,000 employees
Real User
Easy to use, significant time saving with automated software deployment, good support
Pros and Cons
  • "We have our KACE agent deployed on all of our workstations and servers, and it provides us with reports on the hardware and software inventory for those."
  • "Scalability is my primary concern right now."

What is our primary use case?

We use most of the modules, although the Service Desk is one of the most important ones for us. We, as an IT department, handle a large volume of calls that includes different requests. We tried to make it accessible for all of the different teams within the IT department, not just the Service Desk, but networking servers, admins, and applications. We try to make it so that all of our IT requests come in from a central point, basically.

In addition to that, there are a number of other Service Desk queues or departments outside of IT. Those have been either initiated by us asking if someone needed some way of tracking their own work or issues, or they've come to us and asked for the same thing. 

The second feature that we use most often is device inventory. We have our KACE agent deployed on all of our workstations and servers, and it provides us with reports on the hardware and software inventory for those. The other half of that is that we take that data and report on it for things like accuracy, renewals, and replenishment.

We also rely very heavily on the patching module, which is part of the security module. This feature ensures that our workstations and servers are up-to-date with the latest patches.

I'm also using it for extensive software deployments. For example, a couple of years ago we went from one version of Microsoft Office in our environment to a completely different version, almost exclusively through KACE automated software deployment. This saved us thousands of PC touches.

Also within the domain of software distribution, we use file synchronization and scripting.

I work with two different entities. The first is KACE as a service, which is hosted, and the second one is hosted by my company in our Azure environment.

What is most valuable?

I feel that KACE is pretty easy to use, although that may be coming from the fact that I've been using it for so long. In the Service Desk, it's really easy to clean up a basic queue, and from there, you can get more granular and do a lot more customization if you need to.

For the inventory functionality, the agent requires no configuration except for pointing it to the server.

For software deployment, as long as you've got your installation commands, it pretty much runs on its own. This is the same with patching, where you set up a schedule and then just let it go.

We have seen a return on investment from its ease of use, firstly because the KACE appliance is managed almost entirely by me alone. This means that we don't need to have multiple people working on each individual component. With the reporting that we do, we've been able to find unused or underused software licenses, remove those from the computers, and apply them elsewhere. This meant savings because we didn't have to purchase additional licenses.

KACE was previously owned by Dell and because we have a hook into Dell's warranty database, we're able to use that information to learn about what's in our environment and see what we need to budget for replenishment. This includes replacing computers on a quarterly or yearly basis. That way, we're not just saying "I don't know, we'll throw X number of dollars at it". It's an actual and pretty accurate budget, instead of just estimating it.

It has also saved a lot of time because for example, when we did the Microsoft Office upgrade, our service desk team did not have to touch all of those computers. It just ran automatically. That would have been a very large time investment. We have had it in place for so long that it is difficult for me to estimate how much time it is saving us on a monthly or weekly basis. I have nothing to compare it against.

What needs improvement?

Scalability is my primary concern right now. The first environment that I had it in was about 1,700 devices and things worked pretty well. Now that I'm well over 10,000, even with plenty of resources allocated, I'm running into issues where things aren't working correctly. I'm having to work with support and the answer that I usually get is that we're trying to do too much with KACE. Essentially, I'm overloading it with tasks to perform and as a result, I'm having to split stuff up a lot more into multiple jobs instead of one job. There's no built-in load balancing, I can't have multiple servers, and limitations like that.

For how long have I used the solution?

I have been running Quest KACE Systems Management in production for seven years, since late 2014.

What do I think about the scalability of the solution?

We have KACE deployed on more than 9,000 workstations and approximately 1,300 servers. Scalability is an issue for us at the moment, and I don't know how much our company is going to grow in the future. One of the ways that we grow is through acquisitions. For example, we just acquired a little company that was about 20 people and acquired another one with about six people.

I don't know what's coming down the pipe. I am not sure if there's a company that's about a thousand people, how is that going to affect how I use KACE. I wonder if I'm going to have to scale things back, such as running a script once every other week instead of once a week, or stretching out my patching windows.

How are customer service and technical support?

I'd rate the customer support pretty high. I use them pretty frequently and I have been satisfied with the majority of their answers. I have never been brushed off by them saying, "Oh yeah, it's just this, you've got to do that."

Quest has a Professional Services offering, which is their consulting service. You can use their professional services to have them come out and help you set up your clients, or work with you to do so. Or, if you need a report written that isn't supplied by default and you can write it by yourself, you can contract them to write it for you. We have not used professional services.

The Premium Support that we have gives us access to a technical account manager. It includes monthly touch meetings to ensure that everything is going smoothly. For example, they ask if we need anything else and whether they can help move things along, such as reviewing any open issues that we have.

The biggest value from premier support is the ability to get past the technical support. I don't mean that they're not providing good support but with Premier, I've been able to talk with our technical account manager about more advanced topics. I would consider myself a power user and I do a lot of stuff that's outside the norm. This is not the sort of stuff that you would just set it up and forget about.

I also get information about a lot of different reporting and things like that. Sometimes, I'm interested in the very minute details of how it works, in order to either do the report or ensure that I'm doing something in the correct fashion. With the help of the technical account manager, I have been able to be interactive as an intermediate, or I've actually been able to get on, or have a call with, some of the developers who may have been the ones specifically programming a certain portion of the appliance. I don't see getting those deep answers from somebody further back behind the technical support customer service.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

It wasn't really difficult to set up. When we set ours up initially, there was an option to have somebody from the technical support or training department go over it with you. Once you started setting it up, they would ensure that you understand how to work it.

I can't recall exactly how long it took for the overall deployment, although I don't believe it was a lengthy process. The two biggest parts of the setup were configuring the initial queue for IT, and getting the agents pushed out.

What about the implementation team?

We completed the deployment on our own and I am responsible for performing the updates.

What's my experience with pricing, setup cost, and licensing?

Licensing is done on a per device basis, so it's dependent on how many agents you've got installed. When we looked at it, KACE was competitively priced versus other agent-based asset and inventory management solutions.

Where we really get a lot of value is that the product licensing is only based on that. It means that if we implement another IT service, we can use it with no problem and it doesn't cost anything more to put that in there. We can just keep adding to it, so we're basically getting more use for no extra costs. An example is that we have other departments and other kinds of entities within our business, and they are utilizing the service desk functionality for things outside of plain IT support.

Which other solutions did I evaluate?

Early on in the pilot, we evaluated other options. It was around the time that we implemented KACE that we also played with a solution called Spiceworks for system support.

They have a ticketing system, and we tried to make it work, but being about the time that we started looking at KACE, and since KACE had the functionality of a service desk, we didn't really pursue that any further.

What other advice do I have?

I know that Quest has other products, whether they're KACE branded or other brands, but, by and large, those offerings are for systems or services that we already have in place with other vendors.

My advice for anybody who is implementing KACE is not to be afraid to use their technical support. There is also some semi-official support available in external groups. They run a website called ITNinja, and there's a lot of discussion on there from KACE users, about questions that they have, or issues that they have, or wants or reports.

People help out each other. The site is run by Quest, but it is community moderated rather than Quest doing the moderation of the content. Essentially, it's a virtual user group and it has been a big help.

In summary, this is a very good product but there is always room to improve. For what we've used it for, it's been very good, and I hope that it continues to serve us well.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Ken Galvin - PeerSpot reviewer
Ken GalvinSr. Product Manager | Project Manager at Quest Software
Vendor

Thank you for taking the time to provide feedback on our product. Our next release will have some great additions, including significant scalability improvements that will be of interest to you. We would like to invite you to join our beta program so that you can see these sooner than later. If you are interested, please contact: KACE_BETA@quest.com

Scott Tweed - PeerSpot reviewer
Windows Engineer at a tech services company with 5,001-10,000 employees
Real User
Low maintenance, reliable, and easy to create packages
Pros and Cons
  • "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 labeling process should be more streamlined. It should be easier to do. It gets confusing at times."

What is our primary use case?

We use Quest KACE Systems Management for things like deploying software packages, inventorying, and versioning what we currently have.

For me, specifically, the use case is for package deployment. When I need to push out a new package. We use a new 8x8 client, or I have Chrome set to update, and if it doesn't, we'll post it here. We use this solution to push packages because we don't have an SCCM solution or anything similar that I am more familiar with.

SCCM is a Microsoft solution, which is now known as MECM.

How has it helped my organization?

Right now, it's just a stopgap until we can set up and configure a proper environment. This product was acquired and brought over from an acquisition. As a result, there is some net overlapping and other issues that prevent it from being fully integrated everywhere, and there is a problem with firewall separation. 

It helps in some ways, and for the most part, it makes my life easier. It doesn't seem to hit everywhere.

What is most valuable?

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.

What needs improvement?

With KACE, you have to use smart labels and groups, and it can be annoying. It's aggravating if you don't know what you're doing because you have to figure out how to do it.

In terms of improvement, I would recommend the labeling process, also known as label management. With  SCCM, you have collections, here they do Label management.

The labeling process should be more streamlined. It should be easier to do. It gets confusing at times.

The only issue I have is with label creation.

For how long have I used the solution?

I have been using Quest KACE Systems Management for nine months.

We are not working with the latest version. I don't see a way of determining the version, but It wouldn't be the most recent because even the application catalog is out of date, and the company decided not to purchase a new software catalog.

I believe that it is hybrid because I'm aware of a machine that checks in but isn't in our environment. It's a machine that was given to an employee and was never re-imaged. I'm aware that the client logs in from time to time. They have to re-image it to remove the agent, and then it will stop popping in. As a result, it's a hybrid.

I'm not very familiar with it. I was never taught how to do it. 

Everything I learned from experimenting with it for tasks that were assigned to me. There was no training.

What do I think about the stability of the solution?

I believe that once the agent is installed on a machine, it is very reliable. It easily tells you when it last logged in. You don't have to search for it. Aside from the labels, I believe it would be a great tool to use if properly configured with proper access everywhere.

What do I think about the scalability of the solution?

We have approximately 800 employees with 67 to 71 data centers.

We don't have a lot of machines in there for scalability. We only have about 300 or 400 people out of a total of 12 or 13. I can't respond to that. 

We had 7,000 employees in the last environment I worked in, and SCCM handled it all with the 300 or 400 domain controllers we had. I can't comment on this because we don't have a large enough environment.

We have 200 or 300 users in our organization.

It is not being extensively used because it is only hitting approximately 30% of the machines. Because this is pushing toward workstations. 

I don't believe that we have plans to increase our usage. That's why we started looking for a third party. I don't think they're heading for KACE. I believe they're discussing BigFix right now, but that's a different department, and we could be drawn into that.

How are customer service and support?

I have never had to contact technical support.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

I was not involved with the initial setup. I came to it in the state that it's in.

I am responsible for the maintenance of this solution. It does not require a lot of maintenance. It is truly low-maintenance. However, we do not send patches via KACE. We use WSUS to distribute patches. If there isn't anything for me to do in KACE, there isn't anything for me to do. If there isn't a new package coming out, maintenance is minimal, and the agent is pushed using a GPO, leaving nothing to do until we deploy agents, which is handled by the GPO.

Which other solutions did I evaluate?

I was only looking for something to patch our internal workstations and servers, not anything for customers.

What other advice do I have?

I would suggest taking a training course. Take a training course on its fundamental administration. That would've been nice because it would've probably helped me with label creation and other things like that. Even though the KBE isn't too bad, you'll need to figure out who has the account in order to log into their knowledge base.

I would give it an eight out of ten, but I haven't seen everything it's capable of. And the reason I say that is because I have 10 years of SCCM experience. I love SCCM, this isn't as bad, but I can't really compare this to that. 

I really like what I am seeing, I would rate Quest KACE Systems Management an eight out of ten. I can't rate it any higher than that.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Quest KACE Systems Management Appliance (SMA) Report and get advice and tips from experienced pros sharing their opinions.
Updated: October 2024
Buyer's Guide
Download our free Quest KACE Systems Management Appliance (SMA) Report and get advice and tips from experienced pros sharing their opinions.