Quest now offers the KACE Systems Management Appliance (SMA) as an IT Asset tracking and management appliance (also available as a virtual deployment if hardware requirements are met). Beyond discovery, inventory tracking and license management, KACE emphasizes automating software upgrade distribution with minimal end-user disruption, featuring remote replication for multi-site upgrades and rollouts. KACE SMA may be bundled with KACE Cloud Mobile Device Management (MDM) to form a complete UEM…
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
ServiceNow is BY FAR the best I've used. KACE and Remedy are hard to use and in my experience, don't meet user needs. ServiceNow lets you customize to such a granular level that it's hard to miss anything. Truly the best.
I think it has added value for any organization. It reduced our Tech Support cost by: -Supporting users anywhere -Reducing users downtime as well keep them informed with the status of their tickets -Managing software and hardware actively -Processing automation -deploy mass software installs, patching or updates - Provide approved software's to users to install without IT help
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Inventory: KACE provides a ton of hardware and software inventory information that is easy to search, filter, and export. This is critical when we need to find the answers to questions about how many of such and such we have in our fleet.
Patch Management: We were using WSUS before and it was altogether too cumbersome. KACE has given us the power, flexibility, and verification we need to feel comfortable our patches are up-to-date.
Service Queue: We made KACE our help desk system and it does everything we need it to do. Great improvement over our old system.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
The KACE SMA needs a better way to handle different roles in the software so certain users can access or administrate certain parts of the software, but not the entire software installation.
The KACE SMA could improve the ticketing process of projects. The aspects of the title and some information do not always flow down from the parent ticket to its child tickets.
The KACE SMA could improve the UI of the software with the addition of different CSS color schemes.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
Overall, the software is simple to understand and use. That said, most vendors have been slowly updating their user interfaces to HTML5 so that they have a clean updated look and feel. This is where KACE falls short in that the UI is great for a packaged software 10 years ago. This isn't a major limitation as the software is really meant primarily for technology users.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
KACE does exactly what you need it to do, it maintains your computer environment. You can set patch schedules, inventory computers, setup software catalogs; basically everything you need to ensure the computers on your network are being actively managed. This is all with little need for constant configuration or updating the setup.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
We have selected this software because it rolls several different systems into one. We have a helpdesk system with this and an asset and inventory management system as well. We pay one price for the whole system instead of paying multiple companies different amounts that would have totaled more than we pay for the single system.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
