We changed our name from IT Central Station: Here's why

Kaseya VSA OverviewUNIXBusinessApplication

Kaseya VSA is #3 ranked solution in top Remote Monitoring and Management Software and #7 ranked solution in top Patch Management tools. PeerSpot users give Kaseya VSA an average rating of 8 out of 10. Kaseya VSA is most commonly compared to Microsoft Endpoint Configuration Manager: Kaseya VSA vs Microsoft Endpoint Configuration Manager. The top industry researching this solution are professionals from a computer software company, accounting for 27% of all views.
What is Kaseya VSA?

Kaseya is a provider of complete IT management solutions for Managed Service Providers and small to midsized businesses. Kaseya allows organizations to efficiently manage and secure IT in order to drive IT service and business success. Offered as both an industry-leading cloud solution and on-premise software, Kaseya solutions empower businesses to command all of IT centrally, manage remote and distributed environments with ease, and automate across IT management functions. Kaseya solutions currently manage over 10 million endpoints worldwide and are in use by customers in a wide variety of industries, including retail, manufacturing, healthcare, education, government, media, technology, finance, and more. Kaseya, headquartered in Dublin, Ireland is privately held with a presence in over 20 countries.

Kaseya VSA Buyer's Guide

Download the Kaseya VSA Buyer's Guide including reviews and more. Updated: January 2022

Kaseya VSA Customers

Sage UK, MSP, CodeBlue Ltd, Connect Work Place Solutions, All Covered, 501cTech, Chairo Christian School, Green Duck

Kaseya VSA Video

Kaseya VSA Pricing Advice

What users are saying about Kaseya VSA pricing:
  • "With the on-prem, you buy the agent license. That's a one-time fee, and it varies depending on how many you have. You also pay annual maintenance on the number that you have. So, there are two fees involved: a one-time fee and a recurring fee."
  • "It is not expensive. Anyone can afford it. Most of the time, we get a discount for licenses. We had about 5,000 agents, and we received a discount on the price. There is only the licensing cost. If you use the on-prem version, you also have the infrastructure cost."
  • "The pricing is quite good and we are satisfied with it."
  • "It depends on what products you want. Kaseya loves packages, and if you are packaging, it is more affordable. If you're not packaging, it tends to be a little bit more expensive than others."
  • "I think it costs more than ManageEngine."
  • Kaseya VSA Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Team Lead at a tech services company with 51-200 employees
    Real User
    Easy to use with great remote access and patching capabilities
    Pros and Cons
    • "The ease of access and ease of use was great."
    • "The deployment process could be better."

    What is our primary use case?

    We would install Kaseya on customers' computers and provide tech support. We used it as a monitoring tool and remote access tool.

    The main uses were for information gathering, management, software, and patching as well. My team would not be responsible for patching. That was another team that was at the engineering level. My team was responsible for going on the customer's computer and providing just regular tech support. That was done via Kaseya quite often.

    How has it helped my organization?

    The product has allowed the company to provide faster service. If you're, for example, using something like TeamViewer, which is a different type of software, versus Kaseya, if it's deployed on the computer, it will be very fast and easy to do the same things with Kaseya compared to TeamViewer. That means there is higher customer satisfaction. When we do our jobs faster and more efficiently, the customer is happier.

    What is most valuable?

    The ease of access and ease of use was great. When Kaseya is deployed on the customer's computer, we have access to the customer. We just need the computer's name or ID, or sometimes, if the user has the same name as their first name, we can find them that way. 

    I know it's customizable. Even with the customization we had, which was not that great, I, myself found multiple ways of how we could find people, based on system version, their computer specs, location, et cetera. That made finding people very easy. 

    The functionalities were helpful. I could check what type of computer the customer was using and if they had a warranty. It provided a lot of information out of the box and just pulled all the information from the computer itself. For tech support work that is very valuable. You don't have to go to the client and say "Can you find me a serial number somewhere on the computer" and have them messing around, looking for it. Instead, I just pull it from the system, as Kaseya finds it automatically.

    There is automation that was used for a big product, however, you need to learn it. One of the people in the company actually finished the course. When I saw what he could do with it, it's way more than what I could do. You just need to learn it.

    What needs improvement?

    The deployment process could be better. There were some issues sometimes that were kind of random. For example, by sending a link to a customer, you would need to add the link manually, which is a bit strange, as it is customizable. You need to know which part of the link you need to edit and how you need to edit it. I don't know how much of this is Kaseya VSA itself and how much of it is our custom setup. Maybe Kaseya would say "No guys, you just did it wrong. That's not how you do it." However, based on what I saw, editing the link was a bit odd and I would prefer something more on the lines of just sending their general link and maybe an easier deployment. 

    There was some lag. For example, even if it's installed, it's not showing up and you need to wait for it to show up. 

    Sometimes there were connection issues. It was not exactly clear why it didn't connect even if the customer had internet that was working fine. I'd do a speed test, and it would show normal speeds. We would have our fast office internet and everything was working fine, yet it wasn't connecting right and we don't know why. We used it on literally thousands of machines and servers as well and it just would randomly happen. 

    It doesn't doesn't scale on smaller monitors properly. For example, if we moved from 17-inch screen laptops to 12-inch screens, it would not scale properly. There is a part that's called Live Connect, however, it wasn't actually a live connection. You connect to the customer's computer in the background and you have this user interface and the smaller monitors would look really bad. With some of the screens, you couldn't click a button or anything like that. While it was working fine on a normal big monitor, on smaller ones, it did not adjust which made things difficult. I don't know why, how they missed that. Maybe we used some kind of older version or something.

    Kaseya is not really friendly with Mac OS. The deployment is even harder than deploying on Windows. You need to have a custom download. If a company runs a customer service desk and has a bunch of tier-one agents, they're not going to be able to do that. Right. They're going to be able to edit a link if you provide instructions, and that's about it.

    For how long have I used the solution?

    I worked with the solution at my previous organization for about a year. I used it up until a month ago.

    What do I think about the stability of the solution?

    We sometimes had connectivity issues and I never spoke with a Kaseya representative that could explain that. We worked from Europe; the servers were probably in the US and the customers were in the US. Sometimes it would work quickly and then snappy and everything would be great. Other times it would be kind of slowish. I would say it would be way faster or way slower than a TeamViewer connection. 

    What do I think about the scalability of the solution?

    The solution is scalable. We had thousands of users.

    We didn't have issues with scaling. When it was set up, it was designed so that, if a business joins, we join them on the server and they have their own ID there. We could install it on the computers. It connects that computer to the whole system. While it's hard for me to answer about scalability in a detailed way (I didn't work on that infrastructure part), my understanding was that it was decent at worst. It was pretty okay.

    We used it daily. It was a core product for the servers. However, we were hacked, and for a few weeks, it was quite bad. 

    How are customer service and support?

    We had the in-house staff. I can't really say anything about technical support as the person we dealt with was just an expert that was hired by the company, working for the company, doing some other stuff as well. 

    We didn't really need to contact directly with Kaseya. When the hack happened, they were communicating well with us. Based on the opinions of that other person, that had finished the course with them, he was very happy about that and thought support was super professional. 

    How was the initial setup?

    In terms of deployment, technically one person is enough. For Macs, you just need to know how to do it and it's a very specific procedure. As far as I remember for each company, there is a separate download. With Windows, it's the same download, however, it needs to put the users in a specific catalog. You need to edit the link, essentially the same way you would for a website and you need to put specific lines in the link. For Macs, you have a different file that you need to know how to download, where to download it from and how to check if something is wrong. While one person is always enough in terms of handling the deployment, that person needs to know how to do it.

    Deployment times vary from a few minutes to half an hour. Maybe a few hours. It depends. Most of the time I would say it's only a couple of minutes. However, when you really need to have it configured and you are first building the infrastructure, the whole thing, if you order a product and you want to start using it, I have no idea how long that process takes. That's definitely going to take longer. 

    We had five Kaseya Servers for thousands of computers, thousands of servers, et cetera. That would take a while. Right. If it's just a business of maybe 40 users, I would assume it is a way quicker process. 

    Kaseya itself would update regularly and then it usually would show up with a message such as "You have a patch to do. You need to install this patch." That's about it, in terms of maintenance. I'm not an engineer. I was more of a user. From a team lead side, I was managing people that used it daily to help customers. While there was definitely some normal updating in terms of handling the security patches, that was the only real maintenance task. 

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

    I can't speak to pricing. I was not involved at the decision-making level. 

    What other advice do I have?

    My company was a customer of Kaseya.

    I'd rate the solution at an eight out of ten. 

    Kaseya is more beneficial if you really have all of these machines and you need to manage your servers, you need to set up automatic patching for scripts to run or something like that. 

    Whether it would work for others depends on the business. For some, I would assume it's not going to be worth the price. If you just need a remote connection, you can just go to TeamViewer or something similar. If you need automatic patching, you want to have this access, instant access, background access to the user's computers, so that you can check what's happening, basically without the user knowing, it's very, very good for that. At the end of the day, it depends on the scale of the business and business needs.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Automation Team Lead at a tech services company with 201-500 employees
    MSP
    The most helpful solution for MSPs for supporting end-users and addressing environmental problems, but it needs better updates, patch management, and Mac support
    Pros and Cons
    • "The most valuable piece of the puzzle for me is what they call Live Connect. It is the piece that allows you to support an end-user without having to take the keyboard and mouse."
    • "There should be more Mac support. Whenever a new Mac operating system comes out, the support is very limited. It takes them a while to get things up to date. We're seeing more and more people move to Mac from the Windows environment for various reasons, but their support for Mac is very limited. A lot of it might have to do with Mac itself, but there are ways to improve upon that. That would be my biggest thing for improvement."

    What is our primary use case?

    We use it for remote control, patch management, server monitoring, inventory, warranty, reporting, and automation. That's pretty much the gist of it, and there is a lot to that. Each one of these is very all-encompassing and very deeply rooted in the MSP world, and this is just the 30,000-foot view.

    How has it helped my organization?

    I come from a couple of MSPs, and it is the most heavily used piece. It allows us to support end-users and address alerts for problems within the environment. It is basically our eyes and ears into the environment.

    What is most valuable?

    The most valuable piece of the puzzle for me is what they call Live Connect. It is the piece that allows you to support an end-user without having to take the keyboard and mouse.

    What needs improvement?

    I've been a user of this tool for about 16 years, and I've seen it improve. One of the things that they need to improve upon is that when they roll out updates and patches to the system, they usually come with some bugs. Their QA needs to be a little bit better in terms of rolling out updates. 

    In terms of features, I really would love to see their patch management improve. They do have a newer patch management module that's in beta that I'm actually testing, and that needs to be their primary focus for the near future. That would be my biggest takeaway.

    There should be more Mac support. Whenever a new Mac operating system comes out, the support is very limited. It takes them a while to get things up to date. We're seeing more and more people move to Mac from the Windows environment for various reasons, but their support for Mac is very limited. A lot of it might have to do with Mac itself, but there are ways to improve upon that. That would be my biggest thing for improvement.

    Their security should also be improved. Kaseya had a very big vulnerability exploited out in the wild in July last year.

    For how long have I used the solution?

    I've been using it for about 16 years.

    What do I think about the stability of the solution?

    I didn't have any issues specifically with the product itself. Based on what I've seen over the years, the issues are usually related to the infrastructure and the speed of the hardware. So, it wasn't the application itself; it was outside of the application.

    Its performance over the years has got to an acceptable level. I don't have any complaints about its performance in 2021.

    What do I think about the scalability of the solution?

    It is absolutely scalable. It will max out around 15,000 endpoints. The sweet spot is 13,000 endpoints. From my experience, you start seeing performance lags with 15,000 endpoints. Ideally, we'd like to see a Kaseya server handle about 50,000 endpoints. I don't know when that's coming or if it's coming, but 13,000 to 15,000 right now is the sweet spot.

    We have several hundred users who use this solution.

    How are customer service and support?

    I use their tech support often. If you open up a Severity 1 dire emergency ticket, they're very responsive. If you just open up a standard ticket, it usually will get fielded by somebody who will make the phone call and escalate it, and that bothers me. I wish that their tier ones were able to handle a little bit more of the basic problems, but they escalate it. It is almost like they're buying time. So, their support could get a little bit better, but if you're opening up a Severity 1 ticket, they're very responsive.

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

    I have not used any other solution.

    How was the initial setup?

    It is in the middle of the road or moderate. Some people who are not familiar with it might find it a little bit more complex.

    If you're installing it on-prem, it is going to take at least a couple of days to put together the infrastructure and get the webserver and the SQL server going. Installing it on top of those would probably take another couple of hours. You can have something up and running with various people involved within a day. You just need a couple of people from different teams.

    I take care of its maintenance. They usually put out a patch once a month. So, usually once a month, there is a downtime. A couple of years ago, they used to take five to seven hours. They're now down to about 30 minutes of actual downtime. So, the outage is not too terrible these days.

    What was our ROI?

    When we were without it for a short time in July when everything shut down, it was difficult to support our customers. We could do it, but something that used to take less than a minute was taking 5 to 10 minutes. It is probably the most helpful tool in any toolbox for the MSP world.

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

    With the on-prem, you buy the agent license. That's a one-time fee, and it varies depending on how many you have. You also pay annual maintenance on the number that you have. So, there are two fees involved: a one-time fee and a recurring fee.

    I don't know its price. I've priced out some other ones that were more expensive, but we may have been grandfathered in. Both companies that I was at were already users of the system, and we may have had different pricing.

    What other advice do I have?

    I would advise others to leverage their professional services. We've used them while doing some migrations from one piece of hardware to another. They're very good. They're very thorough. They do take the additional time to sit down with you and lay the plan out. 

    It was early 2020 when we were migrating from an old piece of hardware to a new one, and we had to move the database and everything over. We engaged their professional services. They were very helpful, and it went very smoothly. I was really happy with the product plan.

    I would rate it a seven out of 10.

    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.
    Flag as inappropriate
    Learn what your peers think about Kaseya VSA. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
    564,322 professionals have used our research since 2012.
    Darshana Dissanayake
    Information Security Consultant - Security Operations Center (CISO) at USEZER
    Real User
    Top 10
    Makes it easy to manage devices, has a lot of useful features, and is inexpensive
    Pros and Cons
    • "I like the Live Connect module provided by Kaseya. It is a powerful module. I also like the Agent Procedure module. We work with it most of the time."
    • "Our main concern is related to security. Kaseya had a ransomware attack a few months ago, and it was a big concern for us because Kaseya was the main RMM tool that we were using. We faced a lot of difficulties accessing our users and systems. So, security is our main concern."

    What is our primary use case?

    Most of the time, it is used for remote desktop, but we also use it for running scripts, patching services, and auditing purposes.

    Currently, I am working with the SaaS version, but previously, I have worked with the on-prem version.

    How has it helped my organization?

    We can easily deploy agents to a bulk of devices, and we are able to manage devices remotely. We can easily get the required information. For example, if we want to get the serial number of a server, we can get that data with two or three clicks. This is the biggest benefit.

    What is most valuable?

    I like the Live Connect module provided by Kaseya. It is a powerful module. I also like the Agent Procedure module. We work with it most of the time.

    What needs improvement?

    Our main concern is related to security. Kaseya had a ransomware attack a few months ago, and it was a big concern for us because Kaseya was the main RMM tool that we were using. We faced a lot of difficulties accessing our users and systems. So, security is our main concern. 

    I would like to see mobile device management and mobile application management functionalities similar to Microsoft Intune. They probably had a module for this, but I don't know whether it is continued or discontinued. If they have such a feature, it would be good for customers.

    For how long have I used the solution?

    I have been using this solution since 2011.

    What do I think about the stability of the solution?

    The stability of the SaaS version is acceptable. Except for the ransomware attack, there were no major incidents. The on-prem version had a lot of performance issues, but they have fixed those issues in the current version.

    What do I think about the scalability of the solution?

    I am working with a startup company, and we have 20 people working on the SaaS solution. At my previous workplace, we had Kaseya, and we had more than 250 users using the platform.

    How are customer service and support?

    While using the on-prem version, we had to contact their technical support. They were friendly, and they provided the required support. We have had some issues in the past with the priority of the ticket where from Kaseya's point of view, it was a minor issue, but from our point of view, it was a major issue.

    It takes time to contact the account manager in this region. For Australia, they have an account manager in Sydney or New Zealand.

    How would you rate customer service and support?

    Positive

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

    I have been working with Kaseya from the start.

    How was the initial setup?

    We are now using the SaaS version, and we can configure it in a few hours or half a day. The on-prem version, which I haven't used in a while, takes longer. It is not as easy as the SaaS version, but anyone with the basic knowledge of the configuration apps can set up the system. You don't need high-level engineers. The on-prem setup can take up to two days. For the on-prem version, we need at least three engineers. There were several issues with the on-prem version, but they seem to have fixed those.

    It is easy to manage. For on-prem, you need to take care of the agent updates. You need to maintain the server side, the database side, and the application side.

    What was our ROI?

    We are a managed IT service provider, so we get more benefits when we use Kaseya.

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

    It is not expensive. Anyone can afford it. Most of the time, we get a discount for licenses. We had about 5,000 agents, and we received a discount on the price.

    There is only the licensing cost. If you use the on-prem version, you also have the infrastructure cost.

    Which other solutions did I evaluate?

    We had plans to use only Kaseya, but after the ransomware attack, we are considering an alternative solution or moving to another stable product because the impact of the security breach was very high. We have done some research regarding RMM tools, and feature-wise, Kaseya is better for us. Other solutions can't match its features. They have features, but they are not completely aligned with Kaseya. That's the only reason why we have still kept it, but most probably, we will move to a Microsoft product.

    What other advice do I have?

    I would rate it an eight out of 10. It is a good product. All features are useful and user-friendly, but security is our main concern.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    Manager at a tech services company with 51-200 employees
    Real User
    Top 10
    Efficient patching and good alert system, but the interface needs updating and technical support needs improvement
    Pros and Cons
    • "The patching is very efficient and we can rely on the alerts that we receive."
    • "The predefined reports are not up to the mark and you have to do a lot of customization."

    What is our primary use case?

    We primarily use Kaseya for managing all of the inventory, accessing the nodes remotely, and patching them. This includes the operating system and third-party applications. We also use it for the monitoring of services, such as vendor services.

    What is most valuable?

    The most valuable feature is remote access to the machine.

    The patching is very efficient and we can rely on the alerts that we receive.

    What needs improvement?

    The GUI is not user-friendly. You have to search and dig deep into the options to find things. The overall look of the solution is dull and boring.

    Technical support needs to be improved because the process is too long.

    The reporting is not well organized. The predefined reports are not up to the mark and you have to do a lot of customization. Along with that, the process of customization is not very user-friendly. You cannot just put things into the GUI and get what you are looking for.

    For how long have I used the solution?

    We have been using Kaseya VSA for between three and four years.

    What do I think about the stability of the solution?

    This solution is quite stable. As it is on a public cloud, you just need a good internet connection to access all of the features. You probably need an internet speed of about five megabits to test all of the features.

    What do I think about the scalability of the solution?

    It is quite scalable and easily manageable.

    How are customer service and technical support?

    The support is not one of the features that Kaseya would be proud of. Whenever anything happens and you need support, they have a long process where you have to create a ticket that begins at level one with an email response. It moves to level two and if things don't get resolved there then you have to go to the engineering team.

    We do have a Kaseya account manager that we can contact directly, and they usually help us.

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

    I have used SolarWinds and it has a very friendly user interface that is self-explanatory. By comparison, Kaseya is a little bit glitchy. SolarWinds is quite costly and you have to pay a lot to get features that Kaseya is offering at a much lower price.

    How was the initial setup?

    The initial setup is easy and you don't have to worry about a lot of things. You will get a link and just have to log in using your credentials. It is multiply authenticated in a two-stage process and then you are in. You just have to add your nodes to see all of the features.

    If you are a technical person and are new to Kaseya then you will find it a little bit difficult to configure because of the GUI. This is unlike SolarWinds. However, if you just give it some time then you will get used to it and things will become quite easy to do.

    What about the implementation team?

    We implemented this solution ourselves. We are a managed service provider and onboard products for our clients from time to time. We are asked to create approximately 1,000 machines on a monthly basis.

    We did have some help from Kaseya during the initial configuration, but after that, we worked on our own.

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

    The pricing is quite good and we are satisfied with it. It compares favorably to products like NinjaRMM and SolarWinds.

    What other advice do I have?

    This is a good solution and we like the group of people at Kaseya. The product is quite affordable compared to other RMM solutions on the market and we only have a few complaints.

    On-call support, for example, would make for a very big improvement. Whenever someone has an issue, we can just directly call the number and speak with a technical person who can help us at that very moment. They would be able to take over your system on that very call, for example. Ideally, the reporting will also be improved.

    The suitability of this solution depends on the need. For example, if you want to monitor your Linux environment and Linux services then the configuration is more difficult. That said, if you are using the PRTG Network Monitor or NinjaRMM then you cannot monitor Linux services. Ultimately, it depends on the use case.

    I would rate this solution a seven out of ten.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Emmanuel Okojesu
    Technical Analyst at FMDQ
    Real User
    Top 10
    Good training and support, but the patch deployment capability needs improvement
    Pros and Cons
    • "The training that we received was quite good."
    • "I have been looking for a way to deploy patches via the internet to selected equipment from Kaseya VSA, but it seems impossible."

    What is our primary use case?

    We use this solution for remote management.

    What is most valuable?

    The most valuable feature is remote management. It is quite robust.

    The training that we received was quite good.

    What needs improvement?

    I am having an issue with patch deployment. With a lot of people working remotely right now, it is difficult to deploy patches because most of my clients are not on the office network. I have been looking for a way to deploy patches via the internet to selected equipment from Kaseya VSA, but it seems impossible. This is something that I would like to have support for in a future release.

    Kaseya seems to download Windows patches, although I have not found a way to select those patches that I want to roll out, as it is done in the System Center. In SCCM, you can select the specific patches that you want to roll out. The only option I have seen is to approve or deny all of the patches that are available.

    The workflow is not quite straightforward.

    For how long have I used the solution?

    I have been working with Kaseya VSA for between seven and eight months.

    What do I think about the stability of the solution?

    I would say that because it does the job, it is stable. I don't use it every day, but so far, I haven't had any problems.

    What do I think about the scalability of the solution?

    We have about 200 users that are a combination of administrators, developers, and end-users. They do not work on it directly, but we capture the information from the endpoints on the developer's system.

    How are customer service and technical support?

    We had two training sessions with the support staff and they were good. The sessions were recorded and I quite enjoyed them. Personally, I don't like to contact technical support and would rather research the problem myself. If I hit an obstacle then I will contact support.

    Overall, the support is good and I am happy with it.

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

    I have experience with Microsoft System Center and there are some things that are easier to do with it.

    How was the initial setup?

    I was not present for the initial setup, as it was in place before I joined the organization.

    What other advice do I have?

    I have not tried automating any of the processes, although I have watched some videos and it seems to be straightforward.

    My advice for anybody who is considering Kaseya VSA is to run a proof of concept first so that they have a fair idea of what they're going into.

    Overall, I think that it is a good product and I may just have to better find my way around it.

    I would rate this solution a seven out of ten.

    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.
    RHS Tech Manager at a recreational facilities/services company with 10,001+ employees
    Real User
    Top 5
    Good remote support that allows support for Apple devices and offers good technical support
    Pros and Cons
    • "The remote support is the most valuable aspect of the solution."
    • "We actually upgraded the solution due to the fact that we needed the support for Apple devices. We haven't had a chance to test that part of the product just yet, however, that was our biggest criticism of the product prior to this most recent update."

    What is our primary use case?

    We primarily use the solution for remote support.

    What is most valuable?

    The remote support is the most valuable aspect of the solution.

    The solution now supports Apple devices.

    We were able to handle the implementation internally.

    The technical support is quite good.

    What needs improvement?

    We actually upgraded the solution due to the fact that we needed the support for Apple devices. We haven't had a chance to test that part of the product just yet, however, that was our biggest criticism of the product prior to this most recent update.

    For how long have I used the solution?

    We have had Kaseya for a while. That said, the VSA upgrade was just recently done last month. That's a rather new part for us.

    What do I think about the scalability of the solution?

    Our technicians, level one and level two, and our help desk all use this product.

    How are customer service and technical support?

    My experience with technical support is limited. Just in our recent upgrade, we dealt with the support team. We didn't face any issues with them. We're satisfied with their level of service. I don't have anything negative to say.

    How was the initial setup?

    We didn't do the setup; our network team does that. Therefore, I wouldn't be able to speak on how easy or difficult the initial setup was. I cannot speak to the deployment process either. I don't know how long it takes.

    What about the implementation team?

    Our network team handled the implementation in-house. We didn't use an integrator or consultant as far as I know.

    What was our ROI?

    We don't look at the product from an ROI perspective. We simply don't have a have remote support solution, or we didn't. SCCM may provide that to us. We needed a remote support solution, and therefore, Kaseya was what we chose at the time.

    Which other solutions did I evaluate?

    Right now, we're making an evaluation of whether to standardize with either this solution or the SCCM.

    What other advice do I have?

    I'm a direct end-user of the solution. We're just customers.

    We're using the latest version of the solution.

    In general, I would rate the solution at an eight out of ten. Thus far, we are quite satisfied with the product's capabilities overall.

    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.
    Joseph Bennett
    System Administrator at a computer software company with 201-500 employees
    Real User
    Top 20
    Very useful for patch management, unlimited scalability, and good stability
    Pros and Cons
    • "Patch management was very useful. Backdoor access to the clients was also very useful."
    • "Its scripting language kind of sucked. They have their own version of PowerShell inside VSA. if you want to reach out and grab endpoint information, for instance, to know how many end devices have a program installed, you actually have to write a script for that. It wasn't like how it is in CrowdStrike where you can just do a search, and it just happened. In VSA, you have to write your own script to do it. In terms of new features, an integrated MDM for mobile devices would be awesome."

    What is our primary use case?

    I used it in my previous company. I was on client support. We had about 300 clients, and each one of those clients had from 10 end-users to 300 end-users. We were using VSA in order to manage those end-user devices.

    What is most valuable?

    Patch management was very useful. Backdoor access to the clients was also very useful.

    What needs improvement?

    Its scripting language kind of sucked. They have their own version of PowerShell inside VSA. if you want to reach out and grab endpoint information, for instance, to know how many end devices have a program installed, you actually have to write a script for that. It wasn't like how it is in CrowdStrike where you can just do a search, and it just happened. In VSA, you have to write your own script to do it.

    In terms of new features, an integrated MDM for mobile devices would be awesome.

    For how long have I used the solution?

    I have been using this solution for two years. 

    What do I think about the stability of the solution?

    It is very stable.

    What do I think about the scalability of the solution?

    VSA is unlimited in terms of scalability.

    How are customer service and technical support?

    They are knowledgeable, but they are not so much responsive. They are definitely more responsive than IBM. The IBM cloud management support sucks.

    How was the initial setup?

    VSA is not as complex as Intune, but it is still somewhat complex and not very user-friendly. CrowdStrike is friendlier in deployment than VSA.

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

    It depends on what products you want. Kaseya loves packages, and if you are packaging, it is more affordable. If you're not packaging, it tends to be a little bit more expensive than others.

    What other advice do I have?

    I would advise others to definitely do onsite or virtual demos, and make sure they are asking about everything. They should make sure to get a demo of the product doing what they are planning to use VSA for. This way they can see how much work is going to go into implementation.

    I would rate Kaseya VSA an eight out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Systems Engineer at a tech services company with 51-200 employees
    Reseller
    Top 10
    An integrated IT systems management platform with a good patch management feature
    Pros and Cons
    • "I like the remote control, audit, inventory, patch management, software management, and monitoring features."
    • "The agent-based monitoring solution can be improved."

    What is our primary use case?

    We use Kaseya VSA for software and patch management.

    What is most valuable?

    I like the remote control, audit, inventory, patch management, software management, and monitoring features.

    What needs improvement?

    The agent-based monitoring solution can be improved. I think they need to be updated. The remote control feature could be better. It would also help if they had a mobile device management feature.

    For how long have I used the solution?

    I've been working with Kaseya VSA for more than a year.

    What do I think about the stability of the solution?

    Sometimes patching is unreliable. I haven't encountered any other issues.

    How are customer service and technical support?

    Technical support is good. If I have inquiries, issues, or a troubleshooting encounter, I can raise a ticket on their website and ask for support. 

    On a scale from one to five, I will give technical support a four. 

    I gave them a four because they don't always fix the issues that I encounter. For example, they suggest fixing the problem on the next version or the next enhancement.

    How was the initial setup?

    The initial setup was difficult for me. It would help if you had the license and SQL driver for onboarding successfully.  

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

    I think it costs more than ManageEngine.

    What other advice do I have?

    I can still recommend this product. It'll help do technical tasks like remote control, patching, monitoring, audit, or inventory. You can also monitor devices in the production or the company's environment. But it's not a perfect solution.

    On a scale from one to ten, I would give Kaseya VSA an eight.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller