Every time we update to a new version of ConnectWise Control, it freaks out our EDR.  We spend days dealing with hundreds of benign alerts -- because your update files aren't signed.  It also delays the rollout process.  Would really appreciate if you used signed files for updating.  It is more secure and significantly less headaches.

I would like a way to set a default zoom level, particularly to 100%. Every day the zoom is automatically set to higher, we have to change it to 100%. It would be nice to have the functionality to set a default, as you can with screen quality.

We regularly transfer fairly large files from our customers to our agents (typically large log files or database files) using the file transfer controls. During the transfer, the session become very laggy and unusable. We suspect this is because all of the available bandwidth is used for the file transfer.

We'd like to see an enhancement to restrict file transfer bandwidth either per session with an in-session control or to detect when other activity is happening in the client and implement a QoS-like solution to protect the control traffic.

It would be great to have a QueuedModifyHost event to be able to update the session's host. I would like to be able to do so by utilizing a CustomProperty I set on sessions I create via the RESTful API Manager extension. 

Additionally adding support via a new API function to change the host on a session, or being able to set it upon creation would all be welcome features, as right now created sessions via the RESTful API Manager extension default to the username specified for the extension.

For security we would like the ability to enable a feature that would automatically clear stored credentials when we disconnect from a session.

Improve quality and refresh rate. The lag when moving windows is highly noticeable where it's non-existent in Teamviewer

Please uplift API to allow Un-bundle and Un-merge actions

Trying to tie our logs into a SEIM so we can automate some reporting on connections. 
In the Logs I can see the hostnames used to initiate sessions but not what they connected to. It's always name=(hostname of initiator),  host=<none>, and either guest=<none> or guest=Guest.

It appears the machine info that is pulled from the support session is written into the log before the guest machine is processed. Thus the logged information is guest rather than a machine name. Having the option to set a delay would be great so we can see what actual machine is being connected to from the initiator.

Need the ability to sperate sys logs for customers so that they can remain compliant with requirements but also we are not sharing all of our customer information with one client.