Kaseya VSA Reviews

Our top uses are remote support, asset and inventory management, and patch management.  

The patch management and the remote support are very good, especially the remote support. There is a module built into the solution which allows remote control without necessarily interrupting the user. We could manage things in the background without them seeing or interacting with anything, which is a very useful feature. 

The response to bugs is slow and software improvement comes slowly too. The lack of response to our feature requests made it feel like they were going into a black hole. Additionally, when we encountered bugs or issues with the VSA, they were slow to respond to those too.

The solution could also use better management and functionality for file transfers. Now when you want to do file transfers, you can simply copy a file and paste it over. Sometimes that works, and sometimes it doesn't. I like to have a file transfer window because I can see the data tree on both machines, mine and the remote. This is an industry standard and I would like them to bring this feature back. I understand they were trying to make things easier but sacrificing this functionality isn't the way to go about it.

We have been using this solution for the past 12 months.

The stability is good, there was one occasion where the site was down and we couldn't do anything, but overall I have no complaints about that.

The scalability of the solution is good, it allows for rapid deployment of under an hour, whether for a smaller or larger number of workstations. We package in antivirus along with the remote control aspect, which allows very fast onboarding of clients at a basic level.
The probe functionality allows us to leave the probe on the domain controller and anybody connecting to the network would have Kaseya deployed to their workstation, and we receive an alert of the new addition. This is excellent for management and deployment.

Regarding our internal use of the solution, we had about 35 people using it. 

Customer support has been quite responsive. By phone I recall getting in contact with support within a few minutes, and opening a chat session was even faster, so I would use that option more than anything else. 

Positive

We primarily used LogMeIn before switching to Kaseya. The problem with LogMeIn is that although they provided remote control support and to some extent asset management, there was no robust reporting to give us the data we needed. This made us feel like we were being overcharged for the product. That being said, Kaseya is not cheap either, but we are getting a lot more for our money. That was the reason why we left a competitor and came to Kaseya.

The initial setup was a mix. Some visually poor UI elements complicated the process, while remote control of assets was straightforward. 

The deployment was very quick thanks to the incredible probe functionality. We would install a probe on the domain controller and assets would be checking in within minutes. 

You're going to pay for this solution, but you're going to get so much more out of it in reporting, asset management, and the ability to manage your clients. I would recommend giving Kaseya serious consideration and I would recommend implementing it. 

I consider Pulseway a viable alternative, but it's a bit too expensive. They don't have a probe functionality either, even though it has been frequently requested on their website. 

I would rate this solution a nine out of ten.

We use the solution internally, deployed to our own workstations as well as with our customers. There would be times while working on something where I would encounter an issue, and a network engineer could remote to my system to help get a solution quicker. We also use the solution for our own inventory management.
I would recommend Kaseya to any MSP, because their product is a little ahead of the innovation curve compared to the competitors.  
The ability to quickly onboard clients is phenomenal. I feel that compared to its competitors, the solution is not as complicated. You log into the portal, create an organization depending on the client, create an installer, throw it on the domain controller and let the software work for you.

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.

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.

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. 

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.

I have been using this solution since 2011.

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.

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.

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.

Positive

I have been working with Kaseya from the start.

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.

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

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.

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.

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.

The most valuable features of the solution are its ability to offer control remotely to its users and provide patching capabilities to users.

The technical support of the solution is an area with shortcomings that needs improvement. The solution's technical support should respond more efficiently and quicker. If we ever encounter issues in our company, the technical support takes too long to provide the proper resolution.

I have been using Kaseya VSA since around 2018 or 2019. I use the solution's latest version. My company is a reseller of the solution.

Stability-wise, I rate the solution a seven out of ten.

After some upgrades of the solution, if our organization encounters issues or concerns with the device or the solution, Kaseya's technical support team cannot handle our issues. Kaseya's technical support, whatever issues we face, will be fixed after the upgrade in the solution, so they do not provide an immediate resolution to the issues we face.

It is a very scalable solution. Scalability-wise, I rate the solution an eight out of ten.

In my organization, more than ten people use Kaseya VSA.

I rate the technical support a five out of ten.

I am not entirely happy with the technical support team of Kaseya.

Neutral

On a scale of one to ten, where one is difficult and ten is easy, I rate the initial setup an eight since it was fairly easy.

The solution is deployed on the cloud and on-premises. You need to provide a dedicated server to Kaseya VSA for the on-premises version. I have no visibility over whether the solution was configured or installed using which cloud provider.

The time for the deployment phase of the solution depends on how many agents one wants to install. If there are too many agents to be installed, it takes over a month, but if only 100 agents or lower than that have to be installed, then it will not exceed a month.

The solution's deployment phase involves installing agents for which around five to ten staff members from my organization would be required.

Though I don't have complete visibility over the solution's pricing, the solution is not cheap, from what I remember. The solution is on the pricey end.

Those planning to buy the solution shouldn't expect quick support. It is the best solution for patch management and its ability to provide control remotely to its users. Kaseya does provide an update on the solution.

Kaseya VSA is not the perfect solution, and I know that there are no perfect solutions.

I rate the overall solution an eight out of ten.

We are resellers. We use it internally, but not all of its features.

The most valuable features of this solution are automation, inventory, and patch management.

The majority of end users want complete software management. It focuses on a thorough evaluation of the initial projects in the software.

It should focus on the lifespan or timeline of the software and hardware. The majority of end users ask if there are any notifications or advice regarding when they purchased the hardware and software and when it will expire or need to be replaced, and there are none in Kaseya. As a result, even the software metering.

Better software awareness and metering are required.

Metering software depends more on what they use it for, and how much software is available within the company.

If I think of any additional features that are required, it will be for detecting or including mobile users of managing endpoints. There is currently no mobile license for cell phones, Androids, or even iOS. I believe we should include a VSA license to provide complete endpoint management.

We are resellers and have been dealing with Kaseya VSA for six or seven years.

Kaseya VSA is a stable solution, some of the end users have been using it for years.

The scalability is good; it is up to the end-user or we can add additional licenses if necessary. We can conduct policy checks as well.

I would give the technical support a four out of five. There is no such thing as a five. You coordinate things, and it is available as needed.

The initial setup is straightforward.

It is simple to implement, especially when the end-user knows what policy they want to implement.

The implementation was completed in-house. We used the Kaseya method of implementation.

In terms of maintenance, we don't need a lot; one person can monitor it.

In the Philippines, licensing fees are paid on a yearly basis.

I believe it is competitive, depending on the number of users purchased. It's scalable in terms of pricing.

Fees are paid per license, per user, and per year.

It is, in my opinion, competitive in the market. It is determined by the number of users and licenses needed. Depending on the license count of users, the price ranges from $10 to $80 USD.

I would rate Kaseya VSA an eight out of ten.

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.

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.

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.

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.

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

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. 

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. 

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. 

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. 

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

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.

We primarily use the solution for remote support.

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.

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.

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.

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

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.

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.

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

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.

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

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.

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.

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.

I have been using this solution for two years. 

It is very stable.

VSA is unlimited in terms of scalability.

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

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.

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 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.

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.

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.

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.

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

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.

It is quite scalable and easily manageable.

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.

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.

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.

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.

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

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.