A user encountered a ‘logging off’ status in a Citrix VDA environment. After selecting ‘log off’ option, the process takes longer than usual and, if the user tries to reconnect the next day, they get a message. ControlUp can help with this situation, either setting an automated action to reboot the system for single sessions, or putting the machine into maintenance mode for multi-session hosts to prevent new connections. In case of one user assigned to the system, killing the processes one by one can help. Further information can be found on Citrix’s support article: https://support.citrix.com/article/CTX891671/graceful-logoff-from-a-published-application-renders-the-session-in-active-state.
Read the entire ‘How Controlup Can Help With Logging off Issues in Citrix VDA Environments’ thread below:
Hi,
I have an unusual question for you. Has anyone, in a Citrix VDA environment, encountered a ‘logging off’ status? In practice, it looks like a user randomly every now and then has a problem during the process of logging out of an active Citrix VDA session. By selecting the ‘log off’ option when finished, the process takes longer than usual (about 2 min max), after which an attempt the next day to reconnect remotely to the end station, ends with a message and can no longer be set up. Citrix services are enabled. In the Director, the session still has the status "Logging off", as if the process has not finished properly. Interestingly, in this situation, in order for the VDA environment to be able to connect to the target station again, a reboot of the station is required, otherwise the connection attempt ends with the message "Cannot start desktop Remote PC". This is a random situation and does not happen every time. The problem is so inconvenient that it is necessary to restart the station if the user wants to log in remotely to the computer again the next day. Can ControlUP help in this situation?
I don’t know if I’ve described it well at all…
Hello Mariusz, ControlUp can help with these types of situations. Is this a single session or multi-session VDA they are connecting? If it is a single session, then I would create a Trigger filtered to when the session is in the logging off state for an abnormally long amount of time and then set an automated action to reboot the system. Now, if this is a multi-user VDA, then obviously a reboot would not work, but what about changing that system to maintenance mode so that no new users can log back in? Would your user be able to log into new session on a different system?
That’s perhaps another question, I’m not entirely sure I understand the concept of ‘maintenance mode’ in a Citrix environment. Could you explain it to me a bit more ? These are single sessions, it looks more like the user has their own station and only logs on to it.
Thank you very much @member for the hints, they are very valuable!
For multi-session hosts, where one machine is hosing multiple users on it, you can tell the system to stop taking on new connections. So basically this would deny users the ability to reconnect to that system and the existing users would eventually log off and you can restart the system.
If the user is the only person on the system – as in they are assigned to it – then using the trigger option to restart the system would be your best option. Maybe set the time in the Logging Off state to be something along 4 or 5 minutes, so that you are sure their session was truly stuck.
Must likely u have a process that is getting hung during the logoff process. This is a common issue in Citrix environment. When a session is hung logging off RDP on to the box or check in Controlup what processes are running for that user and kill them one at a time, You will find the process with the right issue when the session logs off
Continue reading and comment on the thread ‘Help With Logging off Issues in Citrix VDA Environments using ControlUp’. Not a member? Join Here!
Categories: All Archives