The plan becomes unresponsive and the following RemoteApp errors generate:
Trying to reconnect.
connecting to acloud
initiating remote connection
The RDP session is frozen and disconnected from the hosted server.
To close Orchestrate on the remote server successfully, please send a command to the server to shut the application down. This can be actioned within the remote session by actioning the following steps:
Press CTRL + ALT + END on the keyboard to bring up a blue screen (Legacy Hosted Users). Press CTRL + F1 for MyDesk Hosted Users.
On this screen, click Sign Out
This will correctly end the user session in the hosted cloud environment
Open and log into the Cloud session. This will provide a fresh new instance of Orchestrate.
Also, if you have multiple Orchestrate sessions running, close the additional sessions to only leave one session running. When you shut down your PC, if there is a option to 'update and restart', select this option to install important Windows updates.
If you are on the MyDesk (Workspace) hosted environment to close a stuck session, please complete the following steps:
Right-click the Citrix Workspace icon (blue circle with white lines) on the Windows taskbar
Select Connection Center
This will open a dialog box with a list of current connections and applications. Usually this would only be the one connection to MyDesk.
Locate and select the offending session.
Click Log Off
Click Yes to confirm your session should be logged off. This will force the session to end. Close the resulting Citrix Connection Center window.
Based on the current GPO configuration applied to the hosted servers, the session settings are as follows:-
Session Reliability timeout: 10 minutes (600 seconds). This allows a Citrix session to remain active for up to 10 minutes during a temporary network interruption, enabling the user to reconnect without losing their session.
Disconnected session limit: 3 hours. If a user disconnects from their session, the session will remain active on the server for up to 3 hours before it is terminated.
Idle session limit: 3 hours. Sessions that remain idle for more than 3 hours will be ended.
Based on the current policy configuration, the disconnected session timeout is set to 3 hours and the Session reliability timeout is set to 10 minutes. The current configuration of 3 hours is commonly implemented in Citrix environments to manage server resources efficiently and prevent abandoned sessions from consuming memory and CPU on the RDS servers. This also helps avoid stale sessions that may lock applications or files while still allowing users sufficient time to reconnect if their session disconnects unexpectedly.
If the above does not resolve the issue, please raise a new case online and reference the title of this article.
Citrix logs can assist us in determining the cause of the drop out connection (please attach them to the case):
Right-click Citrix app (blue circle with white curly lines) from the Windows taskbar and select Troubleshooting
Collect Logs