What is your primary use case for Kaseya VSA?

We use the solution as a remote control tool to help clients.

On an internal basis, we use it to manage our users. Externally, we provide an end-user support service, including remote support, with the company. Once we implement it on the network, we've noticed, on average, a 15% reduction in truck rolls. By truck roll, I mean a man in the venue actually has to come out to fix a problem. For example, a customer complains, "My email address isn't showing up. Sorry, I'm in a fix. This could be your email as well." And, we live in South Africa; it's a big country, so for me to rush somebody out to, like, the northern cape or something like that, it could take them a day to get there. If I use Kaseya, I can have my call sorted out. Up to 13% to 15% of my calls may be sorted out remotely, which makes for a much better customer experience.

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

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.

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.

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.

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

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.

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.

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.

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

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

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

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

We primarily use the solution for remote support.

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 are service providers. We use this solution to deploy our services to our customers.

We use Kaseya VSA for software and patch 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 this solution for remote management.

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

IT outsourcing.