What needs improvement with Quest KACE Systems Management?

The user interface needs improvement as customers have mentioned they do not like the interface since it is not an SMA-based interface and lacks a manual configuration option.

Easier integration would be beneficial.

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 think KACE could be designed a little bit more intuitively in terms of administration. Their knowledge-based articles are very good. But one of the things Microsoft does well is that they bake in a lot of the instructions and make the UI design a little bit more intuitive. So if you're flowing through something, the need to go back to the manual with Microsoft and it is not as heavy as it is with KACE. It is not necessarily always a good thing, but I would say KACE feels like an old-school piece of software. You need to make sure you've got the manual open while you're utilizing it. Now I am trying to get the right size solution for my small businesses.

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!

Sometimes the information is not as real time as it's supposed to be. In that scenario, they have to work with Microsoft and figure it out, because I think that's the challenge that we always come across. The information we get isn't always 100% accurate. There could be a dynamic environment where you can select what products you're using, whether it's Dell or IBM or HPE, and it creates its own repository. When there's not much internet usage, it downloads those critical patches or firmware updates so you can push it. I think that kind of thing will make it much better, because I think Microsoft products are only geared toward Microsoft. I think because KACE is not a Dell product anymore, it can work as a vendor independent or vendor agnostic approach where you can select which products that you are using, which models that you are using, and based on that, it can tell you there is an update or firmware upgrade that's available for this particular product or this particular model. If I forget to research what's available on the internet and the latest firmware upgrade, the tool itself could go every night and fetch whatever is the important update or upgrades that is available, download it, and tell the admin, "In your environment, these are the things that you can upgrade." Some of the work can be automated.

The solution needs to add: * Automated software deployment, rather than manually having to create uninstall packages and running this against a number of manually entered devices. * Driver feeds for devices outside of Dell ownership. * The ability to push out managed feature updates from Microsoft in a more seamless way. * The ability to integrate quickly with workstations to push out tests/patches. There is a Resolve issue whereby some workstations no longer report/check-in after a recent update. This is now an open case with Quest Support. There is a Resolve issue whereby we cannot migrate between VMware hosts.

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.

The customization of the interface needs improvement for things like end user tickets. While the functionality is good, some of that UI stuff does need improvement. Though, I don't receive a lot of complaints about it. Some of the reporting could be a little more intuitive. This is something that could be worked on. You really need to take the training. There is a learning curve when using it because it is just different from other things. There are some newer things coming out where it won't cover quite as much with some of the Microsoft Azure stuff.

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 complaints about smart label adaptation and because of this, I recommend a 24 to 48 hour bake-in period. I'm not a big fan of the bake-in period, but that's going to happen because we have a two-hour report time. We've got 1,626 PCs, which means that it's just going to take time no matter what. If there is a machine that doesn't report, then it never receives that smart label. In this case, we have what I call hanging chad, but with 1,626 machines, if we can catch 1600 of them, that's only degradation of 26. That's not bad compared to sometimes in other programs, where they don't conform at all or don't report at all. I'm not sure what could be done to resolve this. I know that I can tell the system to report more often, but the agent reporting time of two hours is perfect because we won't have a lot of machines bogging down our infrastructure. We're running what's considered a modified MPLS and if you think about it that way, having 26 hanging chads is not terrible. The reality is that I think it's working as well as it can, given our current infrastructure.

The fact that there is so much that can be customized with K1000 is great, however, some lack real-world higher-level customization without having to get other(s) (professional services) involved (and the extra costs in general) would be ideal. Paying for the product should come with full and extended training anytime it is needed. I am not sure if our organization is just ahead of the pack on what we demand and or how we want to utilize the K1000, however, even if it takes a little bit of time, so far, we have always been able to figure out what we need and make it happen with the K1000.

What could be improved is the possibility to use replicas in a secure way outside our network in order to maintain the machines that never connect to our corporate network. The helpdesk could also improve, although it has evolved a lot on the last versions. It does not meet the moment for our needs. What could be interesting when deploying larger software or software to many machines on a remote site would be to be able to do it P2P in order to accelerate the local deployment and not to load too much of the inter-site links.

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.

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.

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.

KACE.uservoice.com is a platform where users can post suggestions for improving the software. A lot of ideas that have ended up in the development of KACE have come from this. For example, in version 10.2 KACE implemented the possibility of reducing the network speed of the KACE agent. You can set it so that it takes whatever network speed you want or you can set it to 5 Mb, to save network speed. You set it for all the computers, but it would be preferable to separate between VPN connections in our home office and the local area. It would be great to be able to set separate speeds for different VLANs. I posted this idea on Uservoice.

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.

The only pain point I have is with their salespeople. They call too often. They're too aggressive in trying to upsell. We know what we need, and we know if we want to expand. I don't mind quarterly calls from them, but sometimes, it is weekly. They need to get their sales team under control. The main goal of their support people and professional services is to make sure they deliver the service, and they deliver it well, whereas their salespeople are so interested in making a sale that they're wasting my time. We did look at MDM, and I was misguided by their salespeople. When I talked to their tactical people, I found out that I hadn't been given the full picture on MDM, and it wouldn't have been what we wanted if we had moved forward with it. I really value their technical services, their professional services, and their support services, but their sales team needs to really up their game and not phone every week.

I still need better communication about which processes are really due and which processes are currently being processed. According to the initial setup service provider, there is still no real management or overview on KACE where you can really see 100 percent of what is going on as well as what is going to be processed next and whether I can influence the overall process. It could really help me if I knew, e.g. exactly in 10 minutes my colleague will be supplied with this or that software. I haven't found this yet. If they could add this, that would be cool. It is still missing and I haven't yet found something like this. Sometimes, if you copy and paste someone incorrectly, then you can also assign the wrong software and that can then lead to problems where you distribute the wrong software.

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.

It is a little bit difficult to use the license compliances because you need to decide when you are using the software catalog if you are using it with their license compliance or the normal software part. Under the inventory, you can use software as a menu link or software catalog. Most of my specialist software is not in the software catalog. When I try to import them, in my license compliances overview, there are cryptic names for this software that I have to import. That is not very good for the reports that I use. When I take them to my bosses, they see cryptic names of software that they don't understand. It would be much better for me if I could use software and the software catalog as well for the license compliances. If it could be possible to use GUI to create reports, where I could drag and drop like in Microsoft Access where you can create reports, e.g., when you take columns from tables from the drag and drop menu, then you can slide it down in another area and sort columns or create new columns. This would be nice to see in the graphical user interface as well as be much more developed for the reporting part than it is at the moment.

For the basic functions, it is very easy to use, e.g., looking up computers and seeing what is on them. For the software deployment and scripting, it is more difficult. I only have experienced people on my team do that type of work. If there was a way to simplify the interface for more technical tasks, that would be more useful. We had a system that we had to upgrade manually this past week. It was a good portion of the systems. Unfortunately, due to the type of software it was, I couldn't do it with KACE, even though we tried. So, my folks had to manually touch each one of the computers, and it cost us hours in lost productivity. The correlation between assets and inventory needs improvement. The KACE appliance does both asset tracking and inventory, and the link between those two is very sparse and difficult to operate. So, I asked them if they could link those two more seamlessly. I gave that information to KACE a couple of years ago.

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.

I would sure like them to be able to copy and paste out of OneNote. That drives me nuts. You can't copy from OneNote into KACE. I've brought that up many times. We've just had a major upgrade and I haven't had a chance to dig into things too much, as far as the improvements and the latest upgrades. So I can't really speak to what else might be missing. There is a great resource for improvements that people would like to see, because Quest hosts a forum in IT Ninja where you can vote for features you'd like. When a lot of people vote on something, they roll it into their next update. There are so many good suggestions about things to add. One that I see right now is a Microsoft Outlook plug-in. There's always room for improvement, but the product that they have right now is so great, already, as it is.

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.

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 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 biggest problem we had with Quest KACE, with the K2000, imaging becomes a problem when you start to try to go beyond doing more than thirty or forty machines at a time. We initially tried to do that virtually and it just, it wouldn't work. But that one physical appliance was enough to get us through and once we got the one K2000 physical appliance that was plenty to handle imaging whatever we needed. As far as the K1000, our original purchase was underpowered. We really didn't have the box we should have had for over three thousand nodes, but when it came time to upgrade that box, we got a box that was much more in tune to having over three thousand nodes on that system and it's been doing fantastic for almost three years now. We haven't had any problems.