The Microsoft Remote Desktop client has this function. Force touch on iOS right clicks as well.

A partner asked us to provide support for their customers using our infrastructure while using their name. We would like to be able to offer multiple branding over one Control server.

for example:

main.support could bring our branded page for support

client1.support could bring a client branded page for the support we are provinding to them

client2.support could bring another branded page for the support we are provinding to them

etc..

There needs to be an option to allow some or all of the App.Config file setting to be used in the Roles settings. Currently if you want to remove the option to not allow someone to Blank Guess Monitor it's a global setting which financial institutions don't want to happen. On the other hand if your staff are working from home they do want the ability to blank their screens.

Ability to protect only one session group but allow a user to create new session groups and have access to them. I have contacted support regarding this and they suggested submitting a new feature request.

ESET has 2 Factor Control already ad we would like to see it integrated with ConnectWise Control

When you are connecting to a guest machine that has lower resolution than your guest and maximise/full screen the application, you will see black borders on both sides.

It would be nice to maximise the view and remove the black borders.

Example: https://imgur.com/a/bIjgV

For extra information, please refer to support case #9552598

Allow exceptions by session group for security. i.e. we want permissions to flow down to all groups except one we can define as an exception. Currently we need to add each group to a users security group if we want to create exception session groups.

Please add option 2 Factor to Cloud Account Admin via email address !

please let me know

GuestOperatingSystemName - looking for variable to pull Build number as well.  Weve had issues where windows 10 updates chages build numbers and we need to sort those out. 

We resell access to ConnectWise Control Access to some of our customers. When we setup accounts we force the user to change their password on first login. Many times we have received questions or experienced some frustration over the process of changing password for the following reasons:

• Lack of clarity of minimum password requirements, not identified or written anywhere (or at least not obviously and clearly)
  
• Even with the rule of "minimum 8 characters, 1 upper, 1 lower, 1 number, 1 symbol" it is possible to get an error message stating 'invalid password'. Sometimes the password does not change, and sometimes despite the error message the password changes (but only find out after we log out and log back in). This is extremely confusing for both our client users and our NOC technicians. I have personally experienced both scenarios where a complex password I try (a) does not take effect + I receive an error message stating 'invalid password' (which password is invalid? the old password or the new one?) and (b) I receive the error message stating 'invalid password' + my account password changed to the 'invalid password' password (the new one) and the only way to test this is to log out and log back in trying the new password for which I received an error message

Additionally, we have had users encounter 'invalid password' with 2FA setup. They enter their credentials and hit login, then enter their Google Authenticator code and hit submit only to receive an 'invalid password' error.

I apologize in advance as some of what I write and present here is lacking in concrete reproducible steps.