Forum Widgets
Latest Discussions
Citrix Profile Migrated to FsLogix - Disk Compaction fails - Ran out of time and bypassed operation
We have used David Otts script to migrate Citrix UPM profiles across to FsLogix and this is working great, with profiles now operating in a VHDx container. We have enabled Disk Compaction via FsLogix group policy, however this does not seem to run at all. To test, we had a profile that had 5GB of data, being able to expand to a maximum of 50GB. Copied 10Gb of files into the profile then deleted them and logged out, leaving the disk expanded at ~15GB. I Looking at logs, the error is Disk was not compacted, Reason: Ran out of time and bypassed remaining operation Am i missing something here? I couldn't find much on this error, but the log out process takes ~ 10 seconds and im unsure why it thinks it ran out of time. EDIT: we are using FsLogix v2.9.8884.27471
FSLogix - Search issues
Hello, Does anyone know what happens when an FSL server reboots when there are current connections using the containers? I'm beginning to suspect that this is what's causing search issues. I've been testing logging off vmware sessions while the server is online and it picks up the index as 'complete'. I'm noticing after the reboot, for anyone that had a session running, it resets the index back to 0 and has to rebuild it from scratch. I currently have a single windows server (ntfs) for ODFC (no profile) containers.
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?
FsLogix Implementation
Hi, We are currently in the midst of a home drive migration from an on-prem file server to OneDrive, we will be using Folder Redirection to redirect users Known Folders to OneDrive. This presents some challenges on shared computers such as our Library and Lab computers where students could login to any computer on a given day. Our intention was to implement FsLogix to ease some of these challenges - We've had to implement Profile disks due to one critical application not been compatible with the OneDrive Sync and so excluded from it. However, it's giving me some headaches at the moment. It works perfectly in a simple config with one user logging into one machine at a time, but I've been given some requirements which I'm struggling to make work. Firstly, users need to be able to login multiple concurrent sessions - in addition to physical desktops we have an RDS deployment, which is currently using UPD's but our intention was to ditch UPD's and also apply FsLogix Profiles to RDS, so our users maybe logged on to one or more physical desktops and then have an RDS Application open as well. I have been testing differencing disks with multiple physical computers. MS documentation suggests setting it to option 3 should allow you to connect concurrent sessions from different computers. However, after logging into the first computer, the second computer fails to connect the profile log shows: Attempting merge of diff disk \\path\RW.VHDX RW diff disk is open in another session RW exists, Taking RO role then I get: Status set to 1: Cannot load user's profile Further down I get: LoadProfile failed. Version: 2.9.8884.27471 User: User. SID: SID. SessionId: 2. FrxStatus: 5 (Access is denied.) Secondly, I've been given the requirement to seperate out Staff and Student Profile disks in to seperate folders - given we're applying a computer settings GPO I don't see how this is feasible, maybe on the desktops different reg keys via a user GPO depending on who's logging in. If anyone can advise on the above it would be appreciated. I would be interested to hear if anyone else has managed to configure fsLogix in a mixed Physical \ Virtual deployment. ThanksTroubleshooting FSLogix Profile Container Issues: Open File Handles on Azure File Share
FSLogix Profile Containers are widely used to manage user profiles in virtual desktop environments. However, issues can arise when open file handles on Azure file shares cause problems with profile containers. This article explores common issues related to open file handles and provides solutions to resolve them. Understanding Open File Handles Open file handles occur when a file is being accessed by a process and is not properly closed. In the context of FSLogix Profile Containers, this can happen if a user session is abruptly disconnected or does not sign out correctly. These open handles can prevent other sessions from accessing the profile container, leading to various issues. Common Issues Caused by Open File Handles: Profile Load Failures: Users may experience failures when loading their profiles due to locked files. Slow Performance: Open file handles can cause slow performance as the system struggles to manage locked resources. Data Corruption: In some cases, data corruption can occur if files are not properly closed. Identifying Open File Handles: To identify open file handles, you can use tools like qwinsta from Windows Terminal or Command Prompt, Task Manager, or Computer Management. 1. Using Qwinsta: Open Windows Terminal or Command Prompt. Run the command “qwinsta” to list all active sessions. Identify sessions that have not signed out correctly. 2. Using Task Manager: Open Task Manager and go to the Users tab. Check for any active sessions that should be closed. 3. Using Computer Management: Open Computer Management (compmgmt.msc). Navigate to Shared Folders > Open Files. Look for open files related to the user’s profile container and close them. Fixing Open File Handle Issues: Once you have identified open file handles, follow these steps to resolve the issues: 1. Log Out Users: Ensure that users have successfully signed out from all sessions using their profile container. 2. Close Open Files: In Computer Management, right-click on the open file and select “Close Open File.” 3. Restart Services: Restart any relevant services that may be holding onto open file handles. If everything goes well, the lock should be lifted, if not we can force it with CloudShell: Open Azure Cloudshell from the portaland select the Sub ID Select-AzSubscription -subscriptionid <Sub ID> #Create azure storage account context $Context = New-AzStorageContext -StorageAccountName <replacewithstorageaccountname> -StorageAccountKey <replace with storage key> #List handles Get-AzStorageFileHandle -ShareName "your-share-name" -Recursive -Context $Context Get-AzStorageFileHandle -Context $Context -ShareName "your-share-name" -Recursive | Sort-Object ClientIP,OpenTime #Close a specific handle, use the Close-AzStorageFileHandle cmdlet with the handle ID: Close-AzStorageFileHandle -ShareName "your-share-name" -HandleId "your-handle-id" #Close all handles Close-AzStorageFileHandle -ShareName "your-share-name" -CloseAll -Context $Context -Recursive -Verbose #Additionally, you can close all the file handles of the particular folder in the share: Close-AzStorageFileHandle -Context $Context -ShareName <replacewithsharename> -Path <'Sharedfolder/SIDuserfolder'> -Recursive -CloseAll Preventive Measures: To minimize the occurrence of open file handles, consider the following best practices: Proper Session Management: Ensure users properly sign out of their sessions to avoid leaving open file handles. Regular Monitoring: Regularly monitor open file handles and take proactive steps to close them. Regular Session Host Reboot: Regularly reboot session Host servers to reduce the possibility of open handles. Open file handles on Azure file shares can cause significant issues with FSLogix Profile Containers. By understanding the causes, identifying open handles, and implementing effective solutions, you can ensure a smoother and more reliable virtual desktop environment. Resources: Issues with SMB file share open handles - FSLogix | Microsoft Learn Troubleshoot Azure Files SMB connectivity and access issues - Azure | Microsoft Learn Get-AzStorageFileHandle (Az.Storage) | Microsoft Learn
How can I persist HKLM setting that holds application licensing?
Hello- I am very new to FSLogix as I have recently converted our office away from roaming profiles and folder redirection. Up until this point I had a program that some users get and when they registered it that registration persists when they log in and out of our Horizon non-persistent desktops. I reached out to the software vendor and they told me that the license key is held in "HKEY_LOCAL_MACHINE\SOFTWARE\VanDyke\SecureCRT\License" registry hive. I have a very simple FSLogix profile setup for users using GPOs to set default settings. Nothing else has been done. Since swapping to FSLogix this registry hive is not persisting. I am not sure at all how I can make this particular registry hive persist now that I am on FSLogix for profile? Sorry if this is a noob quesiton, I am googling as well, just not finding it yet. Thank you!Moving from AD to Entra - FSLogix folder name SID change
Hi All, We've been using FSLogix on AD joined AVD session hosts without any issues, but are now creating a new AVD environment with Entra joined session hosts. The last stumbling block I have is the FSLogix profiles. When a test user, or any user, logs on to one of the new Entra joined AVD session hosts, a new FSLogix profile is created instead of using their existing profile. The profile path is the same on the working AD joined session hosts and the new Entra joined session hosts. When the user logs in, it creates a new profile using %EntraSID_%Username%, instead of using the existing profile for that user located in %ADSID%_%Username%. That makes perfect sense as the SIDs are different but I'm hoping someone here can give me a pointer on how to get the existing profiles used instead of creating new ones. Thanks
Lateste FSLogix issues with VMware UEM Registry keys
Hello we are on the way to implement FSlogix. In the moment we also use VMware UEM for user predefined settings. When wa activate FSLogix we had teh problem that some registry keys want apply in the user session and then the predefined settings are missing. Did anyone else use FSLogix togehter with UEM and still have this issue? Thanks Regards Thorsten
