This message was deleted.

The policy settings in Studio only apply to Desktops. You have to use MS GPO to disconnect and log off the published app session. MS GPO doesn't work that great either, we usually see a lot of sessions hanging on app processes, etc...

My problem is that the logoff works too well. The sessions gets logged off before I want it to. I suspect it's something in the image, so I'm creating a new image to test.

You can increase the disconnect time in the GPO, we have ours set to 2 hrs

Yes, we have ours set to that too, and it works as intended on our 2019 plattform, where our users can disconnect and it stays in a disconnected state for 2 hours before the session is logged off, on our 2022 plattform, with the samme idle/disconnect settings in gpo. So it seems like our 2022 image doesn't honor the set time limit for disconnected sessions. I suspect someone has optimized the image a bit to much.

It's interesting Tom, as I have seen this too on the odd occasion. The app closes itself and therefore the session logs off. I've never troubleshooted it further, as it happens rarely, and I suspect with only 1 app in our suite. I suspect the app gracefully closes, which triggers the logoff process, as this is what I see in the events. Do you get the same behaviour with published Notepad?

yes I do, I get the same behaviour no matter which app I run, even if I use a published desktop it will log off as soon as the session reliability timer is up. I've never seen that at other customers or in my lab, so I suspect there is something fishy with the golden image. Atleast it gives me a chance to verify that the task sequence to build a new image is correct, since I'm going to build a new image to verify

Interesting

To make this even more wierd, seems about 90 percent of our users does not have this issue, but for those who have the issue, it follows them no matter what endpoint or CWA version they use. I see that most of the users who experience this issue have their client ip showing as the endpoint ip, but for those who don't have this issue they are showing their public ip. All are connecting through netscaler, so not sure why some show public ip and some show private ip on client ip