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.

It would be really nice to be able to get a notification on the desktop when a new message comes in so that the window doesn't have to be open or monitored closely all the time.

Currently the consent requirement is all-or-nothing when accessing ScreenConnect/Control via LabTech/Automate. We are required to keep this consent in place for accessing end user computers, but this is a huge roadblock for us when trying to access servers. If LabTech were ever able to resolve the known issues RE their RDP tunnels crashing constantly (still an open issue, 6 months now) this would not be such an issue as we would just use RDP. However we have much more faith in the ScreenConnect team to help us out with an integration enhancement that would allow us to apply this consent requirement based on other factors such as whether or not the guest machine is running a server OS, for instance. Right now we have to apply the consent requirement to the default All Sessions group which is what LabTech hits when it connects us to a machine.

Currently it's a bit difficult to clear out annotations on the screen, at least on the Mac client. If you've been drawing on the screen and want to clear it you have to go to the menus at the top of the screen, which can be very slow if you're having to draw and then clear repeatedly. It would be great if there was a clear screen shortcut key or a management panel like on Windows, including a button to manage on-screen annotations.

When participating in a remote session as the technician my username appears for messages and also in the participants list. I have found the setting under appearance which allows you to change the "GuestAnonymousName" but I think it would be great to be able to use their username for the remote session as it would be much more professional in the chat than "Guest" when they're a contract customer of your company.

we use two lang (HEB , ENG ) and when i connect to client they become unsynced lang .

we want 

auto sync my computer with the client lang

thanks 

Hello,

Everyone who needs access to the screenconnect/control web interface is granted that via a security group in AD. However, there's a generic local admin account that's still available as a back door in the event the AD accounts don't work. The switch from local accounts to AD accounts was made recently, and it has been requested to keep that one local account open for now.

Email OTP has been setup for that admin account, and a group of people get the OTP email when someone tries to use that account.

My question is, can the OTP email include information like the IP address and/or computer name of the machine that accessed the web interface? I know the idea is that only one person would receive the OTP email with the code, but we all need that email since it's a generic account for any of us to use. Having additional details in that OTP email would make identifying the OTP requester easier.

I'd like to see it available even as an add-on for cloud hosted access session only subscriptions.

We use access subscriptions vs. tech subscriptions to allow the end users (not just techs) to access their computers remotely.  So while we would save money by going to the premium bundle, we can't because of the SC licensing restrictions and as it stands now can't do the recordings either. :(

For auditing purpose we need to record all activities / Automatic screen record and save all the data to control server.