Your comments

Note: For really old video cards, if CPU spikes for screenconnect when you're connected Blank screen will reduce CPU usage :)

Having a dedicated link that does auto OS detection and create a builder would be nice for Access items. Some workarounds till then:


Red link = Windows Access (msi installer is a backup in case .exe fails, don't have to use it as often)

It's a pre-built windows installer with use custom name: 1----%COMPUTERNAME%

Then I have a Session Group that is: Name LIKE '1----*'

New computer installs appear in there, I rename them once they're connected so it's always clean and I can tell new installs.

If you had lots of Mac/Linux clients you could probably do the same build extra installers for those OSs. I rarely do Access installs for Macs unless they're NOT Macbooks as the Screenconnect java guest client is a battery hog (at last check). Leave a Support download for them on their desktop and all they have to do is double-click it for reconnects.

Or....use the green link (Support).

Then I can create support session as Published with their name, tell them to click the arrow by their name (wait for them to get to the screenconnect page before you publish so there's a visual change on the screen as I'm talking with them). Once I'm in I can setup permanent Access if necessary. I use the "List Published Sessions" extension so if there's more than one published session it just shows up.

You'll need a website where you can post files for download...and I have to recreate the Built Access installer with each Screenconnect version so it installs latest.

HTH a workaround you can send the command: shutdown /s /f

using the Commands section. Use the Command Toolbox to remember the command for reuse

Check out other useful things you can do here:

Add useful commands yourself if you have some not listed :)

I think this may be an extension in chrome issue, as I see this happening frequently with other sites (using lastpass bar). See: