Using TSCON to move a session from RDP to the Console

Overview

If you log in to Launcher through Remote Desktop Protocol (RDP), Windows will disable the desktop when the session is disconnected. This behavior can cause the UWC and Engine-based connectors to fail.

Keeping an RDP session active 24 hours a day is usually impractical. Logging in directly through the VM console may also violate security policy.

Transfer the Session to the Console

To avoid these issues, transfer your active RDP session to the VM console before you disconnect.

Only one session can be active on the console at a time.

Run the following command from a Command Prompt (CMD) window:

CODE

TSCON %SESSIONNAME% /dest:console

Administrator Permissions

Some environments restrict regular users from running TSCON. If you have to Run as Administrator, the %SESSIONNAME% variable may not be available. In this case, use the query user to identify your session name.

Create a CMD file with the following content. Use double percent signs (%%) so the script works whether you run it as a standard user or as an administrator:

CODE

for /f "tokens=1,2,3 delims= " %%A in ('query user ^| find ">"') DO (set MYSESSION=%%B)
TSCON %MYSESSION% /dest:console

Create a Shortcut

Save the script as Disconnect.CMD on the desktop to make session transfers easier. When you are ready to disconnect from RDP, run Disconnect.CMD to move your Launcher session to the console.

For convenience, you can create a shortcut to Disconnect.CMD and enable Run as Administrator in the shortcut properties.