The desktop clients can send the clipboard as keystrokes. This would be ideal in the iOS version too, as it is even harder to get a complex server login password right when you can't see them side by side. (I'd suggest ensuring a limit to the number of strokes too, just in case you copy War and Peace by mistake - or perhaps prompt to ask if you really mean to type 65 characters or something)

We recently started using the Toolbox to to deploy software and setting to Session Groups by setting up zip files to take advantage of the .SCAPP file extension.  We've discovered that if the SCAPP happens to be a larger file (more than a few MB) and it is sent to more than a few dozen Guests, then the server splits the bandwidth and resources across all of those devices at once.
This results in a very slow experience for all of the connected hosts, and cause the tool to take a much longer than expect time to download and eventually execute.  Since the download dialog shows up in the Windows UI, it's also best for it to finish as quickly as possible.

Basically  - we'd be looking for a way to put in a configurable hard limit of simultaneous Tool execution (like 10 or 20 once) and place the rest of the requests into a Queue, and have the server process the queue until all of the Guests are finished

The screenshots that are visible currently are to small and when a client is using multiple monitors it makes it hard to view what they are seeing on their screen.  The ability to make these screenshots larger for optimal viewing capability will help tremendously in this aspect.

It would be super useful if the Control Agent could be triggered to trigger the LTSVC.exe Automate Agent to perform its "Send Status" function, and likewise if Automate (when integrated with Control) could trigger the Control Agent to perform this to speed up the execution of commands (particularly in turning on FasTalk). It doesn't make sense why a functionality as this wouldn't be a good idea in environments where both Automate and Control exist (and have an integration connection in place) -- rather than waiting several minutes for FasTalk to turn on NOC technicians end up abandoning Automate and throwing their weight on Control since Control responds to commands immediately. With that, though this is the wrong place to mention this, it would also be great if we could have the ability to execute commands through the Control Agent from Automate (as an alternate way of executing commands).

The existing meeting windows aren't wide enough to identify which microphone to select.  The speakers window is the same.

Hi 

First of all we are really pleased using it

Would it be possible to store within the session database the serial, manufacturer and model information that you can now obtain with the other informations module.

Purpose is to link this information with our other CRM databases

those information do not need to be updated as long as the session is active

But as for now this product works "alone" in the information system

Thanks in advance.

Goal: To increase security of ConnectWise Control accounts used in integration scenarios, such as in the screenshot below where an administration account is used in a Automate/LabTech integration.

Possible Fixes: Enable MFA or OTP capabilities with integrations

or

Disable public login capabilities of specific accounts - for instance, our integration account has full access, however it has no multi-factor authentication like our actual user accounts do. This means that we have a high-level access account floating around that can be brute forced. If this account could be setup in a way in which it only communicates to a certain website or is not usable publicly, MFA/OTP would not be necessary.

Currently the folder transfer doesn't act like a operating system folder transfer, as a result hidden file contents don't transfer during a folder transfer. The folder transfer option should transfer all files in the folder.

We would like to change the color of the connected host notification balloon from grey

Other remote control software automatically pulls the current username into the username field, so the remote user just has to type their password.  I haven't come across a single user who actually knows their own username yet.  It's very tedious to have to get it myself, write it down and manually type it in.