FSLogix release 2201 Public Preview

This article is contributed. See the original author and article here.

Hello FSLogix nation!

Microsoft is pleased to announce the availability of the FSLogix Preview release 2201.

This is a PUBLIC PREVEW release

To access please go to this link and complete the following form: Public Preview request form

After submitting the form, a download link will be provided.

Changes:

• Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service.


• The Office file cache is now machine specific, and therefore cannot roam between session hosts, so it is excluded from FSLogix containers.


• FSLogix Search Indexing is now only available in versions of Windows Server that do not provide per-user search indexing. Per-user search indexes were introduced in Windows Server 2019 (version 1809). FSLogix search indexing is not available in Windows 10 or Windows 11.


• FSLogix now correctly handles cases where the Windows Profile SVC 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.


• 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 blocksize was smaller than a cloud provider’s. For optimal performance, we recommend the session host disk hosting the CCD proxy directoy has a physical block size greater than or equal to the CCD storage provider with the largest blocksize 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 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 if FSLogix loaded a container for the user.


• 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 there were no assignments configured.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.