Blog Post

FSLogix Blog
3 MIN READ

FSLogix version 2201 is now GA

Gonzalo_Reyna's avatar
Gonzalo_Reyna
Icon for Microsoft rankMicrosoft
Mar 30, 2022

Hello FSLogix nation,

 

I am pleased to announce that FSLogix version 2201 is now Generally Available. Our product group worked hard to address several issues and also to address an issue that, while it was not technically caused by FSLogix, it was affecting our customers, and I am talking about the Group Policy Access denied error. Here are all the fixes that are included in this new version:

 

  • Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service.
  • The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update.
  • Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server.
  • Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems.
  • FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value.
  • Over 30 accessibility related updates have been made to the FSLogix installer and App Rules Editor.
  • A Windows event now records when a machine locks a container disk with a message that looks like "This machine '[HOSTNAME]' is using [USERNAME]'s (SID=[USER SID]) profile disk. VHD(x): [FILENAME]."
  • Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was ignored in some cases.
  • Fixed an issue where active user session settings where not retained if the FSLogix service was restarted. This was causing some logoffs to fail.
  • Fixed an issue where FSLogix did not properly handle logoff events if Profile or ODFC containers were disabled during the session or per-user/per-group filters were applied mid-session that excluded the user from the feature. Now FSLogix logoff related events will always occur based off the FSLogix settings applied at login.
  • FSLogix will no longer attempt to reattach a container disk when the user session is locked.
  • Fixed an issue that caused the FSLogix service to crash when reattaching container disks.
  • Fixed a Cloud Cache issue that caused IO failures if the session host's storage block size was smaller than a cloud provider's block size. For optimal performance, we recommend the session host disk hosting the CCD proxy directory has a physical block size greater than or equal to the CCD storage provider with the largest block size.
  • Fixed a Cloud Cache issue where a timed out read request (network outage, storage outage, etc.) was not handled properly and would eventually fail.
  • Reduced the chance for a Cloud Cache container disk corruption if a provider is experiencing connection issues.
  • Resolved an issue where temporary rule files were not deleted if rule compilation failed.
  • Previously, the Application masking folder was only created for the user who ran the installer. With this update, the rules folder is created when the Rules editor is launched.
  • Resolved an interoperability issue with large OneDrive file downloads that was causing some operations to fail.
  • Fixed an issue where per-user and per-group settings did not apply if the Profile or ODFC container was not enabled for all users.
  • Resolved an issue where the Office container session configuration was not cleaned up if a profile fails to load.
  • Fixed an issue where HKCU App Masking rules leveraging wildcards would fail to apply.
  • Fixed an issue that caused some sessions configured with an ODFC container to fail to login.
  • Resolved an issue where the App Rules editor would crash if no assignments were configured.

 You can download this version now from here https://aka.ms/fslogix/download.

Published Mar 30, 2022
Version 1.0

19 Comments

  • vara93's avatar
    vara93
    Iron Contributor

    Gonzalo_Reyna Hi. 

     

     

    I confirm that the problem is not solved. Maybe you can write a temporary script to solve the problem ?

     

    SteveDMSFTLet me know how you are doing in solving this problem. Please do not ignore it. We look forward to hearing from you.

  • vara93's avatar
    vara93
    Iron Contributor

    Gonzalo_Reyna thanks!

     

    I will update FSLogix and test it when the next Windows Server 2019 update comes out. Then I will let you know.

  • vara93 you might be facing a particular scenario and further troubleshooting for your scenario will be required. We will need to basically look at the open handle requests to the files under local_ folder and based on the failed delete operations done during the logoff, determine why that file/folder was unable to be deleted. Please confirm that after installing GA version 2201 you are facing the issue and if that is the case, a support ticket must be open to work on it.

  • hi NickPanaccio. I am really sorry that I missed your question. The .metadata file it is a control file that we are using internally, it is expected to be created, so no concerns here.

  • NickPanaccio's avatar
    NickPanaccio
    Copper Contributor

    Gonzalo_Reyna: What's it going to take to get an answer from MS to my question from above? I have asked this in multiple MS forums, including MS support, and have received no reply. It should not take this much effort to get an answer from MS on what is likely a very simple question.

  • hi vara93

    1. and 3. These issues are solved by installing the latest updates for Windows. If after installing the latest updates you are still facing this problem, we will need to investigate your particular scenario and determine what is causing this. For the local_ folder not being deleted, generally speaking this is caused by FSLogix not able to delete a file under that folder because it is in use by another program. 

    2. I am not sure about that Microsoft statement that you are mentioning, but regarding FSLogix, RoamSearch must be disabled when running Windows Server 2019. You can find more details here: Roam the windows search database with Profile Container - FSLogix | Microsoft Docs

  • vara93's avatar
    vara93
    Iron Contributor

    Gonzalo_Reyna hi.

    1. In this version the problem of hanging local_ folders is fixed ?
    2. What is the recommendation to configure windows search service at this time for windows server 2019 ? I remember Microsoft wrote that this service in rds scenarios causes performance degradation.
    3. what about the black screen issue ?

  • NickPanaccio's avatar
    NickPanaccio
    Copper Contributor

    I've been running FSLogix in my W10 VDA for years, and after installing this build - with Cloud Cache not enabled via GPO - I noticed that a 'Profile_username.VHDX.metadata' file is now being created in the profile directory during the user's session. Is this normal and expected? I can't find anything in the documentation about this, and haven't received any feedback from MS in any other forum I've asked this question in.