How is everyone managing the migration to Teams 2....
# microsoft-365
l
How is everyone managing the migration to Teams 2.1 on non-persistent VDI? I originally thought it would make the most sense to have classic teams and 2.1 teams installed together on the gold image, and then let the UC team manage 'enabling' of the toggle for the users. Microsoft has a note on their Teams page that says the side by side method is only supported for persistent VDI. They have also said that the "new teams toggle" is tenant wide - so every user will see it and be able to do it. I envision thousands of users upgrading Teams on their NP VDI every day, nothing persisting and then they open tickets every day because it keeps resetting. The new teams, while a much improved app, has a really poor development team on it.
j
you using Citrix? this is the method we are using
image.png
l
You have both classic and new teams installed side by side on nonpersistent VDI? Their page says this:
j
no, only installed the appx using the bootstrapper method
that doesnt install the classic teams
l
image.png
t
Assigning the MSIX package through appventix...
j
youre doing this with non-persistent? per user install? ^
this looks pretty sweet! Are you creating your own msix packages for standard applications as well or just doing apps that cannot be installed on a gold image and only delivered via msix?
t
@Josh Farlow were doing mostly older Appv. But since the new Teams came as a MSIX, we decided to try it out. Non-persistent VDI's yes. Works pretty well.
j
nice. are you using any FSLogix app masking rules with it? we are using WEM today, but we are considering moving to a different way of presenting apps/shortcuts to users. we are not using any of the optimization features that WEM offers now either
t
Yes, FSLogix is part of our setup, and we do some appmasking on windows apps. But with Appventix, there is no need for appmasking, as you assign applications to users/groups.
n
Anyone get this to work on Server 2019 yet? We uninstalled Teams classic and then installed the new Teams using the MSIX and DISM command but it's not showing up on the Start Menu or launching for users. I see it in the Get-AppXPackage -AllUsers command.
a
Anyone run into issues where on their NP VDI they have modified it and removed all apps via something like the VMWare OS Optimization Tool? We have VDI pools like that, with none of the regular Win10 apps, and I think the lack of the "App Installer" app is causing new Teams to not properly register and run for our users.