Welcome to the ConnectWise Control Feature Request Portal
If you do not have an account, click "Sign in/ Sign up" to get started.
- Search for an existing improvement or feature request before adding your own. This helps us prevent duplicate entries and track all suggestions.
- If you find a matching request, give it a thumbs up and throw in a comment.
- If you can't find a request for an item you need, create your own request. Provide as many details as you can, especially regarding possible use cases.
- No spam, advertising, or self-promotion.
- No offensive posts, links, or images.
- Only one request per post.
- Administrators have the ability to moderate the forums, including editing, deleting, and moving posts. Posts may be deleted for any reason, with or without notification.
Thank you for sharing your thoughts with us!
We would like to be notified of an offline machine that's been disconnected for an extended (Days) period of time. The current limitations of the trigger section only allows for a few minutes. This is not long enough to stop false reports due to computers rebooting or disconnecting for regular maintenance.
Currently we have unattended access on about 85 servers. But we see more and more that our technicians are getting personal logins to servers because of security reasons.
Is it possible to have a personal 'send to screen' button with credentials linked to the logged in user?
We would like to see this :).
When will Control support offer Duo's native interface as an option, rather than the version of Auth API that is used now? The current implementation gives off the impression that it is half-baked and not well thought out, not to mention insecure. It looks like users have been asking for this for more than 2 years. We really need for Connectwise to make this happen ASAP.
As a user, I want to be automatically logged in after I complete the last step of a mult-factor authentication process so that I have fewer steps and clicks before I am logged in.
Currently, after completing the final MFA step, CWC still sits at the login screen and we have to click the Login button to actually get into the system. It's a relatively small thing but it helps when we have a relatively short login timeout.
I need to ability to receive login and security alerts from control / automate hosted instances the same way that control hosted instances are sent out.
For example, when logging into name.hostedrmm.com no email alert is sent but when logging into name.screenconnect.com the following email is sent out.
Please include this functionality in all instances of control not just the one's hosted by screenconnect's cloud environment. We need all the security we can get nowadays.
When you connect to a server the screen resolution can be quite small and there is no way to change the default window size, having the ability to change or set a default connection resolution size or control it in the session would be very helpful, it is very frustrating when you are viewing a sever at 800x600 when you have 1920 x 1080 monitor.
If one of our employees wants to work from outside we give them access through ScreenConnect to their PC in the company. With WOL they are able to turn the PC on at any time they want.
A better way would be if ScreenConnect could initiate a new RDP session on a given terminal server where the user can logon with his credentials so that there is no need to use of an extra PC.
Oracle discontinued support for Java Web Start (JWS / JNLP) and removed it from official Java distributions starting with Java 11.
This means to use CW Control from a Linux (e.g., Ubuntu) workstation a significantly older version of Java, Java 8, must be installed and configured for use. This is not a recommended practice, especially since Oracle no longer provides free updates for Java 8. [I believe this impacts CW Control's Mac OS X client(s) as well, if they are JWS/JNLP also.]
OpenWebStart is an open source implementation of the WebStart and JNLP standards (JSR-56):
It is still in Beta, but has an aggressive schedule to have a release candidate in the coming months. Not all features will be supported initially:
So CW may wish to ensure that the CW Control Java app will run within the confines of what OpenWebStart will support initially and/or assist with the OpenWebStart open source project (e.g., financial sponsorship and/or developer contribution) to ensure OpenWebStart has all the features required by CW Control.
Customer support service by UserEcho