Not sure if there was an recent update to connectwise but copying a cell from excel file on host computer to paste into remote session excel file it tries to paste as picture and not the contents. Can use Clipboard Key Strokes to get the correct info but is an extra step and slower to paste information.

Is it possible to allow Accessibility and Screen Recording permissions using Intune? I can only automate allowing Accessibility permissions using a custom profile. It's to prevent this annoying message upon installation which requires local admin rights to allow it. Some users panic and think it's malware with the amount of popups it causes XD

In order to deploy macOS privacy preferences policy via MDM/DEP, the macOS app in Mojave that needs exceptions must be signed. Otherwise, a user has to create exceptions to allow remote control via ConnectWise Control, which isn't ideal. I don't want to have to sign your app to get the payload pushed out to create the exceptions from our management software. If you signed your apps like other developers, this would be much easier for all users, like those of the Addigy and JAMF communities. 

   Backstage and the administrative Command Prompt provide administrative level access to systems and endpoints that would otherwise require credentials and in most cases MFA in our environment. Currently access to ScreenConnect and thereby these two features, a threat-actor circumvents all of our hardening we have implemented with MFA and the requirement of long complex passwords.

   Ideally I would love to see Backstage require standard authentication to the system being accessed to be utilized. At the very least, the requirement of a system password in ScreenConnect that is only accessible to an Admin account to utilize Backstage and the Administrative Command Prompt would be a significant security enhancement and would make me sleep better at night.

THIS SHOULD ABSOLUTELY BE A FEATURE ALREADY.

EVERYONE UPVOTE PLEASE!!!!

When you minimize the CW chat window on a client PC you can never get it to show back up again. Even closing the chat window completely and then typing a new chat from the CW portal will not result in a chat window reappearing. The windows has been lost. This means that you must never minimize a chat window (or even click "show windows desktop" to minimize all windows) or you will lose your chat window until the client ScreenConnect agent service is restarted.

Support is aware of this issue to the extent that they removed the minimize button from the chat window in order to avoid the problem. But the issue remains, you're left juggling an open chat window even as it gets in the way of working on the client PC. And be sure to never use the show desktop option when a client PC has 30 windows open or you're lose the ability to chat with them.

It is terribly frustrating that this problem first occurred well over a year ago and it has still not been solved, and any inquiry to support about this problem it is met with instructions to make a feature request for a base level function that should be a given.

For Shame! This is not a feature. This is a bug fix. It used to work and it still should. Please fix this problem.

Currently there is no support for connecting to a headless endpoint (windows computer without a monitor plugged in). This is a big problem, as we are in the middle of moving from Bomgar to Control and now we realize that we can't support many of our client's servers or even Win10 computers who are headless. Even though the client has no monitor connected, we should still be able to see the Explorer GUI, other remote support apps certainly can do this. This is a HUGE feature-lack.

It would be beneficial to have audit and logging ability for changes made by the ScreenConnect administrator. Things such as adding or removing permissions, making changes to screenrecording permission, agent functionality changes, etc.

The VOIP quality in the meeting session type is so bad I can't put it in front of my company's customers. That kind of defeats the whole purpose of the session type. Quality should be on par with competitor products such as Webex or Teams. The audio quality sounds like a walkie-talkie or how TeamSpeak sounded 15-20 years ago. It needs attention. 

I would like to see an option to save recorded ScreenConnect sessions on the data partition rather than the C: Drive.  The way the installation is now, there's no option for this.  Not very efficient when you have to bloat a C: drive to save data that could easily be saved on the data drive.  The added upside is you don't have to worry about locking up a c: drive. 

I tried re-enabling it through the backend command line but it errors. Is there a way to add a powershell feature to the connectwise client? 
Either that or fix the backend CMD to stop throwing errors when I try to enable via command line without disturbing my users.