MicrosoftHi Jason_Parker ,
Thank you very much for looking into the issue I’m facing!
I have verified that the app_settings.json file is there and contains the settings you are referring to.
We have 2 scenario’s, and 2 different issues:
Issue 1: Teams Autostart not roaming / saved in FSLogix container
Scenario 1 (Statefull machines):
Test setup:
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:
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
Scenario (Statefull machines):
Test setup:
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
