we use Connectwise Screenconnect as it is by far the best remote control software arround. We only use Kaseya in the event we need to load Screenconnect or fix Screenconnect on a computer.
My technicians don't have PCs but we all work on a terminal server in our cloud.
Splashtop uses an ID to distinguish between the Splashtop users. This ID is the same for all users working on a terminal server. And that's the problem.
So every user must have it's own workstation to being able to use Splashtop.
The workaround was a browser based remote control. But that was so slow, that even the sales rep agreed with me, that this is no working solutin for now...
Just because I happened to look at a small client that was complaining about the patching, I see endpoints that show vulnerabilities because Adobe Reader and Chrome are out of date. They also show errors because those patches could not be installed because they are not licensed for 3rd party patches.
Is it too much to ask that an endpoint does not show an error if it is not licensed for something and only shows vulnerabilities if patches it is entitled to are not applied?
Make sure you don't have a 3rd-Party Software profile assigned to the machines and you shouldn't see these vulnerabilities listed.
We have only one customer (currently) paying for 3rd-pary patching, and theirs are the only machines with the 3rd-Party Software profile assigned and the only ones that report Adobe, Chrome etc. as vulnerabilities.
No 3rd party profile or 3rd party enabled.
If it's trying to patch 3rd party apps and 3rd-Party Support in SM is not enabled I'd open a support ticket
So - what?? Has everyone somehow uninstalled Patch Management from their VSA? Do you really think changing your RMM is going to be easier than rolling back to Patch Management until all the Software Management kinks are ironed out? Some of the comments sound like "I have a splinter.. quick - amputate!" :)
We've moved every one of our MSP clients back to Patch Management with great success and tightly controlled scheduling.
Application Updates fully automated by NinitePro and soon Chocolaty.
Windows Upgrades via an app + procedure for orderly scheduling of these often-invasive updates.
We're still staying on top of Software Management 'cause its a good concept. The last engineering preview showed it heading in the right direction, but the finish line is still in the distance where we're concerned with providing support to MSPs. There's no reason to change RMM and no reason to stick with S-M if it isn't working for you.
My issue is strictly around the reporting. Only 15% of all of my machines state to be in compliance, yet they are not missing scan or deployment threshold I have set as 5 Days and 95% patch compliance.
I have several tickets open with no real answer as to why I am not having success in compliance reporting.
your terminal server is not corectly configured.