Announcing general availability of FSLogix 2210 hotfix 3!

Jason_Parker Also with this final version the autostart of the new teams is not being roamed in W10, pretty frustrating as we have lots of roaming users. Also if FSLogix disk is removed (because of issues) users get a error during signin on a machine where they have logged on before that teams_autostarter.exe cannot be found. Apparently the autostart setting is per computer and not being contained in FSLogix.

So this release still isn't sufficient to succesfully migrate to the new Teams!! Getting pretty scared now since the deadline is coming soon... PLEASE HELP!!

Can I skip the intervening version FSLogix 2210 hotfix 2 (2.9.8612.60056)?

Dear Jason_Parker thank you for this release.
I have installed FSLogix 2210 hotfix 1 (2.9.8440.42104)
How do I upgrade my computer to FSLogix 2210 hotfix 3 (2.9.8784.63912)?
As far as I can see from the installation instructions, I need to replace the Group Policy Template Files in the central store with the new one.
If I replace it, will my computer running with FSLogix 2210 hotfix 1 (2.9.8440.42104) work fine?

Anyone try the version released today yet?

EDIT: Hopefully they fix the Server 2019 issues soon, our users are getting frustrated.

Hello FSLogix nation!

Microsoft is pleased to announce the availability of FSLogix 2210 hotfix 3 Preview (2.9.8716.30241).

This is a PREVIEW version, and we recommend first running in your non-production environments to fully test and understand the new updates and fix.

We've updated several new articles in our documentation and updated the release notes page.

Release Notes:

• Update: When new Teams is detected, the AppX package is registered for the user during sign-in.
• Update: During user sign-out, Teams user data/cache located in %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache will be saved in the container.
• Fix: Resolved an issue where a virtual machine would reboot unexpectedly as a result of bug check (various stop codes) when a user's redirects were removed before sign-out

[UPDATE] January 9th, 2024:

First of all, I want to say "THANK YOU" to all of those who've been testing and validating this hotfix preview release. Based on the testing and feedback I'd like to report on the current status:

All:

• Potential anti-virus conflicts. Teams 2.1 paths have changed, and some anti-virus products have prevented the Teams executables from launching correctly.  Confirm with your vendor if any changes are needed to be compatible with Teams 2.1.

Windows 10 and 11 (Enterprise and Multi-session):

• Operating systems have the correct API(s) for proper discovery and registration for UWP / AppX packages.
• Profile only, Profile and ODFC, and ODFC only configurations working as intended.
• Preservation of Teams user data in %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache working as intended.

Windows Server 2022:

• [Unable to reproduce] Teams 2.1 fails to launch / start with a message, "msteams_autostarter.exe 'The parameter is incorrect'" (Looking for customers to help investigate and reproduce).

Windows Server 2019:

• [Confirmed] Missing API for UWP / AppX packages preventing discovery and registration (under investigation).
• [Unable to reproduce] Failure to instantiate storage folder C:\Users\%username%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache for package MSTeams_8wekyb3d8bbwe with Error Code: -2147024809 (Looking for customers to help investigate and reproduce).

Once we can confirm we've addressed the issue above, we will plan for an updated release for hotfix 3 (updated version).

Cheers,

Jason Parker, Sr. Program Manager for FSLogix

Windows Cloud Experiences at Microsoft