Is than an estimated release date for the Mac M1 client?   The current client installs sucessfully, but never registers in the control panel.

There doesn't appear to be a way for SaaS/hosted users to harden web encryption security by disabling TLS 1.0 and 1.1 on the ConnectWise web portal. Both TLS 1.0 and 1.1 are no longer recommended for use due to security issues with the encryption of both methods.

Being able to disable TLS 1.0 and 1.1 allows us to protect our user base further. Please consider this security enhancement as having one encryption profile for all hosted clients also reduces the security for all if only one customer has a requirement to support Windows XP still. 

While investigating the use of Syslog on our cloud hosted instance of ConnectWise, it doesn't appear that any type of Syslog encryption is supported. This exposes sensitive audit logging that would traverse the public internet to reach a syslog ingestion point. 

Rsylsog, Syslog-ng, etc support TLS encrypted communication which ConnectWise could connect to if supported.

We'd really like to be able to either export or link all of the device information in Control with IT Glue.  We have device names, IP address and now we also have information such as model and serial number thanks to a PowerShell script - lots of great data about the devices.  Ideally we'd like to get this information out of Control and into IT Glue as a Configuration Item, simiilar to the way it integrates RMM systems to get device information.

It would be very useful to be proactively notified when a new version of ConnectWise Control is released via RSS Feed or via an email as opposed to having to periodically check the "Version Check" page in the Admin Status section.

Allow for the ConnectWise Control client (used on support agents' computers to remotely access client computers) to be updated without the agent having local administrator rights to their computer. Update it as a service.

Add the ability to forward specified ports from the host to the client.  For example 5433:localhost:5432 - let me connect from pgadmin to the postgres database on the remote (port 5433 gets forwarded to localhost:5432 on the remote.) 

You can do this with plink as "plink.exe -R 5433:localhost:5432 username@sshost.com", but you need an ssh host running and connectable from the internet.  (Plus additional key/password management hassles.)

Need the Ability to use the mouse with a true Trackpad Support now that Apple has released it. Also the same goes for bluetooth mice. They should sync with the mouse cursor and work as one unit. 

Would like to have one single web interface but with multiple servers managing the traffic between host & guest.

We have a world wide network and today a single instance of ScreenConnect in Europe. With this setup the China and US-guys do not want to use SC to help their clients in US or China since all traffic is routed via Europe.

So instead we would like to have one web interface where all clients can be found and then multiple servers routing the traffic.

Why one web?
A workstation should be able to "roam" from Europe to US and still be found in the same interface, and with 24x7 support that follows the sun our support-guys should only have to look in one web to find the client.

Add universal binary for Mac host and guest.