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!
NVIDIA NVS 310 drivers on Windows 10 x64 give blank screen when remotely connected
All NVIDIA NVS 310 drivers on Windows 10 x64 give blank screen when remotely connected. Have to switch to Microsoft Basic Display Adapter to get remote connection working again. Even tried installing the oldest driver from NVIDIA's website I could find (release in 2017) but problem still happens.
Sucks cause if the display drivers get automatically updated, i.e. by Windows updates, it reverts back to the NVIDIA drivers which then requires me to boot into Safe Mode and switch it back if I need to do any work on the computer. Would be nice if ConnectWise can roll out an actual fix for this instead of relying on using generic drivers but at least we have a workaround for the time being.
Block client users seeing the command window for agents they can access
Would prefer client limited accounts to their machines not to be able to see commands run through the run command window - can visibility for that be removed for limited access accounts?
Thanks,
There should be a hotkey to open the toolbar.
There should be a hotkey to open the toolbar.
Control computers' list appearance
The current layout in computers' list is: Name, CustomProperty1-8,Client version if outdated and User. If all custom properties are enabled, the computers' blocks in Access list become huge.
We find custom properties convenient to organise computers but the more you use the more crowdy the computers' list becomes. There is already the option to make specific custom properties invisible but this disables them completely. After making a custom property invisible you are not able to edit/add it to any computer.
This feature request focuses on controlling the appearance of the custom properties in the computers listinstead of one control point that disables their functionality completely.
Documentation/Instruction for SAML 2.0 Generic Connector request for Jumpcloud
Aloha,
I am having trouble configuring Connectwise Control SAML to be linked with jumpcloud generic SAML 2.0 connector. I am able to upload the screenconnect metadata to jumpcloud, setup cert. keys etc. When I attempt to complete configuration on the screenconnect side, I am unable to understand what is being requested.
IdentityProviderMetadataUrl - Attempted the following:
Provided jumplcoud IDP url - I receive the error -
Error processing external authentication return: SAML Configuration Error ( https://sso.jumpcloud.com/saml2/screenconnect): The 'link' start tag on line 1 position 335 does not match the end tag of 'head'. Line 1, position 395.
If I encode the (downloaded) jumpcloud metafile to base64 I receive an "object reference error."
I have not attempted to configure any of the other screen connect fields as I am unsure what information to give. Is there any documentation, or has anyone completed this integration before that could lend some help?
Creating a USB Recovery stick with ConnectWise Control
Hi all,
Quite some time ago there was a discussion on the original ScreenConnect forum regarding setting up a LiveCD/USB (WinPE or Linux Mint either would work) environment with ScreenConnect installed (so you can connect in obviously). There were several guide in this thread but they no longer seem to work or it wa not quite finished, is there any chance of getting this working?
Links below to previous topics and guides:
http://controlforum.connectwise.com/yaf_postsm7437_Script-for-LiveCD-Boot-Disk-Remote-Session.aspx
ScreenConnect Client Network Deployer
Would like the ability to specify a company when pushing SC agent so they populate correctly in the console. Right now you have to push the agent search for machines recently added then add them manually to the company groups. If this could happen on the front end when deploying the agent that would help out a ton.
Being able to log off of a thin client and back on as the admin. Need the shift key held during log off process.
When remotely supporting thin clients sometimes we need to log off and back on as the admin. To do this the "shift" key needs held during the log off process. Currently screenconnect will not read the shift key as being held during that process. This would be extremely helpful if this was a possibility.
Switch Terminal in Linux Headless
Ability to switch shell sessions using Ctrl+Alt+F1- Ctrl+Alt+F7 in linux sessions that are headless. Right now I've only tested it on redhat and it doesn't function for me.
ConnectWise Now with Dark Themes
The ConnectWise Now Dashboard does not display properly with dark themes.
EDIT: On-Prem v19.0.23665.7058
Customer support service by UserEcho