Kaseya Virtual System Administrator (VSA) is a cloud-based Remote Monitoring and Management software. VSA unifies the monitoring of system infrastructure and endpoints and is designed for use by IT teams and MSP’s. It offers a robust crowd-source automation scripts library, as well as antivirus and malware capabilities with real-time threat alerts.
N/A
Microsoft System Center
Score 8.3 out of 10
N/A
Microsoft System Center is an enterprise-grade IT Operations Management (ITOM) suite designed for the centralized administration of data center infrastructure, virtualized environments, and hybrid cloud workloads. The platform provides unified management across heterogeneous environments, including support for Windows Server, Linux, and Azure Stack HCI.
System Center is Microsoft's ITOM stack for organizations that maintain a significant on-premise footprint, vs the company's Azure-based…
$1,323
Pricing
Kaseya VSA
Microsoft System Center
Editions & Modules
No answers on this topic
Standard Edition
$1323
Datacenter Edition
$3607
Offerings
Pricing Offerings
Kaseya VSA
Microsoft System Center
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Kaseya VSA
Microsoft System Center
Considered Both Products
Kaseya VSA
Verified User
Anonymous
Chose Kaseya VSA
Kaseya VSA compares well to other solutions available. I think some of the other solutions so have some small areas which are better than Kaseya VSA, however as an overall product, Kaseya VSA seems most complete. I'd like to see them continuing to evolve the product as it …
While Atera and NinjaRMM are both solid products, they seemed to be more oriented to MSPs which we aren't. There were more features associated with costs per user/system, etc. that we would never utilize.
We looked at several options besides Kaseya in the beginning of our research process. We preferred the layout, support, and overall feature rich platform of Kaseya to some of their competitors. We also liked the ability to grow with Kaseya as needed and the ability to add …
What's Up Gold is more of a monitoring application and very good at that, but doesn't have the management tools that VSA provides. It requires additional applications and you lose the "single pane of glass" concept.
ConnectWise, at the time we looked at the product, did not have …
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 …
We used to use Netop for many years prior to Kaseya. The main reason that we switched was because with staff working from home we needed a cloud based solution and Netop required gateway servers or PIN servers to be configured in order to be able to access those staff while at …
Kaseya is the worst remote desktop software I have ever used. I could never understand why I constantly was unable to connect to our remote desktops. Not being able to do my work, the lackluster customer service, and the constant complaints from my workers is the reason why we …
Kaseya is cheaper compared to Continuum RMM solutions, and also has a better feature set of tools. The reporting has more customization than what continuum offers.
I think that one of the best features Kaseya has over the other tools I mentioned is more maturity and expertise in the area, so you have a good support and good know-how in the network. It also works in most use environments.
Automate is by far more customizable and affordable, a lot of our pain points in Kaseya are addressed with Automate. In our case, we have used Kaseya since 2012-2013 and have started migrating our customers to Automate in the past year.
VSA is easily on par with SolarWinds N-Central but ConnectWise Automate is the best tool out there for RMM. Automate shares some of the clunky interface that VSA has, but it is extremely fast and reliable. N-Central has the best organization of the three, it is very easy to …
The way LabTech integrates with ScreenConnect and Teamviewer is just SO much better than Kaseya. I feel like Kaseya is a bit more intuitive though as opposed to Labtech that you should probably get some real training for. Scripting in LabTech is more reliable. I've never had a …
Both SolarWinds & Autotask appears to have a better user community, but they have the same issue with out of the box scripts (non-existent). With Kaseya, I can write everything in PowerShell, dos, vb, java, and then have Kaseya execute across applicable devices. In fairness, …
It has been a long time since I tested competitors so it would not be fair for me to compare existing version of Kaseya with older versions of the products I have tested int he past. It is very hard to change and I am very Happy with Kaseya therefor no intentions of testing …
There are other products that do some of what Kaseya does, but I've not personally worked with another product that does everything Kaseya does. Sure there are plenty of remote control products, but products that do as much as Kaseya are few and far between. Hard to go wrong …
Kaseya is not as good as Labtech but gives you great bang for your buck. I would recommend it to anyone trying to achieve a proactive approach to network monitoring.
SCCM is often considered superior to Intune because it is more predictable and transparent in day-to-day operations. Errors in SCCM are clearer and easier to troubleshoot, whereas Intune issues can feel vague and harder to diagnose. SCCM also offers rich, built-in features such …
Microsoft System Center really integrated with our windows system better than any other 3rd party product which obviously you would expect to a certain extent. Our main reason to procuring System Center (apart form the options)was licensing costs. We already had a Microsoft …
None. We are a Microsoft business, and this is THE tool for imaging, packaging, remote support, and antivirus management. Microsoft's tool is the best for managing its software, systems, and antivirus clients. I will say that Microsoft Intune, the cloud platform, can be used …
The capability of SCOM as far as monitoring Windows systems is concerned is far greater than any monitoring product out there as both are a Microsoft product so integration and discoveries work well and fast.
The versatility of the suite of application provided by the Microsoft experience center was way above the other competitors , it helped gained leverage over the other products in the market . That why we made the decision of choosing Microsoft system center as a infrastructure …
We use Azure, we have lisences, so we have no needs any other cost. And also, we want to save backup data in Azure. Veritas ask additional cost reagurally and have to rebuild bakcup environment.
Because Datadog was too small, we decided quickly to use Microsoft System Center. We use a lot of other Microsoft products so that discussion was quickly set internally.
We have used Ghost from Symantec (licensed), FOG and Clonezilla which are freeware products. All three products had their pros and cons. The two freeware products were functional but did lack some polish, and Ghost was a good product for imaging of desktop computers. All did …
We previously used a mix of FOG and Clonezilla to image machines. The biggest issues with these products is that changing one piece of the image required you to rebuild the entire image itself. These pieces of software also did not allow you to manage applications and Windows …
We are using Microsoft products for a long time, so the overall confidence played a part in the decision, the feature set and licensing cost was also very high when compared with above products, so we decided to use System Center for our environment, so far it has solved many …
We selected it simply because it is less expensive than the competition, but yet just as good. We saw no reason to go outside the walls of Microsoft for this task. We are satisfied with the product.
This was used to monitor uor non-Windows systems and was cumbersome. Their licensing was per device with how many agents you needed; however, with System Center Operations Manager, their billing was a lot easier for their product.
All comparative features are way expensive and complex to configure in all other competitors. Value to money and ease of deployment for Microsoft based environment
Microsoft System Center has more options. Microsoft System Center has the ability to image PCs as well as remotely connect to PCs, and software installation and patching where Symantec Ghost Solution Suite didn't handle all of these options as well. We haven't looked at many …
Much better UI for system center. Also, Tivoli was discontinued, so it was an easy decision. Altiris was acquired by Symantec but was unreliable and painful. It's UI was unresponsive and generally outdated. It wouldn't clean up old packages and would hog GB of disk space, …
SCOM is better than OMi for Windows-based servers monitoring. You need to know how to use Visual Studio to customize the management pack. Dynatrace is way better for all Application Performance Manager.
It has its similarities between the two from a ticketing standpoint but as a primarily Microsoft shop it is nice to have a product that was created to play along with other tools that we are using such as SCCM. We like Jira for the project management tools and Cherwell for …
It is an excellent product for monitoring features like Exchange, Active Directory, DNS. Monitors are custom designed and can be adjusted to any system. Great monitors can be created even when monitoring open-source systems.
How SCEP stacks up against some of the other AV solutions/products is that it does a pretty good job overall (not the best in the industry) at detecting/removing malware, which is the main focus for a product like this. It is also easy to use on the end-user side, which can't …
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.
We used a product before that was designed to prevent users making changes and saving files to the desktop computer. This required a renewal of the license. By using SCCM in our environment we were able to discontinue using that product because SCCM allows us to completely restore a machine back to the original configuration. We have taught our users to save their individual work on either a network drive or a cloud drive. By doing this, if we do a re-image of their machine they have lost no data, and it makes for a faster resolution. In some instances having a computer in our SCCM environment it can become cumbersome when creating new users for very specific purposes. It can be done by creating new organizational units and applying new policies but when in a pinch it can be frustrating. For the most part we have tried to make "new" purpose images and groups to at least accommodate a quick install.
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.
One of the biggest drawbacks to SCOM is the sheer scope and complexity of the system. This can be a pro and a con. The system is very customizable, what you put into it is what you'll get out of it. That said, the learning curve is fairly steep. An organization needs to be committed to putting time and resources into SCOM to get the most out of it. I've heard stories from colleagues of several different companies that invested in SCOM and then abandoned it due to the excessive time and care required.
SCOM is expensive. Not only is the enterprise licensing costly, SCOM requires it's own servers, operational and warehouse databases to be maintained.
The OOB SCOM reports are a bit clunky and feel outdated.
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.
It is not user-friendly for the most part. With IT infrastructure, sometimes it cannot handle excess requests. Every few months, you will need an upgrade in terms of server resources to keep up with incoming alerts and requests. This does not happen all of the time, but it does happen when there are too many requests.
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
There is a fair amount of documentation out there to help you when you have questions or run into issues with this product as well as tutorials on some of the more common tasks. Between the documentation and the overall ease of use we haven't had to deal with direct Microsoft support for this product.
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.
None. We are a Microsoft business, and this is THE tool for imaging, packaging, remote support, and antivirus management. Microsoft's tool is the best for managing its software, systems, and antivirus clients. I will say that Microsoft Intune, the cloud platform, can be used for those with heavy 365 usage, but for us, that does not meet our current company needs.
The positive impact it has had on ROI is that it has been a solid AV product in our environment, meaning it has worked well when running on client computers. It doesn't use a lot of system resources on the client-side, so that helps end-users productivity of not being slowed down.
It has been good for the end-user, since they really don't need to take additional training or consult user manuals, in how to use the product.