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!
Partner would like to limit ScreenConnect hosts to only be able to open a configurable number of sessions at a time, preferably with a way to have different users with different numbers of sessions that can be open (licenses used).
We are looking for when a SC session ends or we exit, that the Windows session also get logged off. There are too many times where a SC session disconnects, and the next day someone goes to log into the server, everything is left off where the previous tech was. We need this to be clear when a user logs into the system.
Please enable Azure Single-Sign-On by way of the Office 365 MyApps page: https://MyApps.Microsott.com
We are using your SAML login for IT Personnel. Our SAML is configured per your documentation by way of Azure App Registration and Azure Enterprise Applications which produces an icon on the Office 365 https://MyApps.Microsott.com page. However, when the user visits https://MyApps.Microsott.com and clicks the Connect Wise app icon the configuration produces, it lands the authenticated user on the login page with a malformed url like https://company.screenconnect.com/Login?ReturnUrl=%2fHost&Reason=5#Access/ which should be https://company.screenconnect.com/Login?ReturnUrl=%2fHost#Access/&Reason=5 and requires a second login. Within the browser session this does not repeat, rather occurs only on the first login.
We identified this problem in Service Ticket#12195842 but it was considered a feature request at that time.
add the ability to audit login failures/successes for logging in to the web interface
On both the "Start" and "General" tab for Access sessions, it displays the screenshot preview.
This seems redundant to have the same preview shown in two different locations, one tab apart from each other.
I would like to see an option to remove it from the General tab, as there is a lot of very useful information in this tab, but it is located further down the screen (scroll down) only because the screen preview occupies so much screen space being located at the top.
There is an article https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Knowledge_base/Restrict_or_remove_the_screenshot_preview#Globally_remove_the_screenshot_preview
to restrict this or one can also edit the web.config -> GuestScreenshotMaxPixelCount GuestScreenshotMaxScalePercent
and set either of those to 0, BUT both of these options remove it from BOTH the tabs.
My request is to have a configurable option to remove the screenshot preview from the "General" tab only and leave it on the "Info" tab.
I have reviewed the changes coming in the pending 2019 release and they look great. However one important usability tweak is glaringly obvious.
As described, one will now be able to get to Backstage by right
clicking on a computer, and selecting Join with Options from the
drop-down menu. This opens a dialog box where one can click the
Backstage radio button and then click Join Session. This is an unnecessarily complex sequence
of four clicks and intermediary mouse movements (right click, click
Join with Options, click radio button, click Join Sessions).
This can very easily and more naturally be done with one or two clicks. It could be done with one click by adding a [BS] button in the vast unused space on the host page, as below:
Or it could be two clicks (right click, click Backstage) by putting [Backstage] directly in the drop-down menu. You could still retain Join with Options for those who want to select Suspend My Input or other future options.
It is, in fact, easier to go to Backstage right now: double-click to open the session then immediately click [Backstage]. This of course creates the possibility of accidentally disturbing the user with mouse movement, but the sequence is ironically more direct than what you are proposing for direct access to Backstage.We go to Backstage 10+ times per day per technician, so having the four click sequence for no reason is going to be immediately irritating.
When you disconnect from a backstage session one of three things should happen:
1) The session is killed (ie the command prompt, powershell, and any other processes started)
2) The session is left running for X minutes
3) The session is left running indefinately
Right now it appears #3 is happening (or if there is a timeout it is a VERY long one). This causes issues because just having the command prompt open to a certain working directory locks that folder so it can't be removed until either the machine is rebooted or someone connects to backstage and changes directory or closes cmd. I'm sure there could be other issues eventually as well.
Ideally we'd be able to configure this as #1,2 or 3. It might make sense to ask when closing the session; maybe you started a process that you want to keep running.
Currently I get emails all the time like this: "[SC] Your guest to session 'TAM-VM' has connected (EOM)"
I am told that it's from the guest session starter ext.
I really like that ext and don't want to disable. Can you please add an option in the ext to be able to control if it sends out emails or not?
You can delete the trigger 'Notify when guest connects to unconnected support or meeting session' to eliminate these emails.
Customer support service by UserEcho