The FSLogix 2201 Public Preview is now available

[Steve Downs]

FSLogix 2201 Public Preview Update 1 has been published to address the issue outlined below. Please read details here.

FSLogix 2201 is now available in Public Preview.  This public preview is not recommended for production workloads. Please leverage your standard Microsoft support channels to report issues with this public preview release.

ISSUE IDENTIFIED IN THIS PUBLIC PREVIEW RELEASE:

We discovered an issue with the 2201 public preview that is impacting customers with session hosts configured to allow users to have more than one Windows session per user per host. In those situations, only that user's first session to a host will connect. Additional connections for that user to that host will fail to login.

Your environment is impacted by this bug if you have the "Restrict Remote Desktop Services users to a single Remote Desktop Services Session" group policy set to disabled or the HKLM:\Software\Policies\Microsoft\Windows NT\Terminal Services\fSingleSessionPerUser regkey value is set to 0.

We recommend impacted customers not install this public preview or revert back to the current generally available release. We are validating a fix for the issue and will publish an update to the public preview when it is available. Customers not impacted by this issue can continue validating this public preview release.

Preview Details

You can sign up here to participate in the Public Preview:

https://aka.ms/fslogix/preview

This release can be installed over all existing versions of FSLogix or you can perform a fresh install without a pre-existing FSLogix version.

Here's what's new in this release:

• 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 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 '[HOSTNAME]' is using [USERNAME]'s (SID=[USER SID]) profile disk. VHD(x): [FILENAME]."
• 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.

[#2]

@Stephanstoke 

Im not absolutely sure but i think we had the same problem until we redirected the %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache with the redirections.xml file.

[#3]

@stefanosevangelou Is there a public roadmap around FSLogix?

[#4]

@PdfPeet I'm also seeing stuck folders on the C:\Users folder. Can you please share your script ? Upload it to pastebin or github. Thanks!

[#5]

@Steve Downs 
Has anyone noticed strange behaviour with OneDrive since installing this? Some users are seeing duplicate OneDrive icons: one working normally and the other showing as not signed in.
The latter is unresponsive and cannot be signed in to
Users can ignore this however we've found that if a new user encounters this they're unable to log in to OneDrive at all

The issue does seem to stay on particular VMs when it manifests but as all of our VMs are built programmatically from a gold image we don't believe there's anything configured incorrectly for those VMs 

We found a workaround which involves closing onedrive and then deleting the folder:
'C:\Users\<user>\AppData\Local\Microsoft\OneDrive\Settings'. The sign-in window appears when onedrive is launched but if you close down this window you then get stuck again. 

When testing with non fslogix users the OneDrive sign in prompt works reliably

[#6]

Gentlemen, we have this issue with multiple customers, even after applying the known logoff and change to zero.
We have opted for the fix multiple times, but we still dont have a download link.
Can someone send me this version?

[#7]

Tell me more about the new Profile_nick.VHDX.metadata file in the profile folder.

[#8]

@maximilianlinseisen 

Hi, Thanks for the suggestion! Unfortunately this did not solve the problem.
I am currently working with Microsoft on this issue.
As soon as I know more I will announce it here.

Good day!

[#9]

Hi Alex,

We also experience this problem.
The workaround works fine for now. I have already opened a support case for this issue.
I'll mention your workaround to Microsoft, maybe it will help them.
Regards!

[#10]

Windows server 2019 with the February 15, 2022-KB5010427 (OS Build 17763.2628) Preview update. Many profiles become corrupted.

Also, many users can not enter, the profile is busy. The latest update breaks FSLogix

[#11]

Also in this version, many users have a black screen for 5 minutes, then the desktop loads.

Very very unstable version. 500 users.

[#12]

Does anyone know how to properly configure Windows Server 2019 search service + FSlogix ?

[#13]

Many users encounter a black screen when logging in. The only thing that helps is restarting the appreadiness service

What to do ?

Give at least some updated information. It takes you a very long time to fix critical problems !!!

[#14]

Thanks for your feedback. Have you opened a support ticket? That will help us collect logs and analyze the issue.

[#15]

Why don't you know about this problem, but your developer does? https://techcommunity.microsoft.com/t5/fslogix-blog/fslogix-2105-hf-01-2-9-7979-62170-released/bc-p/...

Can you work together ?

Steve Downs, your product has a lot of problems. That's a fact. You've been fixing critical problems for over a year now.

What's the problem?

I asked if there was any news, any progress in fixing the problems now ? You are ignoring.

Do you have developers who can take care of your product ? I don't want to wait another year.

I am also interested in another problem, why haven't you fixed the local_%username% folder freeze after logout?

I really hope you will answer me. FSLogix is the best solution, but I don't understand how you can spend years fixing critical problems. Do you think this is normal ?

[#16]

Thanks @vara93. Gonzalo is a support engineer, not a developer, and is responding to an issue not related to this public preview. We are aware of existing black screen issues and are working on them. However, you indicated a new issue in this public preview. If you're referring to the older issue and not something new then please open a support ticket.

[#17]

When is the next pre-release with a fix for the hanging local folder?

[#18]

How can i make a request to microsoft about problems with the FSlogix product or can i do it only through a paid subscription ?

[#19]

Hi -

Have filled out the form 4 times since Thursday.

Need to Get my hands on this to test - We are crippled with "The Group Policy Serviced failed the login" on Windows 10 Enterprise Multi Session.

AVD Deploymet is less than three months old, users completely rejecting it due to this Issue.

We are not seeing stuck or locked folders, but Ref Count is being set to unexepected Value (By Something) and Resetting it to 00 00 00 in regedit allows the user to log in.

What specifically is this public preview doing in regards to this point:

FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value.

Is FSlogix no longer caring if the value is no 00 00 00 and allowing access?

The form states I will receive a link via email within 24 hours and I have filled out the form 4 times since Thursday... Still no link.

Azure Support are reluctant to provide the file to me and say I need to sign a legal waiver.

How do I get the public preview update 1 to test my ref count woes?

Please advise,

B.

[#20]

When a user logs out, the Local_ folder remains.

In the logs I see:

Error removing directory: C:\Users\local_Makeev\AppData\Local\Microsoft (The folder is not empty.)

Event ID 26.

[#21]

@vara93 

We often have the same problem. I am currently testing the delproof tool with a daily reboot. 

 rof2: User Profile Deletion Tool • Helge Klein