This message was deleted.
# _generals
Slackbot
09/19/2023, 1:31 PMThis message was deleted.
r
Ray Davis
09/19/2023, 1:33 PMThe only thing that comes to mind is the log off system checker regkeys you could try.
https://support.citrix.com/article/CTX891671/graceful-logoff-from-a-published-application-renders-the-session-in-active-state
⤴️ 1
j
James Rankin
09/19/2023, 1:36 PMLogoffCheckSysModules is the answer to so many issues....
k
Kevin
09/19/2023, 1:36 PMThanks. The only problem with that is that it's mstsc.exe that still running. If I add that process to the logoffsysmodules reg setting it logs users off shortly after they launch RDP as a published app.
j
James Rankin
09/19/2023, 1:37 PMWhy should it do that? I thought the purpose of it was to kill any processes that were still running after a graceful logoff? I have the App-V client specified in my value and it doesn't kill the App-V client.....
💯 1
r
Ray Davis
09/19/2023, 1:38 PMYea I never heard of it doing that. It will kill the process under the users seasion or child processes for that session only. That’s what it’s supposed to do on logoff only.
k
Kevin
09/19/2023, 1:40 PMYou'd add other processes that are problematic and not the process that's related to the app your launching. I've tried adding mstsc.exe to that key, and it launches the app then shortly after it'll close the app and log you off.
j
James Rankin
09/19/2023, 1:40 PMTry launching mstsc.exe as a child process of something else then, cmd maybe?
r
Ray Davis
09/19/2023, 1:40 PMI have also seen this not work because AV had a lock on the process not allowing the system to do its job. Now I say anti virus software, but todays time it could be applocker type software, or any security software that’s doing this.
Ray Davis
09/19/2023, 1:43 PMTry creating a simple cmd file(or powershell) that calls mstsc.exe. Plublish the script file. Test it with you and see what you get. What James already said .
Ray Davis
09/19/2023, 1:44 PMOr create a logoff script that ends the mstsc.exe for a user session. Not sure if you use WEM but external task at logoff would do it there. Or just a simple GPO logoff action
Ray Davis
09/19/2023, 1:46 PMIf you go into studio and see the users seasion stuck , does it honor the log off action?
k
Kevin
09/19/2023, 1:47 PMIt seems to be the behavior of RDP that's changed since updating to 22H2. I'm not seeing any faults in the event log but mstsc.exe shouldn't still be running when the GUI is closed. The session isn't hung at log off, as the process is still running it doesn't start the log off process. It'll just sit there as active, then eventually disconnect. The session will remain on the worker with 'application not running' status.
Kevin
09/19/2023, 1:49 PMI've had a few processes in the past such as onedrive or sharepoint that need to be added to logoff syscheckmodule so have some experience with that and how it works. The issue here is some fault or setting in Windows I think that's caused this behaviour.
Kevin
09/19/2023, 1:51 PMI can log off these sessions from studio without any issue.
r
Ray Davis
09/19/2023, 1:52 PMSorry maybe I am not following you. I though you said here “This is problematic as we publish this as an app so it keeps sessions running after users close the RDP GUI.” So it does log of the user’s session from windows in time? I’m just trying to understand when you say the mstsc is still running under the users context, but you are also saying it’s logging them off but process is still showing under them?
k
Kevin
09/19/2023, 1:56 PMNo so the user launches RDP as a published app. They close the GUI after use, but mstsc.exe does not end, it keeps running. The user doesn't notice this has happened, but the session is still active/running. We have session timers so the session will eventually disconnect but keep running until around 18hours where policy is set to log off idle sessions.
r
Ray Davis
09/19/2023, 5:38 PMOkay. I would put in a logoff script to check is mstsc is running for the session id and if so end it upon the user logging off.
2 Views