Screenconnect Waiting For Free Slot

Posted on by admin

Since updating ScreenConnect, a self-hosted remote support solution similar to LogMeIn and other services, to version 5.5 it has not wanted to reconnect support sessions after a reboot. The typical workflow for using the software is creating a support session, getting the client connected so that you can see their screen, and performing the requested fix. Often, in Windows world, that last step requires a reboot, whether it is installing or uninstalling software, making a registry change, or other common administrative tasks.

Screenconnect Pricing

Since updating ScreenConnect to version 5.5, you would reboot the computer but the client would not reconnect. From bug reports in the ScreenConnect support forums that I have read, it may have eventually reconnected after 5-10 minutes but neither the support nor the client want to wait around twiddling their thumbs for that time. Instead, it is easier for support to walk the client through joining another session in order to finish or verify the fix. This would happen even when verifying that the client was running elevated and in service mode. (If the client is not an administrator on the remote machine, use the “Send Ctrl+Alt+Del” key to elevate the client process to admin-level and a service.)

In order to improve compatibility with Windows 10, the ScreenConnect client’s service startup was changed from ‘Automatic’ to ‘Automatic (Delayed Start)’. The delayed start configuration is usually used for programs that don’t need to start immediately but need to start with the computer, so the delay allows startup/login to continue with less competition. The problem is that this Delayed start can introduce a 5-10 minute delay before the service starts up. The delay was introduced intentionally for improved Windows 10 compatibility in order to ensure .NET framework components are started before ScreenConnect attempts to run.

The solution was introduced with a fix from ScreenConnect but it only works on Windows 7 and Windows 8 computers. Windows 10 still experiences the delay. Login to ScreenConnect as an admin and under the Admin tab go to Extensions. Browse online extensions and install the ‘Change Client Service Start to Automatic (5.5+)’. This extension will have the service set to Automatic unless the operating system is Windows 10. As a result, you have much faster reconnection to your clients after a reboot. Hopefully, a more graceful fix is in the works with faster reconnects for Windows 10 as well.

The 'Waiting for free slot' message occurs when a guest attempts to connect to a session when another guest is already connected. Were the machines where this occurs by any chance created from an image? One troubleshooting option would be to stop the client service on one of the affected machines, and manually change the session id in the registry.

Change the client service to Automatic to decrease the time between reboot/restart of the guest. (Does not work on Windows 10). Disable Extension if upgrading machines to Windows 10 remotely*

Good afternoon,


Screenconnect Waiting For Free Slot

The 'Waiting for free slot' message occurs when a guest attempts to connect to a session when another guest is already connected. Were the machines where this occurs by any chance created from an image?


One troubleshooting option would be to stop the client service on one of the affected machines, and manually change the session id in the registry:


1) Stop the client service on the guest machine

Screenconnect Waiting For Free Slot Machines

2) Navigate to the following location in the registry, where the x's denote your server's public thumbprint: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesScreenConnect Client (xxxxxxxxxxxxxxxx)

3) Double click the ImagePath key; it's value should look something like this (truncated):


'C:Program Files (x86)ScreenConnect Client (xxxxxxxxxxxx)ScreenConnect.ClientService.exe' '?e=Access&y=Guest&h=localhost&p=8041&s=ba9400cb-9f42-427e-a379-464ad741a687...'


4) The value ba9400cb-9f42-427e-a379-464ad741a687 in the above string denotes the session id; modify this from it's current value to a different valid GUID, e.g. cd3500cb-9f42-427e-a379-464ad741a687


5) Start the client service on the guest machine -- you should see a new session on your host page with the new session id from step 4.


If you continue to experience this issue, it may be best to submit a ticket with our support team so that they can conduct more in-depth troubleshooting in you environment.


Screenconnect Waiting For Free Slots

Cheers,

Ben