Your comments
Nathan,
We have found an issue that affects on-premise installation performance, cloud instances were not affected so we decided to release to the cloud first while the issue is resolved. We hope to have a fix for this before the end of the week and will post the download as soon as it is ready.
Unfortunately there is not a way to only subscribe to stable release notifications.
Jeremy, you are able to use different URI as described here:
https://docs.connectwise.com/ConnectWise_Control_Documentation/On-premises/On-premises_knowledge_base/Change_the_relay_addressable_URI
We've always liked to be transparent, so we'll try to be better about adding a brief note when we close issues with a high number of votes in the future.
As a product feature, there wasn't a clean way to implement this specific ask. We discussed it multiple times and determined it wasn't a good fit. Our conversations led to improvements, like the introduction of the security toolkit which simplifies HTTP-HTTPS redirect, but a Let's Encrypt integration would have been very hard to maintain and a hack at best.
When feature requests like this come up, we tend to leave them open hoping that advances by the vendors, new tech, and sometimes team bandwidth will allow for them to be completed in the future. We perform internal check ins on most of these issues every 3 to 6 months, but sometimes issues get cut to make way for higher priorities.
Recently, we've prioritized advances in the performance of the session manager, relay, and the router to allow for better performance and scalability. We've also been looking at long time asks that will make the product more human for users, so they discover some of the power user features inside of the product. This of course is outside of the work to stay vigilant in our security posture and squash bugs.
Thank you all for your feedback, it is heard and appreciated.
Sean White
Senior Product Manager
We will be releasing an updated permission specifically for Backstage in early q4. Currently to disable the Backstage feature, remove the SwitchLogonSession permission from a user's role.
Hey there! Cody is correct, the next plan for the security events are to make them reportable (will be available soon). We will then work on adding security events to our Triggers, which is slated for later in Q3.
Customer support service by UserEcho
The Essentials menu option 'Send Keyboard Clipstrokes' is independent of the shared clipboard and will allow your hosts to send what is on their clipboard without making it available on the clipboard of the guest machine.
This means that you can disable the clipboard as described here: https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Host_client/Essentials_menu/Clipboard_sharing_during_a_remote_session, but still be able to send the host clipboard to the guest machine.
As to the ability to clear clipboard upon disconnect, we have begun scoping this issue out, and I'd like to share some of the potential pain points we have regarding clipboard history in Windows 10 and 11
Clipboard history
Our philosophy has always been to be very careful when making a change that could impact the host or guest machine in an unintended way. In this case we wouldn't have knowledge of which clipboard content to clear; it would be very likely that we would be clearing information that was stored intentionally by the guest or the host, and affecting multiple devices.
That's not to say we won't do this, but would like to hear from our partners what they would expect the behavior to be if clipboard history is enabled.