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!
Calling card applet
The majority of our clients have strict software restriction policies set via Group Policy in Windows that restrict applications from running the in Local Appdata folders.
The ScreenConnect one time client has a fairly long path and a different EXE file name every time it’s downloaded, which makes it very difficult to exempt from the SRP.
Unfortunately, a lot of our clients wouldn’t approve the access client as they don’t want us having unrestricted/unattended access to all of their machines without user interaction – or the ability for the user to disable.
Our suggestions - what Logmein currently does:
Get around this issue by having a calling card application – which can be installed through group policy. Essentially the user has an applet on their machine which they open and can enter the session code – which means they’re authorizing access and are aware we’re logging into their machine.
relate session item to the serial number of guest (prevent creating duplicates)
Hi everybody
We really love your product, but there is one really annoying thing.
Unfortunately every session is related to the installation of the MSI on the client (timestamp when it was installed or so).
That means, if you install and uninstall the ConnectWise Control client on one device for 5 times, you have 5 sessions in your control panel with the same name (duplicates).
We have over 1000 clients in our PROD environment, and reinstalling a device is a common thing.
So we have to pre-delete the specific session item first to not create any duplicates....
My suggestion: please relate this session item to the serial number of a client (this is unique!!).
If there is already an item with the same serial number, dont create any new one!
If there is no session item with this serial number, your'e good to go, a new item can be created.
Is there already something like that? How do you handle that?
Thanks in avance
Silas
Hey Silas,
Seems you are not selecting the Uninstall and End option. The End action removes the session from the list.
Windows AD Auth MFA Attribute
Would like to be able to choose something other than Description for MFA key. We use AD Description field for other purposes. Would be better as a custom attribute
Message window shows "Time Connected" incrementing *after* disconnecting
The Status section of the Message box shows "Time Connected:" and starts incrementing from 1 second upward. Later, when we disconnect after the work is done, that same Message window continues incrementing the "Time Connected" !
Our clients are concerned that if it's not us connected, that someone else is connected.
Not a good representation of the tool or our service.
Version:6.6.18120.6697
Need an Ask Then Deny for Screen Connect
We need to have an Ask Then Deny option for Screen Connect
Ability to select all guest machines with outdated client versions
Simply looking for the ability to select all guest machines with outdated client versions from the Access Screen. This will make it much simpler to run the push reinstall routine without having to scroll through and individually select the machines with outdated clients. If you could do "Outdated & Guest Connected" that would be ideal.
This is already available. I have been using since I first upgraded from 6.0 to 6.1 to locate outdated clients for upgrade.
Create a new Session Group and set the Session Filter to:
GuestClientVersion <> $SERVERVERSION AND GuestConnectedCount > 0
Auto-Default opening dual monitor instances
Good afternoon, Is there a feature or a setting to automatically have two windows open automatically sort of in a LMI sort of way? Almost all of our clients have multiple monitors and it would be nice to have them open in separate windows. Please let me know!
Customer support service by UserEcho