We performed a comparison between Kaseya VSA and Microsoft Configuration Manager based on real PeerSpot user reviews.
Find out in this report how the two Patch Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The way Kaseya VSA treats application vulnerabilities is good. They have released some new features that have been a benefit, such as updates from the Microsoft repository directory."
"This solution is our RMM tool and we love the deployment features."
"The product's support team is very quick to respond, especially because the tool's technical team operates in the same time zone where I am located."
"VSA installs an agent on every computer that allows users to create a help desk ticket with one click. That's why I chose VSA. Many users never create tickets when they have a problem. Sometimes I won't know about an issue until they run into me and say, "Hey, this has been broken for two months.""
"Kesaya is highly configurable."
"The ease of access and ease of use was great."
"The patching is very efficient and we can rely on the alerts that we receive."
"The remote support is the most valuable aspect of the solution."
"The solution has a very good set of features."
"It is a good choice for deployment that performs very well."
"We're a Microsoft-centric organization, so we are happy with the integration between products."
"The initial setup is fairly straightforward."
"It gives us the ability to set up schedules, according to what our security requirements are, to automate the patching of our servers and desktops."
"The most valuable features are application deployment and task-sequenced imaging."
"It works well for the endpoints for the customer I'm consulting. It has a bunch of knobs, and you can tune it to do lots of things."
"The ease of usability is the most valuable feature. It's user-friendly."
"The agent-based monitoring solution can be improved."
"It's very difficult to update the third-party software on every device."
"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."
"The predefined reports are not up to the mark and you have to do a lot of customization."
"I believe we should include a VSA license to provide complete endpoint management."
"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 is hard to use at first until you understand how it works."
"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."
"SCCM does not scale well, which is one of the reasons we are not going to continue to use it."
"One area of improvement is regarding the patching of Office 365 products. We have some difficulties on this side, and it can be improved."
"Its client interface should be more accessible, and the notifications should be more customizable from the console. It should be more user friendly and have some kind of customized notifications so that we can use it on the client side. These are the reasons why we restricted its use only for the server environment and didn't use it on the client side."
"The assets have reached their end-of-life, and patching them is a complex and laborious task. It would be highly advantageous if there were an integrated solution that provided distinct options for each end-of-life asset, streamlining the process and facilitating comprehension."
"Microsoft Endpoint Configuration Manager could improve the integration."
"In terms of scalability, I believe there's room for improvement. While SCCM is capable of handling our current needs effectively, scalability could be enhanced to accommodate future growth and larger deployments."
"I would like to see more automation."
"It would be of benefit if Configuration Manager could be connected/integrated with multiple Microsoft Intune subscriptions rather than just one (the current limit)."
More Microsoft Configuration Manager Pricing and Cost Advice →
Kaseya VSA is ranked 4th in Patch Management with 29 reviews while Microsoft Configuration Manager is ranked 1st in Patch Management with 78 reviews. Kaseya VSA is rated 7.6, while Microsoft Configuration Manager is rated 8.2. The top reviewer of Kaseya VSA writes "Single portal management, cost-saving, with thorough technical support". On the other hand, the top reviewer of Microsoft Configuration Manager writes "Seamless system updates, useful integration, and reliable". Kaseya VSA is most compared with ConnectWise Automate, NinjaOne, Microsoft Windows Server Update Services, Datto Remote Monitoring and Management and N-able N-central, whereas Microsoft Configuration Manager is most compared with Red Hat Ansible Automation Platform, ManageEngine Endpoint Central, BigFix, Microsoft Intune and NinjaOne. See our Kaseya VSA vs. Microsoft Configuration Manager report.
See our list of best Patch Management vendors.
We monitor all Patch Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.