Question for anyone who has dealt with Citrix MCS ...
# _general
n
Question for anyone who has dealt with Citrix MCS and the duplicate SID issue 👇 Scenario: We have Windows 11 persistent VDAs that were created with Citrix MCS on VMware (on-prem), and we’re moving them to Google Cloud Platform. After moving a test VDA to GCP, neither domain nor local admin logins work. The VDA logs LsaSrv Event ID 6167 (“partial mismatch in the machine ID”). It looks like the duplicate SID issue from the Aug/Sept 2025 Windows updates (KB5064081 / KB5065426). MCS clones share the master’s machine SID, and Windows 11 24H2+ now blocks Kerberos/NTLM between machines with the same SID. Refs: Citrix CTX695388 and Microsoft’s “Kerberos and NTLM authentication failures due to duplicate SIDs” Has anyone migrated MCS persistent VDAs to another platform (GCP, Azure, AWS) and run into this? How did you handle it? • Temporary override (KIR GPO or the FeatureManagement registry value)? • Sysprep/rebuild the persistent VDAs? • Rebuild users on new VDAs from a new master image? • Any word on Citrix’s MCS fix or timeline? Thanks!
just a heads up …found a temporary fix from here - woshub.com/duplicate-sid-windows#… - you can run this reg value change. However, i still want to see if anyone else has another fix….curious how everyone has gotten around this issue… “HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides” /v 1517186191 /t REG_DWORD /d 0 /f
g
@newbie1998 We are in a similar situation with some persistent VM’s deployed. It is not reasonable to expect a customer to rebuild over 700 persistent VM’s, so we went on the hunt. There is an easy button, but we aren’t sure of the total impact. Go to Manage Computer Certificates, locate Remote Desktop\Certificates. Remove the certificate named after the computers FQDN. Reboot and you should have RDP, Sharing, and Remote PS management working. I’m not sure if this will resolve your migration issue, but our customer is evaluating the use and impact. I hope this helps.