Forum Discussion
MicrosoftAnnouncing General Availability of FSLogix 2201 (2.9.8111.53415)
Today we are announcing the General Availability of FSLogix 2201. Updates include improvements to login and logoff times, cloud cache performance improvements, and 30+ accessibility updates.
Download Location
https://aka.ms/fslogix_download
Installation notes
This release can be installed over previous versions of FSLogix.
Installation Instructions: Install FSLogix Agent - FSLogix | Microsoft Docs
Changes
• 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]." This event is generated from the METADATA file created in the user's profile directory. This file can be ignored, but not deleted.
• 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.
Resources
FSLogix documentation: https://aka.ms/fslogix
Download Location: https://aka.ms/fslogix_download
- 1. You said that you are still working on the problem of local_username folders hanging, is this fixed here ?
2. What are the recommendations for windows search service setup at the moment for windows server 2019 ? I remember Microsoft wrote that this service in rds scenarios causes performance degradation.
3. what about the black screen problem ?- I hope the local folders issues is fixed we are performing nightly checks to reboot any servers as it causes issues later in the week, not a good option and is stopping us moving further forward with rollout
- We had big problems with the old version. (RDSH 2019 + FSLogix 2.9.7838.44263)
Last night we updated to the new version. (2.9.8111.53415) Its currently working fine.
The black screen problem is still there on Administrator account. (DOMAIN\Administrator)
Does anyone have a solution for the problem?We encountered the same Problems with AVD. After Update i get a Black Screen for one Administrator Account. Ohter Domain Admins work very well. Domain Users don´t have any Problems. All Admin Accounts are in one Group and this Group is placed in FSLogix Exclude Group.
- Been waiting for this update to fix some of the issues listed.
- Thanks, Steve for the update.
- Thanks for the update Steve, been waiting for this!
Will this be built in to the Enterprise for Virtual Desktops Images on the Marketplace? - Thanks for the update Steve! Have a great day!
SteveDMSFT Did they re-add the Enable Concurrent Sessions into the ADMX as this has been missing with newer versions and was brought to Microsoft's attention on numerous calls.
Is the asynchronous group policy processing fixed? I think a lot of people are holding back on upgrading until this is resolved.
This was fixed back in the preview version. RefCount
- Great news thanks for that.
- 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 would like Microsoft to actually confirm that this is the expected behavior. Otherwise, it simply looks like a bug.
- This is mostly the new naming convention of rw read/write fail back to read only configured in gpo. Hope this helps
- Did you fix Blue Screen bug (stop error: 3d) ?
Can anyone verify the refcount issue is resolved?
- This problem is solved.
