Windows Server 2022 and FSLogix profile roaming problems

Copper Contributor



Recently I've been tasked with enabling profile roaming between two Windows Server 2022 hosts, which are added to the same collection. Both of them are hosting internal developed app.

After enabling fslogix on one of them, I've encountered some errors, users getting blocked from logging in.

Those are the errors users are getting when trying to log in into the host that uses FSlogix:

1) Failed to acquire mutex for user: EXAMPLE-USER

2) Failed to acquired cleanup session registry lock for user EXAMPLE-USER (SID=S-1-5-21-1715567821-2139871995-725345543-32785) (Elapsed time: 60000) (The wait operation timed out.)


User is from different domain that has Forest trust type set to Transitive. We have multiple domains accessing this VM and users from all of them are having the same problems when fslogix enabled on it. User has access to both VM and Azure Storage Account File share when profiles are being saved (both SMB and on Azure portal access)


FSLogix policy is set like this:


Policy Setting Comment
Delete local profile when FSLogix Profile should apply Enabled


Policy Setting Comment
Set Outlook cached mode on successful container attach Disabled
Size in MBs Enabled
Size in MBs 10000

Policy Setting Comment
VHD location Enabled
VHD location \\<example>\profiles

FSLogix/Profile Containers/Advancedhide

Policy Setting Comment
Keep local folder after user logs out Disabled
Locked VHD retry count Enabled
Locked VHD retry count 3

Policy Setting Comment
Locked VHD retry interval Enabled
Locked VHD retry interval 5

Policy Setting Comment
Prevent login with failure Enabled

Policy Setting Comment
Prevent login with temporary profile Enabled

Policy Setting Comment
Redirect temporary file folders to local computer Enabled
Redirect TEMP, TMP and INetCache to local drive

Policy Setting Comment
Remove Orphaned OST Files On Logoff Enabled

FSLogix/Profile Containers/Container and Directory Naminghide
Policy Setting Comment
Swap directory name components Enabled

Policy Setting Comment
Virtual disk type Enabled


Any ideas how to solve it or what might have caused it? 

0 Replies