Error removing Rule at logoff
Hello folks. during user logoff Fslogix is trying to remove some rules but get an exception [ERROR:80070490] Error removing Rule: C:\Users\username\AppData\Local\CrashDumps (Element not found.) As a result it removes "users profile" and "local_username" folder correctly with no issues, but sends Error to the logs. It's spamming the logs because it will put error one every excluded folder from redirection. We don't use any FSLogixAppsRuleEditor or something else, checked by ."\frx.exe list-rules -verbose" it returns - "No rules" The redections.xml looks like [...] <Exclude Copy="0">AppData\Local\CrashDumps</Exclude> [...] Is this an known issue ? Thinking it came around with 3.25.202.4223. Thx JensAVD with FSLogix - profiles not loading
Setup AVD with FSLogix several months back and profiles had been loading fine. About a month ago, profiles stopped loading and the logs show "Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced." This is in regards to connecting to the profile share path. If I manually try to go to that path, I receive the same error. The accounts do have a password, so it shouldn't be anything to do with a blank password. There are no sign-in time restrictions enforced on these accounts. What's left is a "policy restriction", which is kind of vague. Things I've tried: update to latest FSLogix verify permissions on profile storage enabled these in local policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options ‘Accounts: Limit local account use of blank passwords to console logon only‘ = disabled Computer Configuration > Administrative Templates > System > Credentials Delegation ‘Restrict delegation of credentials to remote servers‘ = disabled I have a ticket open with MS support for 3 weeks now, but thus far they've been completely useless.
Old file server still present in registry on user profiles
We are running FSLogix 2.9.8884.27471 on Server 2022. Our domain controllers are all Server 2022. We just migrated to a new file server. The Citrix profiles are stored on a completely different server; we have not changed the Citrix profile file server. We only changed/migrated the general file server used for general file storage. After we powered off the old file server, Citrix users complained of "slowness" when using File Explorer. We discovered that there are a bunch of references to the old file server in each user's FSLogix profile registry. If we mount the FSLogix profile, when a user is logged out, and delete the references from a user's profile registry, the "slowness" issues with File Explorer, are resolved. The registry entries that seem to be present in each user's profile are located in the following: HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints 2 (there are a couple mount points still present for the old file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) When we delete the "Favorites" entries, we find that after a user logs in/out, the "Favorites" entry updates properly to the new file server path. We can also remedy the File Explorer "slowness" by simply powering on the old file server. Again, all of the sharing on the old file server has been disabled. So it seems like as long as a user can "ping" the old file server, then that's all FSLogix needs to ensure that File Explorer works. This issue does not occur on physical Windows computers/servers- only with with FSLogix profiles. Instead of either leaving on the old file server powered on, or manually editing the registry in each user's profile, is there a way to remove (or update) these registry entries that point to the old file server?New Teams not loading with FSLogix 2210 HF4, Horizon non-persistent VDI
Hi all, We've been testing the latest Teams 2.1 Bootstrapper on our non-persistent Horizon VDI machines but having issues once we bring FSLogix into the mix. We are able to deploy new Teams onto our base image and when using a local profile it launches and runs as expected from the shortcut in the Start Menu. Similarly on our physical PCs Classic Teams > New Teams upgrades without issue (we're not running FSLogix on physical machines... yet) When logging in with FSLogix enabled (frxtray shows version 2.9.8228.50276) the Teams shortcut is present, however clicking it produces a white progress bar and no further action. We have updated our Redirections.xml to one we found here https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/comment-page-1/ If we look at the properties of the Windows Store App for Teams it returns 16KB, which seems wrong? Looking in Event Viewer AppxPackaging log we see this error, can't find much online relating to it. App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/manifest/uap/windows10/7 is inapplicable, it will be ignored during manifest processing. I note from another thread that there's a GPO for ODFC called IncludeTeams that needs to be turned on to roam the new Teams cache etc. https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy HKEY_LOCAL_MACHINE\SOFTWARE\Policies\FSLogix\ODFC\IncludeTeams However we don't use ODFC as FSLogix is in single-profile mode as recommended here... https://learn.microsoft.com/en-us/fslogix/tutorial-configure-odfc-containers Using the ODFC container in a dual container configuration isn't necessary or recommended. So my question is: does anyone have new Teams 2.1 working with FSLogix HF4 and single container profile? is ODFC required for Teams 2.1 to operate? If so is there any definitive MS documentation to say this as it seems rather vague and support are not giving us any further information has anyone got a stable non-persistent VDI desktop working with Teams 2.1 and FSLogix in general? Any input much appreciated as it feels like we've hit a wall here at present. The MS documentation suggests Hotfix 4 is meant to be the supported configuration for Teams 2.x but struggling to find evidence of a working setup. As an aside the reason we're running FSLogix in the first place is in order for OneDrive client to be deployed onto our non-persistent VDI machines as Microsoft don't support Roaming Profiles for this (which is what we used for roaming user data previously)FSLogix FontSmoothing Issue
I'm running into an issue where I can't get the fontsmoothing option to stay on when running FSLogix. If I stop both FSLogix services on the golden image of the VM then it stays but once I turn the FSLogix services back on that setting is reverted back. Anyone else run into this issue or have a solution?How to fetch username or userEmail from userprofile details of FSLogix
Hi I am trying to fetch several details from FSLogix userprofile like disk size usage , last accessed date. I need to get user details as well like Username or UserEmail. Below is the PS Snippet that I am using. $Profiles = Get-ChildItem -Recurse -Path $FileSharePath -Filter "*.VHDX" -ErrorAction Stop | ForEach-Object { [PSCustomObject]@{ UserGPN = ($_.Name -split '_')[1].Split('.')[0] FileShareName = ($_.FullName -split '\\')[3] FileName = $_.Name TotalSizeInGB = $DriveSizeGB ConsumedSizeInGB = [math]::Round($_.Length / 1GB, 2) FilePath = $_.FullName CreationTimeUtc = $_.CreationTimeUtc.ToString() LastAccessTimeUtc = $_.LastAccessTimeUtc.ToString() LastWriteTimeUtc = $_.LastWriteTimeUtc.ToString() } } How can I get that ? Kindly help! Thanks Hirdesh
Windows Server 2022 and FSLogix profile roaming problems
Hello! 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 Enabled 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>.file.core.windows.net\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 VHDX Any ideas how to solve it or what might have caused it?
