• UPM profile gets corrupt if users with same SAM Account name in different domains login to the same VDA.
• Issue is seen with 1912 LTSR CU5 and above and 2203 LTSR CU1 and above.
• USER1.DomainA.com logs on a VDA and  then User1.DomainB.com logs on the same VDA then the local profile of user1.Domain A account is referenced and corrupts NTUSER.DAT.
• The issue is seen both in RDP and ICA session with UPM in use. The user who logs in 2nd with the same SAM name gets the below error:

Below issue signature is seen in UPM logs for the 2nd Login:

2023-05-04;11:07:53.720;INFORMATION;DomainB;User1;8;9508;ProcessLogon: *Did not find a profile in the user store: \\Fileserver\citrix\profils\user1.DomainB\v6.*
2023-05-04;11:07:53.750;INFORMATION;DomainB;User1;8;9508;QueryLocalProfile: No profile directory found.
2023-05-04;11:07:53.750;INFORMATION;DomainB;User1;8;9508;QueryLocalProfile: Determined the name of a new profile directory: <C:\Users\User1>, directory exists.
2023-05-04;11:07:53.750;INFORMATION;DomainB;User1;8;9508;CreateLocalProfileFromTemplate: Starting to create a new local profile: <C:\Users\User1> from template <C:\Users\Default>...
2023-05-04;11:07:53.885;ERROR;DomainB;User1;8;9508*;Open registry file C:\Users\User1\NTUSER.DAT failed with nError:32*
2023-05-04;11:07:53.885;ERROR;DomainB;User1;8;9508;CRegistryHive::Load: Check signature of *<C:\Users\User1\NTUSER.DAT> to <USER_SID_tmp> failed. The hive file is probably corrupt. Message: Le processus ne p*eut pas accéder au fichier car ce fichier est utilisé par un autre processus.
2023-05-04;11:07:53.885;ERROR;DomainB;User1;8;9508;CRegistryHive::Load: RegLoadKey of <C:\Users\USER1\NTUSER.DAT> to <S-1-5-21-3081954379-1502722009-3557264116-2397> failed with: Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.

 

 

A Private fix has been created under CVADHELP-22965. Please reach out to  Citrix Technical Support to get the private fix if you come across this issue. A Public fix for this issue will be included in future releases.

---

Problem Cause

Known issue in the product.

UPM profile gets corrupt if users with same SAM Account name in different domains login to the same VDA. Issue is seen with 1912 LTSR CU5 and above and 2203 LTSR CU1 and above. USER1.DomainA.com logs on a VDA and  then User1.DomainB.com logs on the same VDA then the local profile of user1.Domain A account is referenced and corrupts NTUSER.DAT. The issue is seen both in RDP and ICA session with UPM in use.