In order to upgrade Teams, you’ll need to re-install the newer version. Please Note that when using “Per-Machine”, automatic updates are disabled. This allows you to manage versions utilizing MSIs and GPOs. I use the “Per-Machine” for almost all VDI deployments. Non-persistent (Instant Clones) VDI requires Microsoft Teams to be installed “Per-Machine”, whereas persistent VDI can use both “Per-Machine” and “Per-User” for Teams.
We’re going to be installing Microsoft Teams using the “per-machine” method, where it’s installed in the Program Files of the OS, instead of the usual “per-user” install where it’s installed in the user “AppData” folder. Microsoft Specific Setup and Configuration of Microsoft Teams Optimizationįirst and foremost, do NOT bundle the Microsoft Teams install with your Microsoft 365 (Office 365) deployment, they should be installed separately.
Microsoft Teams MSI Installer (Available here: 64-Bit, 32-Bit).To get started, you’ll need the following: Please make sure to check out Microsoft’s documentation on “ Teams for Virtualized Desktop Infrastructure“, and VMware’s document “ Microsoft Teams Optimization with VMware Horizon” for more information. This guide will NOT provide instructions on deploying Microsoft Teams inside of non-persistent VDI or Instant Clones (stay tuned for a guide for that soon).
This guide will allow you to deploy Microsoft Teams Optimization for Manual Pools, Automated Pools, and Instant Clone Pools, for use with both persistent and non-persistent VDI. So you’re looking at deploying Microsoft Teams for your Horizon View VDI deployment.