Forum Discussion
New Teams Update Issues
Hi, Just getting to grips with the new Teams in AVD. Can see in the client that there is an update, select Update and Restart, it closes. Then it re-opens and shows that it still requires an upd...
I also confirmed this with Microsoft Support. I have collected logs and the support agent is currently reviewing these logs. I'll post an update when there's something new to report 🙂
This issue is listed under the known issues here:
https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#features-currently-not-available-and-known-issues-in-vdi-with-the-new-teams
New Teams fails to launch for users logging into non-persistent virtual desktops, or the app is not visible in the Start Menu.
Admins don't experience this issue - after installing new Teams on the golden image they can launch it successfully.
After sealing the golden image and deploying it at scale (with provisioning tools like Citrix MCS/PVS or VMware Instant-Clones), users log into the virtual machines and click on the new Teams icon, but aren't able to launch the app. The issue is caused by a failed registration of the MSIX package at the user level with different profile management software (FSLogix, Citrix CPM, Ivanti UEM, and so on), even though the staging of the package was successful (the OS stored the package’s contents on the disk in the %ProgramFiles%\WindowsApps directory). This issue can be confirmed by running Get-AppxPackage -name MsTeams for the affected users. Running this code will return an empty output.
NOTE
Microsoft is working on a solution and plan to remove these limitations soon.
https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#features-currently-not-available-and-known-issues-in-vdi-with-the-new-teams
New Teams fails to launch for users logging into non-persistent virtual desktops, or the app is not visible in the Start Menu.
Admins don't experience this issue - after installing new Teams on the golden image they can launch it successfully.
After sealing the golden image and deploying it at scale (with provisioning tools like Citrix MCS/PVS or VMware Instant-Clones), users log into the virtual machines and click on the new Teams icon, but aren't able to launch the app. The issue is caused by a failed registration of the MSIX package at the user level with different profile management software (FSLogix, Citrix CPM, Ivanti UEM, and so on), even though the staging of the package was successful (the OS stored the package’s contents on the disk in the %ProgramFiles%\WindowsApps directory). This issue can be confirmed by running Get-AppxPackage -name MsTeams for the affected users. Running this code will return an empty output.
NOTE
Microsoft is working on a solution and plan to remove these limitations soon.
- FSLOGIX 2210 hotfix4 coming soon. Check out the long list of teams fixes.
https://techcommunity.microsoft.com/t5/fslogix-blog/announcing-release-date-for-fslogix-2210-hotfix-4/ba-p/4129512
New Teams Changes
Update: Added functionality to repair missing Teams AppX folders in ODFC containers during the container creation process. (new container or container reset).
Update: Added a workaround where in some cases new Teams would fail to on-demand register during sign-in.
Update: Added roaming support for the new Teams meeting add-in when using the ODFC container.
Fix: Resolved an issue where FSLogix was unable to query provisioned AppX packages on Windows Server 2019.
Fix: Modified the sign-out process to solely erase the contents of "non-roamable" folders located in %LocalAppData%\Packages\* while preserving the parent folders. (all packages).
Fix: Resolved an issue where name cache entries in FltMgr (Filter Manager) would become polluted with non-normalized names.
Fix: Resolved an issue where New Teams may not have registered correctly when used with ODFC.
Fix: Resolved an issue where New Teams would fail to start, or the application would crash.