FSLogix Troubleshooting guide (2024)

Have an issue you can't solve? I offer consulting engagements and can be reached here: consulting[а𝐭]amorales[․]org

This article will cover some common issues I have ran into, and steps on how to resolve them.

The guide should be followedin ordersince most of the advanced items are usually not the cause of a problem.

• ODFC = Office Data File Containers
  • This is there Office (Outlook, Teams, Licensing) data is stored
  • This can be used in conjunction with UPDs
• FSL Profiles
  • Replacement for UPDs
  • User profiles are stored here (Office data is stored in the ODFC)
  • Cannotbe used in conjunction with UPDs

The items below should be ignored when troubleshooting

• Local_ files under C:\Users
  • If FSLogix profiles are enabled, these folders can be ignored. They will be deleted the next time the user signs in.

    

Before troubleshooting any specific items you need to verify that all of the items below are in order.

• FSLogix Drive space on the file server
  • The drive should have at least 5-10 GB available

    

• Make sure that you can reach the sharewhilelogged in as the user experiencing the issue
  • Make sure that you can access the share from the RDS having the issue. Generally a DFS path is used.

    

    See Also

    frx command-line utility reference - FSLogixFSLogix Profile Container - Schritt für Schritt AnleitungFSLogix Container (Office/Profile) in Citrix Umgebungen – Deyda.net

• Make sure that the affected user hasfull control and Ownerover their FSLogix Folderandthe VHDX files.

  

• Make sure that the FSL VHDX is not out of space
  • Profiles:
  • Open "C:\Program Files\FSLogix\Apps\frxtray.exe"
  • Check the "Remaining Space" Field
  • Office Containers:
  • Navigate to the FSL disk of the user and check the size of the disk. If it is at 49.9, 19.9, or anything close to a whole number then it might be out of space.
  • Follow the steps on theAdding Space to FSLsection if it is out of space
• Make sure that the user is not being excluded from FSLogix
  • Check thelocalgroups on the RDS, and make sure that they line up with what you're expecting.
  • Generally "Everyone" should be part of the include lists, and the Exclude list should be empty*
    • *Sometimes the Exclude list will have a Domain group called APP_FSLogix_Exclude. Check that group in AD to make sure that it does not have any members.

      

• Is there a .old file on the user's FSL folder?
  • FSL will open the first VHDX that matches the string it's looking for. Adding .old at the end does not stop it from loading a VHDX.
  • Remove or significantly rename (Add OLD to the front of the file) any files that do not belong

    

• Make sure that the user has a 3 Month caching policy applied to them
• Make sure that there are no old OSTs under%localappdata%\Microsoft\Outlook
• Make sure that the user is not storing data on the root of their profile folder (C:\Users\Example)

FSLogix should not be set to roam the windows search on Server 2019. Make sure it is disabled in the settings below.

This section addresses the following issues:

• Black Screen at logon for 1-3 minutes
• Chrome Bookmarks missing
• Outlook cache missing
• Task bar buttons missing
• Profile is missing customizations (new profile)
• Office asking for activation (generally not an FSL issue, but still a symptom)
• All of the issues above persisting even after logging out and back in

The issues above are generally caused by the FSL VHDX file getting stuck somewhere. Follow the steps below to unlock it:

1. Log the user out of the RDS server
2. Go to the file server and open Computer manager (compmgmt.msc)
3. Click on Shared Folders/Open Files
4. Close all open files by the affected user

   

5. Log the user back in and the session should open quickly with all of the user's data
6. If that does not resolve the issue move to the next step

1. Check the user's FSL folder and inspect the size of their Profile_.VHDX file
2. Is it less than 450MB in size?
3. If so, the VHDX might have been corrupt and a new one was created.
4. Restore the VHDX file from backup
   1. Make sure that the file you are restoring is larger than the one you have now, otherwise this might not be the issue.
   2. If you restore from backup make sure that the permissions are corrected

If an FSL disk runs out of space there are different ways to address the issue

While the user is logged into the server:

1. Open disk manager
2. Add a drive letter to the user's VHDX

   

3. Use a tool likeWizTreeto scan the disk and remove any large files
4. Remove the dive letter you added!and have the user test again.
5. In some instances the user will need to log out and log back in

From the File Server while the user is logged out:

1. Make sure the user is logged out of the RDS

2. Double click on the user's VHDX file on the file server

3. Follow the steps on the previous section
4. Make sure to detach the disk when you are done!

   

Add Space to the VHDX:

This should be avoided. If the disk gets full it is usually because of an underlying issue such as a wrong caching policy or too many logs.

drive space

If space must be added then it can be done so with diskpart. Some guides:

• http://itproguru.com/expert/2012/11/how-to-expand-a-boot-to-vhd-disk-or-other-virtual-hard-drive-using-windows-tool-diskpart-windows-8-windows-2012-and-earlier-os/
• https://pmceldow.files.wordpress.com/2014/12/petermc_expandingavhd.pdf
• https://www.considerednormal.com/2014/09/resizing-vhd-files-the-easy-way/