Shay Edri Posted May 30 Share Posted May 30 after installing new Teams version 2.1 on horizon environment Operating system - windows LTSC 2021 21H2 View version 8.10 2306 App Volume - 2309 4.12 1.Installation has been performed on the base image successfully and is working properly on the base image 2.We generate new snapshot and update pool in the view (by IC ) 3.When the user connects to the machine in the pool and attached the writable (bu appvol) we cannot see the new Teams installation 4.When we Disable the writable to this user (bu appvol)and reloing the new teams working well 5.If we crate new writable (bu appvol) to that user we can see the new teams but canot open it can someone share if anyone encountered this type of problem? thanks Shay Quote Link to comment Share on other sites More sharing options...
vRickE Posted May 30 Share Posted May 30 I have seen issues like this with writable and the new teams. AppVolumes 2312.2 is supposed to fix these issues. https://docs.omnissa.com/bundle/AppVolumesReleaseNotesV2312.2/page/AppVolumes-ReleaseNotes.html “new Microsoft Teams” application fails to launch when Profile-only or UIA+profile Writable Volume is attached to the agent computer. NOTE: When this issue occurs, no error message is displayed by the application. [AVA-23756] 2 Quote Link to comment Share on other sites More sharing options...
Shay Edri Posted May 30 Author Share Posted May 30 Great thank you @vRickE for the feedback i will check it and update Shay 1 Quote Link to comment Share on other sites More sharing options...
Employee Roch Norwa Posted June 2 Employee Share Posted June 2 @Shay Edri thanks for bringing this up and thatnks @vRickE for a good call! If you ever decide to package new Microsoft Teams client to use with App Volumes follow this KB article for step by step guide: https://knowledge.broadcom.com/external/article/321547/capturing-new-teams-as-a-package-in-app.html 1 Quote Link to comment Share on other sites More sharing options...
Shay Edri Posted June 3 Author Share Posted June 3 Hi , we did upgrade the APP Volume server and client to the new version 2312.2 and the new teams are available but only in with new writable and not with the existing version we have around 300 users and this will be very hard to create new writable for everyone any suggestion ? @vRickE @Roch Norwa Quote Link to comment Share on other sites More sharing options...
Employee Roch Norwa Posted June 3 Employee Share Posted June 3 @Shay Edricould you try adding below exclusions to an existing affected Writable Volume of some test user? exclude_registry=\REGISTRY\MACHINE\Software\Classes\PackagedCom exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teams.exe exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teamsupdate.exe Use this procedure to add exclusions: https://blogs.vmware.com/euc/2016/03/app-volumes-snapvol-cfg-writable-volume-customize-configure.html Quote Link to comment Share on other sites More sharing options...
tomwildt Posted July 9 Share Posted July 9 The broadcom links in this forum are broken. Can you please provide new links to those articles on documentation of new Teams 2.1 in App Volumes? 1 Quote Link to comment Share on other sites More sharing options...
AfshinLak Posted July 17 Share Posted July 17 Please can somebody provide new link to broken broadcom link? https://knowledge.broadcom.com/external/article/321547/capturing-new-teams-as-a-package-in-app.html Quote Link to comment Share on other sites More sharing options...
Employee Doug Arcidino Posted July 17 Employee Share Posted July 17 2 hours ago, AfshinLak said: Please can somebody provide new link to broken broadcom link? https://knowledge.broadcom.com/external/article/321547/capturing-new-teams-as-a-package-in-app.html The updated KB is still being created. I will post it here when available. 3 Quote Link to comment Share on other sites More sharing options...
AfshinLak Posted July 22 Share Posted July 22 https://kb.omnissa.com/s/article/6000003 1 Quote Link to comment Share on other sites More sharing options...
Mkoechel Posted August 29 Share Posted August 29 @Shay Edri Did you ever find a resolution to this? We are in a similar situation with Teams 2.0. The application has been installed on the base image, snap taken and deployed to our instant clone pools, but will fail to launch for any user that has an existing writable. If I delete that users writable, and they log into the same pool Teams launches as expected. I attempted to update the snapvol.cfg as @Roch Norwa suggested without success. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.