Forum Discussion
PDostiyar
Jul 28, 2020Bronze Contributor
MS Teams New Meeting Experience auto-unchecked
I have noticed a strange behavior after turning on the Microsoft Teams new meeting experience, I checked it is working normally but when you sign out from MS Teams, the new meeting experience is unch...
- Sep 01, 2020
PDostiyar This behavior actually appears to be working as Microsoft intended. In this article, it states:
What happens to the new meeting experience if I sign out of Teams or switch to a different Teams org?
If you sign out or switch to a different Teams org (also known as a "tenant"), you'll have to turn on the new meeting experience again. Follow the instructions for turning it on in Settings and restarting Teams.Microsoft is supposed to be changing that option to be defaulted to On and you have to opt out in the near future which will then keep the box checked even after a sign out.
Filipus24
Aug 09, 2020Copper Contributor
So I investigated a little more and it looks like the configuration setting for this option is found in %APPDATA%\Microsoft\Teams\desktop-config.json. When enabling the New Meeting Experience setting, the appPreferenceSettings.callingMWEnabledPreferenceKey member is set to True.
When ending the task or when logging out of Teams, the setting remains set to true.
When you log back on (after a log out), the setting in the JSON config file does not change but if you go into Settings again, the option is unticked (even through the config still has the option set to True).
I am wondering if perhaps this is due to the fact that I run Teams on my personal machine (where I log into Windows using my personal account) while my Teams application is logged on using my professional account. Perhaps this throws off Teams' parsing of its config file.
PDostiyar
Aug 10, 2020Bronze Contributor
Well first of all Thanks Filipus24
you have gone far in this research and great outcome from the efforts you did in search and I am sure the profile on that machine being personal/local but not connected to Azure AD or local AD could be the root cause for this issue, As I did check mine on the corporate machine and all seems exactly what you mentioned.
you have nailed it, great job!
- Filipus24Aug 10, 2020Copper Contributor
PDostiyar : thanks for the praise but I am afraid it is undeserved. I ran a few additional tests on my corporate laptop, on which I log on using my corporate account, which is the same as Teams, and the same behavior occurs. Logging out of Teams and then back on changes the setting just like it does on my personal PC.
So I guess the answer for now is: if you want to quit Teams, don't log out, just kill the task.
We're a software company, and if my software behaved that way, I would rush out an update because it looks soooooo unprofessional, but in the meantime, hey, whatever works, right? 😕