Any RMM can have this problem. Screenconnect/ConnectWise Control is very well protected as far as i'm concerned.
Offcourse if you run it on premise (instead of hosted) you are responsible to keep a server well protected and up to date.
The known problems with RMMs and Ransomware where all servers that where not secure enough, not infected through the RMM itself.
If setting it up per group is too hard, having the option to have multiple app.config sets, and than per agent assign which app.config to use would also work.(Naming or Numbering the App.config sets)
Groups can overlap, per agent would take care of that problem.
Come on, this has been promised already years ago. Put it on the road-map instead of just considering it.
This really makes the product so much more useful and sell-able (the last both for you and us)
We have several different views from customers on Control. Those who want the icon to show those who dont. Those who want to allow remote control consent and those who dont mind.This would fix those issues and o so many more.
Fixed in the new update 6.6.18120.6697
This has been a problem with loads of remote control software packages, the drivers of Matrox are just the worst.
If you have to problem on a PC with Windows that's not used to graphically intense there is a solution :
- Go to Display settings advanced, tab troubleshoot and lower the hardware accelleration to at least the middle of the scale.
Now you will see Screenconnect (Hate the new name) acting fast and the processor of the PC is also happy again.
Unless we are talking heavy games, I've only seen speed improvements after this change.
I came across this post and that really helps a lot already !
If you just need temporary alerts, there may be an easier way.For the Trigger:
Event.EventType = 'Connected' AND Session.HostConnectedCount = 0 AND Session.Notes LIKE '*ALERTME*'
Then drop an "ALERTME" note on any system you want to get an online alert for. Delete the note when you want to stop getting alerts.
I also create a session group for Notes LIKE '*ALERTME*' to make it easier to locate which systems are alerting.
You could expand on that by adding a tech's name to it, ALERTMARK, and set up a different trigger for each tech. That way they can each create and remove their own alerts without needing permissions for the admin panel.
Hi Ben, can you explain what the benefit is, the interface is nearly unusable in the new setting.
Have a look at the screen when it's used with a secondary language. (As we use)
I'm all for new interfaces but this looks more like a bug then a wanted feature.
Or does it have to do with the other options on the same screen in Administration that use it ?
Hi Ben, immediately after seeing your reply i realized my mistake.
I pasted the added text after the </SceneConnect UserInferfaceSettings>
(Instead of before it)
The program does not crash because of that but the result is that everything in the section is ignored.....
Sorry about that. On the other side we now know that the program behaves like this, good to know.
I've also corrected and explained my mistake on the forum.
Hi Ben i'm ever so sorry..... the bug has been re-introduced.... in the latest update. (1219 at the end)
I now have systems that when i take them over no longer show the banner....
Could be that this happens only after updating the systems before a reboot.
Further info :
One system does not show it when i enter it (Windows 2008 R2 Server)
Another system did show it (same os).
I returned to this other system a few minutes later, no body had done anything on the system in the meantime, however now the banner also fails to show.....
Customer support service by UserEcho