There is such a utility available for Windows. Some of our customers feel more comfortable deciding when they want our techs to have access to their computers. A simple toggle that can be placed on the Mac desktop that they can double-click on and off for Macs would be nice.
on the unattended client icon, right-click menu on the tray-bar, add one option to enable/disable access to the computer.
Partner asks to add the ability for the guest to disconnect an unattended access client or mark themselves unavailable.
Hi, a number of our customers have said they would like the option to close an access session but currently this isn't possible.
I have this feature on my anti-Virus.
My colleagues should be administrator of their computers, some of them stop the service of remote control.
Thank you in Advance.
Currently there is no way for the Host user to disconnect the Client user after being connected unless they stop the ConnectWise service. There should be an option on the ConnectWiseControl that would give the user the ability to disconnect the client.
We are aware of the current capabilities for consent requests and policies. However, we have a client (financial institution) that would like to enable an end user to disconnect from an active ScreenConnect Control session through either the tray or communication window.
We have clients with the ConnectWise remote access agent installed that would like to have the option to disable the remote access feature.
Many of the machines we monitor are personal computers, and so it's not unreasonable for them to want an option to be able to block access.
How can this be enabled?
Kind Regards,
Christian Malcolm
I have ACCESS Session installed on my desktop, I have people in my office while I display a demo. I want to prevent anyone from using my machine for the next 30 - 60 minutes.
I would like the ability to suspend the client for a short period of time, Maybe you could allow the operator to choose a range between 5 - 360 minutes.
Once the Host/Client session complete, and I have disconnected from the client, can the client have a way to go to the notification area (lower right corner of the computer) and on the ConnectWiseConnect icon have an on/off switch. This would give the client the peace of mind to stop me from accessing their computer unless they want me to.
As it stands, users can only forcibly disconnect remote technicians on the single-incident session. However, our clients would like the ability to exist in the permanent/full installed version of the Connectwise Screen Connect client. This way in case something happens or an emergency, they feel comfortable they can kick off a technician even if they technician technically has "always on" access to the machine for a later session. This would still give peace of mind to my clients who expect that level of control on their end.
Give the Host user the ability to enable or disable the ConnectWise service thru the ConnectWiseControl icon in the system tray. Most financial institutions want the ability to turn this service on and off or be able to right click on the icon to verify the service status.
This should also allow the host user to do with without forcing the Host PC to require a login if the 'AccessLockMachineOnConnect' and 'AccessLockMachineOnDisconnect' App.Config option is checked.
Create a way for guests to control when they are available for a session with the unattended access client (such as an available/unavailable flag they can set in the client status window
Please let me respond with a scenario...
Assume that we have 20 ACCESS sessions configured
Does your proposed change allow me to disable 1 of the 20, during certain hours, without affecting the other 19?
Do you want this to be configured on the guest side or would you like to configure this in the web application to block your internal (host) users?
Yes, I believe this should be a feature if the client(host computer) not the admin.
This would give the client the ability to authorize connections during certain hours. By default, anytime, but the ability to limit would be available.
Ah, okay, so you want this to be a guest side feature. In that case, this is a duplicate and will be merged with https://control.product.connectwise.com/communities/1/topics/415-provide-simple-utility-for-a-guest-to-disable-and-re-enable-sc-java-and-net-client-locally
We are exploring the request now, and plan to get it on the roadmap soon :)
This should have been a programmed setting by now as this request is very old. Other competitors have it and many end users, for privacy (even if they approved unattended access) would like the option to easily right click the system tray or similar to enable/disable the app when needed.
This takes two seconds to program such a menu item that essentially runs a batch or script command built-into Windows to disable / enable the associated screenconnect service (or similar tactic, but service disable/enable is perhaps quickest).
If desired as an extra option, it could and should be made a setting in the backend admin settings to enable or disable the ability for an end user system to have this option available to be used ....just like some other settings are similarly allowed/disallowed to be utilized ....either account wise entirely or even granularly by filter/group like many other settings.
Either way, bare min we need to get the enable/disable system tray option for security/privacy reasons if for no other one.
Thx.
As you can see users are desperate to get rid of techs, as they often forget to disconnect.
I see such messages more often than not.
Please finally allow users (guest) to close/terminate any session.
thanks,
Stefan
Where does this stand CW? A simply RIGHT CLICK SYSTEM TRAY DISABLE/ENABLE is required for privacy and security -- period. Competitors have it. You don't. Pls fix.
As an optional tangent of this, as prior stated, you can have an admin app.config or wherever setting that allows us the admin per instance or per group (better if possible) to decide to allow this right click disable/enable to exist depending on our customer type/contract with them/desired privacy vs always-persistent tech support.
As prior also mentioned, the literal programmatic solution is a DISABLE = stop the CW service command and ENABLE = start the CW service command. That is literally 2 lines of code, whether dos command, powershell variant command, similar that triggers with a new menu item(s) you add to the right click menu of the LOCAL ON THE GUEST CLIENT system tray icon.
I may be wrong, but I believe your company is now the ONLY ONE that does not have this either as a right click system tray option or similar in the guest/customer side when they open up a remote control window or a admin side equivalent of it (not ideal as this should be GUEST/CLIENT SIDE, i.e. ON THE COMPUTER WHERE YOUR APP IS INSTALLED. ....you all may also call this "HOST" if memory serves, but it should be clear what we're talking about here or ask for clarity if not).
Thx.
Is there a way to set the ACCESS session up, so that it is available to use only during certain hours?
In other words, I want the session to be available between 8 AM and 1 Pm on specific days of the week.