The product was basically used for remote-in support and monitoring for the ~1,500 endpoints that we manage. The intent was to use the integrations to be able to deploy group policies and updates and push down antivirus updates such as Windows updates and things like that. Our intent was to leverage all of these so-called features that never functioned at all and ended up just putting us in a really bad position, left scrambling to find a functional replacement on the fly.

We actually use it for a few different purposes. We use it as remote control connectivity software, allowing us to troubleshoot and work with staff and customer computers on-site without having to travel to the locations. It is also used for patch management and software deployment. Instead of having to manually go out and do them on each computer, we run all of our Windows updates and Mac updates through Kaseya VSA.

We're a small computer shop, so we use it as the remote control tool when clients call for help and ask us to walk them through something. But we've also got it set up to monitor Windows logs and notify us when an update fails to install or a hard drive is developing a bad block. The sort of thing that allows you to stay ahead of trouble. 

Also, little housekeeping things like hard drives filling up, so you empty the recycle bin, delete the temporary folders, that sort of thing. It's scripted, so it all happens automatically. We get a note saying, "Hey, there was a problem, but we took care of it," which is kinda nice.

I use the solution since it functions as a virtual system administrator that allows me to monitor our company's clients' networks, and the tool serves as an RMM solution. The product allows me to monitor our company's clients' networks and administer and make changes. The solution also allows me to deploy policies, especially in areas like patching or software updates. The tool serves as a single platform to manage everything with just a few clicks.

We have nearly 400 computers at the company but no full-time support tech, so VSA is our hub for everything. It's a tool for remote management. We want it to do software management, pushing out applications, antivirus, etc. We use it to manage all that to make our life easier and automate as much as possible. 

Kaseya VSA is used for maintaining laptops, patching the systems, and securing the platform.

This solution is our RMM tool and we love the deployment features. We just develop a package for each dual client base that we have or for each client network, or actually in some cases we have two packages depending on if it's going to be a remote user or an in-house user. My partner sets up the packages and we install the packages on the computers as they come in and they do pretty much everything for us and get all the software installed. The only thing we have to do is put in a couple of passwords for the individual users and we're off and running.

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

We primarily use the solution for remote support.

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

The solution can be deployed on-cloud, on-premise, and hybrid.

We are an MSP-managed service provider, and we use VSA and to automate our IT management for our customers so we can work more efficiently and effectively. We are customers of Kaseya. 

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.

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.

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.

Certainly, our company is a Managed Service Provider (MSP) supporting multiple organizations in Australia. We use IT Glue for comprehensive documentation, including password storage and sharing. Additionally, we use RMM for remote support, job scheduling, and script execution on devices for effective patching.

I use VSA to create reporting, scheduling of agent procedures, remote control, and monitoring.

There is an on-premise and cloud version of Kaseya VSA.

I use Kaseya VSA to manage peoples' systems and perform patches from time to time.

It would be impossible to do our job without the solution or a similar product. It helps us get to multiple endpoints in multiple sites in multiple counties.

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.

We use this solution for remote management.

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.

We use Kaseya VSA for simulation for customers also using the service.

We primarily use the solution for remote management and remote control.

We use Kaseya VSA for software and patch management.

IT outsourcing.

We are service providers. We use this solution to deploy our services to our customers.