Forum Discussion
Teams New Meeting Experience still not showing up
My team worked with Microsoft for a few weeks to isolate why many could not see the "new experience". Our issue was rooted in our need to centrally deploy the software and a step required many months ago ... we adjusted the MSI through Orca to treat the target workstation as a virtual machine and so the VDIModeEnabled was set to true. The new experience is not available on VDIs.
We isolated the VDI trigger to hklm\software\citrix and implemented a GPO to remove. The next step was to uninstall and reinstall Teams (the version that is not modified by Orca). We now have the new experience (set on by default).
To find if VDI was set, you need to open the Teams app and generate the debug files by holding CTRL + ALT + Shift + 1. Check the downloads folder for the debug files. The main one (largest size) will have VDIModeEnabled.
Stephan Swinford Congrats! Still a "no go" for me. I've even tried for a re-install of Teams as suggested by someone else. So frustrating!
My team worked with Microsoft for a few weeks to isolate why many could not see the "new experience". Our issue was rooted in our need to centrally deploy the software and a step required many months ago ... we adjusted the MSI through Orca to treat the target workstation as a virtual machine and so the VDIModeEnabled was set to true. The new experience is not available on VDIs.
We isolated the VDI trigger to hklm\software\citrix and implemented a GPO to remove. The next step was to uninstall and reinstall Teams (the version that is not modified by Orca). We now have the new experience (set on by default).
To find if VDI was set, you need to open the Teams app and generate the debug files by holding CTRL + ALT + Shift + 1. Check the downloads folder for the debug files. The main one (largest size) will have VDIModeEnabled.
Hello, i understand this is a few months old, but would you mind sharing how you isolated the VDI trigger? I am trying to get this working with VMware on virtual desktops.
If anyone has any experience getting the new meeting experience to show in a VMware environment any help would be greatly appreciated.
Norman Racine Hi Norman, we are facing the same issue but our teams are seperated, so we do not really know what the guys from software deployment do. But I followed your explanation but I cannot find any registry key on the Windows 10 (1809) machine which shows anything with "VDIMode" but the Teams diagnostic log shows me the part "currentConversationVersion": 2019052101,
"VDIModeEnabled": true," . So may I ask you to give me an hint where to search? Thank you a lot, MikeWhat you could do to bypass this issue is to add the option in you %appdata%\Microsoft\Teams\desktop-config.json and add this key "callingMWEnabledPreferenceKey" to the "appPreferenceSettings" and set it to true. This won't make the setting visible but it'll make it selected and you'll have access to the "New Meeting Experience"
"appPreferenceSettings": {"disableGpu": false,"openAtLogin": true,"openAsHidden": false,"runningOnClose": true,"registerAsIMProvider": true,"callingMWEnabledPreferenceKey": true}@Norman Racine Thanks Norman for the great feedback.
Vreezy I did the following:- Delete the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix
- Delete all files: %AppData%\Microsoft\Teams
- Restart workstation.
Worked for me.
Good afternoon GrahamBotes .
I am pleased that many are benefiting from my earlier post. I appreciate the acks.
I realize, however, that my post falls short in two areas:
1. I was able to communicate MY SPECIFIC SITUATION where VDI was interpreted by the Teams installer. Unfortunately, there are other situations that my post sheds no light on. It would be nice to obtain the rules that Microsoft utilizes in determining VDI mode - although Citrix seems to be the main one.
2. Recovering from an initial install of Teams under VDI mode was not explained well. At my sites, we deploy the Teams Machine-Wide Installer (msiexec /i "teams_windows_x64.msi" ALLUSERS=1). Users who had VDI mode enabled because of the Citrix registry entry are corrected using the following steps. The process that we use is not optimized but it is guaranteed to work:
. user logs off Teams and then closes the app when prompted to login
. user uninstalls Microsoft Teams
. delete folders in appdata\local\Microsoft: Teams, TeamsMeetingAddin, TeamsPresenceAddin
. delete folders in appdata\roaming: Microsoft Teams, \Microsoft\Teams
. Yes, I know that is overkill to delete all the above folders - but I wanted a guarantee.
. for the specific user, delete the registry key HKCU\Software\Microsoft\Office\Teams
. Logoff/on for the user and the Teams software will re-install for the user with New Experience on.
Hope this provided additional assistance.
Norman Racinethanks for this! pointed me in the right direction to the same issue.
we also had this reg key and VDIModeEnabed set to True. It turns out as we use Anixis for password policy enforcement it has added this key. Microsoft support have said they have spoken with Anixis and it is okay to remove, we are waiting confirmation ourselves. But I have removed it from my device, quit Teams, cleared the cached files in “%appdata%\Microsoft\teams\" only the files in that folder not any others and then opened Teams again, and it was all good - new experience here we come!
matttateReceived exactly the same advice from MS. When I deploy Anixis updates, I now have a secondary step to remove the specified Citrix registry key automatically. So far, no impact on the password change experience and after clearing the cache, Teams is finally updated for everybody. Good solution!
