We recognize many customers are under pressure to deploy new Teams in anticipation of the upcoming June 30, 2024 deprecation of classic Teams. We have released this version "out of band" of our expected integration in the Azure marketplace images in order to expedite the adoption process. This version will be pre-installed in the Azure marketplace images on March 12th, 2024. We had to slip the date for the marketplace images. We will plan a new blog post when HF4 nears GA.
What's new in FSLogix 2210 hotfix 3?
This hotfix release specifically enables compatibility and support for the new version of Microsoft Teams which became generally available on December 5th, 2023. Following our preview release of hotfix 3, we found some minor changes needed for the behavior when using profiles and ODFC or ODFC only. We have an outstanding bug for Windows Server 2019, and it continues to be one of our top priorities.
Most notable changes in hotfix 3 are in how we register the new Teams AppX package (by family name) and persisting the user data located in: %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache.
A handful of customers have seen unexpected reboots due a bugcheck (various stop codes) due to redirects getting cleaned up for active sessions. This was also included in the hotfix 3 release.
Jeff_Riechers I can apply Hotfix 3 without having to go through the steps. Thank you very much.
Jason_Parker Sorry for being so elementary. This error came up when I tried to apply one of the patches to a computer with hotfix 1. My user is an administrator and I would like to know what the problem is.
We installed Hotfix 3 on our AVD environment (windows 10 21h2 multi-session) and uninstalled the old Teams version. Unfortunately the new Teams does not work correctly. We also get the error message msteams_autostarter.exe wrong parameters. The new Teams 2.1 partially opens after five six minutes. After logging out and logging in again, the same problem usually recurs.
At the same time, we opened a Microsoft ticket. We hope for quick help.
You can patch directly to Hotfix 3 without stepping. Each release is a full install, so you can either start with this, or upgrade to this and you are fine.
You can install the new admx and adml. Any entries that are deprecated in the admx and adml show up as additional registry entries. So you may want to migrate those features before hand to registry entries, or edit the policy manually after you are upgraded to remove them from the xml file.
The reason I was asking about the single user version was because the hotfix says it is for Multi-Session and 2022 only. Will there be another version that supports 2019 and single-user session in the release notes? Or will the release notes be modified to include the other operating systems.
New Teams (bootstrapper install, offline installer with latest x64 AppX package)
FSLogix 2.9.8784.63912 (ODFC container only using CCDLocations (2 SMB Shares)), we start with user not having any VHDX
Physical Machines (statefull)
When I login on PC1 nothing starts. I launch New Teams and it opens successfully. I go to settings and enable "Auto-start Teams" option. Sign out and sign in and Teams automatically starts. File %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\app_settings.json is there and contains the correct settings. So far so good.
Now I move to another computer (PC2), where I do not have a local profile yet. I login on PC2 nothing starts. File %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\app_settings.json is there and contains the correct settings (as this is contained in the FSLogix ODFC container). So despite the file being there New Teams is not automaticly started.
Once I start New Teams manually, It will Auto Start at next logon on PC2.
So we are missing something that is not being roamed when moving to a different computer.
Scenario 2 (Stateless, pooled VDI desktops):
Test setup:
Windows 10 Enterprise (22H2 build 19045.4046), single session
New Teams (bootstrapper install, offline installer with latest x64 AppX package)
FSLogix 2.9.8784.63912 (ODFC container only using CCDLocations (2 SMB Shares)), we start with user not having any VHDX
Virtual Machine (stateless), user gets assigned a new clean desktop at each login
When I login on VDI nothing starts. I launch New Teams and it opens successfully. I go to settings and enable "Auto-start Teams" option. File %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\app_settings.json is there and contains the correct settings. So far so good.
Now I logout/login (and get a new clean VDI machine assigned), where I do not have a local profile yet, nothing starts. File %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\app_settings.json is there and contains the correct settings (as this is contained in the FSLogix ODFC container). So despite the file being there New Teams is not automaticly started.
So we are missing something that is not being roamed when getting a new clean VDI desktop assigned.
Do we need to roam some extra folders/registry keys with our profile solution, to make this work?
-----------------------------------
Issue 2: Error C:\Program Files\WindowsApps\MSTeams_24004.1307.2669.7070_x64__8wekyb…\msteams_autostarter.exe. Incorrect function
New Teams (bootstrapper install, offline installer with latest x64 AppX package)
FSLogix 2.9.8784.63912 (ODFC container only using CCDLocations (2 SMB Shares))
Physical Machines (statefull)
When a user gets a new FSLogix ODFC VHDX, for instance when support had to remove it because of some OST corruption or when they logon to a secondary machine (so a temporary new empty ODFC VHDX is created). They logon to a computer where they have configured Auto Start of New Teams before (for instance PC1 from the previous issue) , but then the get the error message described above. Only when they manually start the New Teams this message no longer appears and New Teams is Auto Starting when logout/login. In this case I would expect New Teams not to start automaticaly since it is not in the FSLogix container
-----------
In my opinion both issues are down to the Auto Starting of New Teams not being fully roamed with the FSLogix ODFC Container. Because if it was then with Issue 1 Auto Start would function if user roams to a different clean machine, also if ODFC Container is removed Teams would no longer try to Auto Start causing the Error screen
Our organization is configured to copy Group Policy Template Files to central store. We have a number of computers that are upgrading from FSLogix 2210 hotfix 1 (2.9.8440.42104) to FSLogix 2210 hotfix 3 (2.9.8784.63912) I am wondering if FSLogix 2210 hotfix 1 (2.9.8440.42104) will still work with the latest Group Policy Template Files in the configuration copied to central store. Sorry. The documentation was not clear. Also, do the upgrades need to be done in the same order as below? FSLogix 2210 hotfix 1 -> FSLogix 2210 hotfix 2 -> FSLogix 2210 hotfix 3 I especially want to know if there is any problem with FSLogix 2210 hotfix 1 -> FSLogix 2210 hotfix 3 since we have many computers.
Could this be something in your environment? Here is my testing setup:
Windows 10 Enterprise for Virtual Desktops (22H2 build 19045.3930)
Microsoft 365 MSO (Version 2401 Build 16.0.17231.20194) 64-bit
Classic Teams (machine-wide installer)
New Teams (bootstrapper install)
FSLogix 2.9.8784.63912 (Profile container only using VHDLocations)
AVD session as well as RDP session for testing
When my user signs in, nothing automatically starts except OneDrive. I launch new Teams and it opens successfully. I go to settings and enable "Auto-start Teams" option. Sign out and sign in and Teams automatically starts.
This should be stored in the users profile (%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\app_settings.json). If the user enables the settings you should see this in the json file:
Microsoft
