Welcome to the ConnectWise Control Feature Request Portal
If you do not have an account, click "Sign in/ Sign up" to get started.
Tips
- 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.
Rules
- 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!
Add toolbox access for techs on the guest client
Partners would like the ability to run toolbox items on machines with their guest client installed when they are on location with their customer.
Often times we are working with our clients and are physically at their machine that we have Screenconnect installed on. It would be nice if there was a way to get to the toolbox from the icon that is put in the task tray to download/run programs that we have in the toolbox. It would be nice if there was a configuration choice to ask for a username and password so the client could not normally get to the toolbox.
We have a lot of nice programs in our toolbox that help us troubleshoot and diagnose a machine and it would be great if a a client said, "Oh by the way. While you are here could you fix this?" we could just go to their machine and pull up the toolbox and get to the program that we needed.
Current behavior: Have to be logged into the host page or connected to the guest client.
AC:
1. Ability to right click the sys tray icon on the guest client, authenticate, and run toolbox items from the guest machine.
SC server MSI should abort upgrade if license check fails even without interactive GUI
Support Ticket #15223402
According to support when installing the MSI with /qn or similar switches for non-interactive / scripted upgrade, it's expected that if the license check fails the upgrade is installed anyway and the SC instance is left broken even though this condition was detected by the license check. It might be expected by support - but not by customers, and this exception is not documented where the license check is documented https://docs.connectwise.com/ConnectWise_Control_Documentation/ConnectWise_Control_release_notes/Upgrade_to_the_latest_version_of_ConnectWise_Control
The license check should abort an upgrade under all circumstances unless a command line parameter is passed to force the upgrade, or a non-default choice is made in the installer GUI to force the upgrade.
Just because the upgrade is running non-interactive is not a good reason to ignore the license check failure and force the upgrade which then leaves the instance unusable. This killed a customer instance this week, and was completely avoidable.
Include click count on support session page so we can tell if users are having difficulty downloading the file
Right now, when a user enters the code or clicks a link, we get a basic "user clicked..." message so you can tell if they made it that far. But, since a certain percentage of users seem to have difficulty locating and running the right file, it would be nice to see if they're clicking the link or entering the code over and over again. That would give support personnel on the phone with the client some additional insight on what they might be doing wrong so we can help guide them.
Use "Organization" to add hosts to Session Groups
I do not see a way to build a custom filter in the Session Group to filter based on the Organization for a system. Since we can create "builds" with the organization already defined, it would make adding them to session groups much smoother. Right now we have to create a Note with the customer name, and then use a filter to make sure those systems go into the right customers session group.
Thank you
Eric
Update has disabled use on Ipad IOS 9.
Recent update has disabled use on Ipad IOS 9. Support tried to get "Legacy" version to function, but this is also broe due to CSS. No advance warning was given that this would no longer work. Screen connect need to get the app working again on IOS 9.
What is all this about Screenconnect stopping suppor for IE 11
Im assuming this is bad joke
Some of the improvements the product team is making to ConnectWise Control requires support for CSS Grid and other enhancements that most modern browsers are supporting in their latest versions. In order for the team to keep delivering cutting edge features and intuitive experiences, we had to make the difficult trade off to deprecate certain browsers and versions that do not support the necessary technology.
This change does not affect your end users. Your customers and end users will still be able to access your Guest page and join a session with IE. This change only affects the Host page.
For more information about IE deprecation, please read the technical bulletin.
For more information about supported browsers, please read the Browser requirements documentation article.
I am going to close this topic as it's not a feature request, but if you have further questions about how this change affects you please send an email to the Product Management team at pm@screenconnect.com.
Thank you
Additional layer of protection required so users don't see each other's passwords!
Please add a layer of security protection so when a guest (or host) entering a password when logging in to another software or website when screen is being shared does NOT appear on other user's screen. Currently passwords can be seen and this is a major privacy/security issue.
Hi Laura,
RyanG is right, it is the application/website responsibility to do this.
Kill the Client Session Cookie after Disconnecting from Host
There needs to be an option to kill the session cookie when the client closes the connection to the host. We do not want the client to have the ability to connect back to the host without logging back into the web interface. Financial Institutions are now requiring 2-factor authentication for access and the current setup allows the client to login back in until the session cookie expires.
Customer support service by UserEcho
