CA Unicenter Network and Systems Management (Discontinued) vs. Kaseya VSA

It's a decent system if you're a pure IT shop and want to become ITIL-aligned. It forces everyone into an ITIL mentality - service level agreements, change management, and asset tracking. It's very rote, for better and for worse. It's not appropriate at all as a customer-facing or non-IT facing self-service tool. You will never get your end users to really understand how to use the interface.

Incentivized

This package is well suited for businesses of any size that needs a method of connecting to systems on or off the network. This is one of the few packages that doesn't require the end user to provide permission before allowing the techs to connect which is what my agency needed as we have a majority of our systems are used by "general public" that walk in our doors and if they are doing something that they are not supposed to it would be unlikely that they would grant permission for us to access the systems.

Incentivized

• ITIL ticketing (incidents, problems, etc.).
• Change orders.
• Matching up its asset management system with incidents/change orders.

Incentivized

• Scripting - Very powerful scripting engine that allows us to update/install applications and maintain PC's and Servers.
• Policy Management - Globally configured policies allowing us to make changes to thousands of PC's quickly.
• Monitoring - Monitoring engine allows us to Proactively respond to alerts quickly minimizing downtime significantly.
• Patch Management - This module requires minimal effort to manage and maintain.

Incentivized

• The user interface (UX) is antiquated and clunky. Compared to ServiceNow, it feels like it's 15 years behind.
• It's complicated - We do routine internal training just to get people to use it correctly.
• It doesn't have an automated way of discovering assets. Everything has to be force-fed.

Incentivized

• The only area I can see where a lot of room for improvement can be made is in scripting of Agent procedures. Making operations more modular and able to be assembled by technicians who might not be strong in a scripting environment would be helpful. In the mean time, Kaseya has an entire site and a whole team of developers who write Agent procedures for common tasks and make them available for free to all Kaseya VSA customers.

Incentivized

Excellent product with easy learning curve

Incentivized

I think this is a solid tool for enterprise IT, however it would be higher if Kaseya VSA addresses the areas raised around recent stability, their support team, multiple session & screen support etc. It does do it's main job and allows an easy way for IT to operate and is mostly fine.

Incentivized

We have to hire 2 full-time 3rd-party consultants to run this application. That tells me it's not a very IT-friendly, vendor-supported application. Compare that with, say, SolarWinds, which is much easier for regular IT staff to customize without sacrificing features and capability. Sure, we have to bring in Loop1 to consult for us when we need to do a major SolarWinds config change or need a really unusual custom query built, but we never need more than 10 hours of consulting per month.

Incentivized

It was lots of back and forth email communication whenever I tried to solve my connection issues. I would send them detailed logs of the date, time, computer, and more of when I was experiencing connection issues. All I would get is an email back a few days later saying that they didn't find an issue in the service

Incentivized

I did not select CA. If it were up to me, I would migrate us to ServiceNow. The user interface on ServiceNow is 100% more modern and 200% more user friendly. With ServiceNow, the front page for end users makes it clear: one button that says "Ask for something" and one button that says "Report a problem". That's what our end users need. The biggest problem we have in our organization is that our end users don't report issues to the Help Desk often enough and rarely ask for things through the Help Desk. A clean, simple self-service option like this would open up a world of new information for our customer service team.

Incentivized

We moved away from NinjaRMM for support of PowerShell scripting and APIs. Overall, the experience with NinjaRMM, though limited in features, was tenfold better than our experience with VSA. We have been desiring strongly to move away from VSA to N-Central (having been provided a full demo that we installed on our cloud infrastructure) but have been unable to do so due to Kaseya's draconian contract policies. It's important to note that NinjaRMM was allowing us to go month-to-month and switching to Kaseya VSA was one of the worst business decisions I ever made. It's equally important to note that, if you are considering Kaseya VSA, you will be locked into a 3-year contract that is nearly impossible to escape from once the documents are signed. SolarWinds N-central only requires a 1-year contract and then has month-to-month billing available. I can provide no good reason for anyone to consider Kaseya VSA when there are dozens of better systems out there to choose from.

• It helped make us an ITIL shop.
• It was integral during our large IT consolidation 10 years ago in merging 10 different IT departments into one by converging on one ticketing system for all IT issues.
• Its lack of user-friendliness has gated us from being able to deploy a true self-service IT help desk.

Incentivized

• It has increased the efficiency of operational tasks for our technicians
• It has change the speed at which we are able to deploy updates and software patches
• It caused us to spend additional money on more security tools due to concern from breaches

Incentivized