Jump to content
  • 0
labgeekdave

ScreenConnect connects to another VDI

Question

4 answers to this question

Recommended Posts

  • 0

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ScreenConnect Client (6457306b9351cb65)\ImagePath contains your sessionGUID. I don't know if this is generated at the server or client side but that is how the SC server identifies the guest client.

 

If you want the SC button to work in labtech that same sessionGUID needs to be entered in the plugin_screenconnect_scinstalled table to link the computerid with the sessionguid.

Share this post


Link to post
Share on other sites
  • 0

So they are checking in LabTech as different agents but SC still sees it as one? I hope your using LT10 and the plugin - if so just do a reinstall of SC by right clicking the SC button on the new machines. Since SC is deployed and a GUID is assigned when the agent checks in, theres little you can do.

Share this post


Link to post
Share on other sites
  • 0

Just delete the &s= from the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ScreenConnect Client ()\ImagePath value and restart the ScreenConnect Client service. Without the &s= it will automatically derive a guid from the combination of the MachineGUID and the computer name.

 

https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Knowledge_base/Image_a_machine_with_an_installed_agent

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×