Anyone have any ideas why Virtual Desktop would be showing as NOT SET here? This is our new Server 2025 environment, and the OUs these servers are in are being sync'd with Azure AD. I don't even know if this is an issue, just know that it's different than what we see with persistent W11 Citrix VMs.

Are they setup as multi-user, or 1 user per vm.

These are multi-session VDAs. I saw the same text on MS's site, but it doesn't actually go into detail what metadata it's looking for or where.

image.png

For good measure, in case anyone searches for this later, here are the possible values: https://docs.citrix.com/en-us/provisioning/2507-1-ltsr/configure/create-hybrid-joined-catalogs.html#create-a-master-target-device

Capture.PNG

wtf

Checking my 2025 with 2507 cu1, and I also see Not Set. Going through patches on in but will confirm once it restartrs.

Appreciate it. Sure starting to look like a bug, though I still don't know how much this information matters unless you had AAD registration issues like from the original W11 article.

It's under the On Demand Updates

Why have I never heard of this before?

It is relatively "new" it's where they are putting specific patches before they get rolled into a whole cumulative update.

Weird. I see no notes on this issue in any of those 4 updates, so I think I'm going to wait for CU2.

Is 2507 CU1 Update 4 cumulative? Aka does it include the fixes from Update 1-3?

I was told on Friday that none of the On Demand updates are cumulative.

wow, that means a lot of work I guess. So I have to read each CTX individually and decide how to solve each for itself.

You dealing with the same issue?

I'm here, because a customer informed me, that there are updates for the updates. And I was like: no, there aren't, there is only CU1. And that's when I discovered there are indeed 4 Updates for the Cumulative Updates, that I wasn't aware of. We are mostly hit by the Director shadowing issue, but to get up-to-date on the information, I just searched for "update 4" here in EUC Slack and found this topic. [...] I just read the whole topic. Sorry to interrupt the flow. You are right, this is a whole different topic. I only have one 2025 environment, yet. 2507 CU1, no further updates. This is what dsregcmd /status looks like:

Weird that yours is working as expected, but Jeff and I see different results - even with Update 4. Ah well, guess Citrix is trying to mimic Microsoft's consistently inconsistent flow state.

Finding it hard to see a reason to recommend server 2025 between this and the weird Schannel and other crypto errors everywhere.

We have no choice. Leadership wants S25, so that's what we have to roll with. Been fun, especially dealing with NetApp issues in S25 with CAFS and SMB.

We have two customers working on CVAD 2507 on WS2025 with no problems I'm aware of. Except the usual: With each new Windows Server release, the RDSH performance gets worse and the user density goes down.

We have found a number of issues, some resolved, some unresolved, but given that we haven't really hit UAT yet, I'm scared about what we'll find. Hell, even application compatibility and support I think is going to be a major roadblock (though this is on the vendors and not MS).

Once 2025 was tuned it has worked really well in all my deployments so far. But it had a lot more changes required than 2022 did.

Are you running storefront on it? Did you have to tweak anything there?

We're going from S16 to S25...

2016 to 2025 provides better feel and functionality for end users. I run everything on 2025.

@Jeff Riechers Is there any public information available about your 2025 tuning for RDSH?

So, back playing with this. Looks like MS is changing something with hybrid. Earlier builds like 2025 vanilla and 24H2 windows 11 are registering fine. Anything newer is failing needing some new Azure Kerberos settings. I am digging into this and will try and get something out there.

Interested to see what you find