Multi-zone Citrix DaaS admins, engineers, and architects! In your experience, should this work? A have two zones. Each zone has a machine catalog with a copy of the same multi-session Server 2022 image. To keep it simple, I only have 1 VDA in each zone. I have one delivery group. The delivery group has one published desktop and contains machines from both zone's delivery group mentioned previously. Users are assigned to the delivery group's desktop and randomly connect to one zone or the other under normal circumstances. I have no zone preferences configured for the users. I am attempting to re-create outage scenarios we have experienced in the past by disconnecting the NIC on a VDA in one zone and watching for new sessions to connect to the other zone's VDAs. So far, this seems to work so long as I do not assign users to a zone with zone preference. What I am struggling with is stranded sessions. If I have a session on a VDA and disconnect the NIC, I am unable to reconnect to that session after reconnecting the NIC and waiting for the VDA to register. I can see in Citrix Monitor that Citrix DaaS is aware of a disconnected session on the VDA. As a user, if I look in the Activity Manager in the Workspace Service, it is unaware of a disconnected session. When I launch the desktop, I get a new session on the same server I have a disconnected session on. What gives here? I've tried setting the "EnforceUserPolicyEvaluationSuccess", "DisableGPCalculation", and "FastReconnect" reg values with no change in behavior. I've opened a couple of support cases about this, but so far have been unsuccessful in getting a satisfactory answer.

Seems like similiar issue that I see, even without zones. Sometimes users cannot reconnect to a disconnected session, sometime I can restart the Citrix Desktop Services to get the users back to the same server. Maybe try that, see if that updates Citrix DaaS.

I will try that. Like you, it’s not 100% of the time. This problem is driving me nuts. We lost internet for 15 minutes at a site this week and maybe 50% of the users reconnected to their session successfully. The others lost their work and started new sessions. Sometimes on the same server they were connected to. I use this same image in a traditional on-prem environment with a NetScaler gateway and do not experience the issue with it. I have my doubts it’s the image.

So are you comparing DaaS with Gateway As A Service with CVAD with NetScaler? Or are you comparing Daas with Gateway service against Daas with NetScaler?

First one. DaaS with Gateway Service vs CVAD with NetScaler.

Is it possible to test it doing DaaS with NetScaler?

@Daniel Viklund After experiencing an Internet outage today, I tried your suggestion for a user and it worked. Their disconnected session was hidden from Activity Manager until I restarted the Citrix Desktop Service on the server they were disconnected from. @Benjamin Crill I don't have a NetScaler to test this scenario with. 😞

Thought you said CVAD with netscaler above?

The project is to migrate away from CVAD + NetScaler to DaaS + Gateway Service. The NetScaler used for production CVAD is unavailable for me to use with this project.

@Matt Sliva yeah, its like the last version of VDA agent is not properly talking back to the citrix DaaS, been having this issue for months, that sometimes users that have a disconnected session, never gets it back, only gets a new one, they end up calling helpdesk, and they need to find where the "ghost" session is located, and kick that out.