FsLogix 2201 Public Preview release

FsLogix 2201 Public Preview release

The FsLogix 2201 Public Preview release is now available for download from Microsoft. The change log is as follows:



- 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%MicrosoftOffice16.0OfficeFileCache is now machine specific and encrypted so we now 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 '' is using 's (SID=) profile disk. VHD(x): ."

- Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was sometimes ignored.

- 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 directory 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 rule editor would crash if there were no assignments configured.

Source



https://techcommunity.microsoft.com/t5/azure-virtual-desktop/the-fslogix-2201-public-preview-is-now-available/m-p/3086026


https://stefanos.cloud/blog/fslogix-2201-public-preview-release/

Comments

Post a Comment

Popular posts from this blog

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom
Read more