Forum Widgets
Latest Discussions
Fslogix and outlook 58tm1 problems
Hello, I am in dire need of some help because i'm at my wit's end here. We have a few on prem windows 2022 RDS farms using fslogix and outlook. We are bashing our heads against the wall because of the dreaded 58tm1 problem. Every once in a while (5 times a day) a user will get a 58tm1 error while trying to open outlook, we usually fix the problem by deleting the Microsoft.AAD.BrokerPlugin which would fix things for a short while, because we've tried everything else out there, nothing works. Every possible settings combination, registry fixes etc... Newest fslogix versions (hello 25.09) do not fix anything but break everything (this entire branch has a nasty bug which would create temporary profiles and fill every storage space available). The users are growing tired, the support guy is considering goat herding as an alternative and the higher ups are veeeeeeeery displeased. Problem, we can't fix this, not in a timely fashion, not cleanly or easily. This seems to be an ongoing issue which has been present for years but got exacerbated lately with modern auth and subscription model shift for office. Is there some hope or do i have to start explaining to people how to type in their passwords? Because my next step would be to nuke everyone's aadbrokerplugin folder at the end of the day. Thank you for reading my rant :)
FSlogix Profile Disconnects
Hi, Just wondering has seen this issue with their AVD instances and FSlogix in regards to profile container disconnects. We have version 3.25.822.19044 and my theory is that computers that go into sleep mode (due to power timeouts) are not cleanly triggering the disconnect procedure for the container to be cleanly disconnected. We have noticed this by the users .VHDX.metadata file not deleting on their log off. It's also not releasing the Handles and Leases for their containers, making them sign in with a temp profile if they try again. We are just running a standard regedit profile setup based on this page, https://learn.microsoft.com/en-us/fslogix/concepts-configuration-examples Just seeing if anyone else has any fixes in place? Or is this a known issue. Thanks Josh.
fslogix printing does not work after changing profile from UPM to fslogix
I use Manuel Winkel's script <www.deyda.net> to convert UPM profiles to FSLogix profiles. When users log in again, some of them are unable to print. Deleting the printer, even from the registry, does not help. Adding new printers does not work. Restarting the printer queue does not work. If I delete the profile and create a new one, printing works. Does anyone have any ideas? Equipment: Windows 2019, Citrix 7 2203 CU6, and FSLogix 3.25.626.21064FSLogix 2.9.8884.27471 redirections.xml and remaining files in the redirected folders
Hi Together, I want to know how you handle the fact that when a new exclusion was added to the redirections.xml the old/orphan files remains in the user profile. We have thousands of profiles which cannot be cleaned manually. Why does FSlogix not offer and option to copy the content to the redirected folder or just delete this orphan files? best regards Bernd
Local Profiles not unloading on latest version of FSLogix
Good Afternoon, I've recently been troubleshooting an issue we have experienced running FSLogix 2210 hotfix 4 (2.9.8884.27471) with new teams on a Server 2019 image. The behaviour observed was that after launching Teams, users local_username profiles would not detach from the server, and when that same user logs back into that server, there is a new temporary profile created with the format local_username1. These local profiles could not be deleted due to containing a file in use by SYSTEM. After reading of the improvements with unloading local profiles with msix packages, I updated fslogix to the latest version FSLogix 25.02 (3.25.202.4223) After this upgrade, we are still experiencing the same issues, where local profiles do not detach and write back to the primary profile VHD. We then tested the latest version of FSLogix on an older image, that still had classic teams installed. The same behaviour was seen where the local profile stays attached and does not write back to the main profile. Are there any new configuration changes that I need to make in order to get this to work, or is anyone else experiencing this same issue?
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.
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 portal and 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
