Luke Gutbier
07/02/2026, 6:31 AMArthur
07/02/2026, 12:59 PMLuke Gutbier
07/02/2026, 1:56 PMArthur
07/02/2026, 2:06 PMmsinfo32, check “Virtualization-based Security services running”. If “Credential Guard” is listed, this is the most likely cause (enabled by default on Win11 22H2+ Enterprise). Disable via Device Guard GPO or registry HKLM\SYSTEM\CurrentControlSet\Control\Lsa > LsaCfgFlags = 0, then reboot.
2. VDA: credential delegation GPO: Computer Configuration > Administrative Templates > System > Credentials Delegation > “Remote host allows delegation of non-exportable credentials” = Enabled. Reboot the VDA. Verify with gpresult /h that the policy actually applied.
3. VDA: is ctxauth.dll loaded into lsass.exe On the VDA: tasklist /m ctxauth.dll. If no result, enable GPO: Computer Configuration > Administrative Templates > System > Local Security Authority > “Allow Custom SSPs and APs to be loaded into LSASS” = Enabled. Reboot. (CTX694923, relevant on Server 2025.)
4. Citrix policy In Studio/WEM: “Enhanced domain pass-through for single sign on” = Enabled and assigned to the correct Delivery Group. Confirm on the VDA via Citrix Group Policy Modeling or the VDA registry.
5. Client: line of sight to DC From the client: nltest /dsgetdc:yourdomain and klist get host/vda-name.domain. If Kerberos cannot obtain a ticket, session SSO will not work (VPN/firewall often blocks 88/tcp).Luke Gutbier
07/02/2026, 10:25 PMArthur
07/03/2026, 9:37 AM