failed to reconnect to your remote session

Tunneled connections send application streaming traffic through the Broker service. Applications launch with non-tunneled connections, but stay at starting/connecting with tunneled connections Log in to the servers and check the server CPU / disk utilization.

The hub server or application servers may be running anti virus scans. Application launches and synchornization is slow Disable roaming profiles and user profile disk. This is unecessary since Turbo will handle the application data caching and sychronization under the application settings. If using kerberos or ask for login mode, the application servers may attempt to load the user profile from the network using roaming profiles or user profile disks. The application server generate temporary windows profiles and should be fast to logon after the temporary profile has been created.

Applications take a long time to start during application server user profile logon To allow users to run multiple applications concurrently, ensure that this group policy setting is disabled. If this setting is disabled, users are allowed to make unlimited simultaneous remote connections by using Remote Desktop Services. If the user leaves the session in a disconnected state, the user automatically reconnects to that session at the next logon. If this setting is enabled, users who log on remotely by using Remote Desktop Services will be restricted to a single session (either active or disconnected) on that server. This behavior is determined by the Restrict Remote Desktop Services users to a single Remote Desktop Services session Group Policy setting on the Application Server that is running the applications. Users are unable to launch more than one application at a time Please contact See the Microsoft Documentation for more information.

If the application itself has transition delays between its windows, then a custom solution may be required. Remove any custom splash screens that may cause the timeout to happen, as Turbo will automatically detect the first shown window and delay the timeout as appropriate. Microsoft RemoteApp disconnects sessions after the initial window is shown then dismissed, and no subsequent windows are shown after a short timeout. Application immediately closes after initial splash screen in Cloud HTML5 or Cloud Windowed mode The following documentation describes commonly encountered issues when streaming a remote application using Run In Cloud (HTML5/Native) and how to resolve them.

Azure Active Directory with OpenID Connect.

Failed to reconnect to your remote session