What happens when users close down a published application running on XenApp but the session remains running with the Application not running Application State?
When publishing an application through XenApp we tell XenApp about the main applications executable file and where to find it for launch purposes. Applications however can start up numerous processes and it is when the main executable cannot close these extra processes at the time of application closure that this error occurs.
Using Citrix Director you can see the processes that are still lingering. To find out which one is causing the application not to properly close, end each user process one at a time. Once you end a process and the session logs off, you’ve found the culprit. In my case, it was the Authenticator.exe process stopping a session from ending.
To fix, you must include the affected process name in the LogoffCheckSysModules registry value. To do this, edit your XenApp servers or gold image and enter the process name within the LogoffCheckSysModules value which can be found under HKLM -> System -> CurrentControlSet -> Control -> Citrix -> wfshell -> TWI.
Now when you close the application, the Authenticator.exe process is ended and in turn the session ends.
Zax
July 27, 2017nice one.
Asif
October 4, 2018i tried but it’s not working. everytime i get error from director you are not authorised to perform this operation, please check director event log…
do you have any alernate solution to find our what not allowing to close the applicaiton.
George Spiers
October 8, 2018Log on to the VDA the affected user is on, and you can terminate the processes one by one until the session ends. Sounds like you have lack of permissions though.
Christian
November 14, 2018Hi Goerge ,
I would like to ask you how to install an application on RDHS 2012r2 with Citrix VDA agent installed?
Is necessary to use remote desktop installation through control panel?
Thanks
George Spiers
November 14, 2018Microsoft say you don’t need to place the server in install mode anymore, but you can do so if you wish:
change user /install
change user /execute