--- # source: blog-content: posts/en/supportende-classic-teams-client-in-vdi.md # route: /en/insights/supportende-classic-teams-client-in-vdi/ title: End of support for the classic Teams client in VDI date: 2024-02-05 author: raphael-thommen locale: en summary: The classic Teams client in VDI reaches end of support on 30 June 2024. This guide covers installing the new client in a VDI. capabilities: [modern-workplace, virtualization] vendors: [omnissa, vmware] hero: /blog-assets/supportende-classic-teams-client-in-vdi/hero.webp migrated: 2026-08-24 translationReviewed: false draft: false --- > **The classic Teams in VDI will reach end of support on June 30th, 2024, after which users will not be able to use the classic Teams and will be asked to switch to new Teams app. Therefore, we recommend you update to new Teams today. [Source](https://techcommunity.microsoft.com/t5/microsoft-teams-blog/announcing-general-availability-of-the-new-microsoft-teams-app/ba-p/4000093)** Microsoft announced this on 5 December 2023, which gives companies barely half a year to switch from the old Teams client to the new one. More on the end-of-support dates for the classic Teams client: [https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability](https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability) So this guide covers installing the new Microsoft Teams client for VDI. Media optimisation has been on by default since Horizon 2212. For Horizon older than 2212, follow this [link](https://techzone.vmware.com/resource/microsoft-teams-optimization-vmware-horizon#horizon-agent-installation-and-configuration). The new Microsoft Teams app needs the same special handling for VDI and specific installation instructions to work with VMware Horizon and other VDI environments. You can run the old and the new Teams client side by side while users are in transition. For that, **both Teams clients** simply have to be installed on the master image **at the same time**. ![](/blog-assets/supportende-classic-teams-client-in-vdi/01.webp) If that button is not visible, the Teams update policy on the O365 tenant needs adjusting. [Allow the switch to the new Teams client](https://learn.microsoft.com/en-us/microsoftteams/new-teams-deploy-using-policies?tabs=teams-admin-center) ![](/blog-assets/supportende-classic-teams-client-in-vdi/02.webp) ## Installing the new Teams client in a VDI 1. [Download the .exe installer](https://go.microsoft.com/fwlink/?linkid=2243204&clcid=0x409) 2. Download the MSIX: - [MSIX x86](https://go.microsoft.com/fwlink/?linkid=2196060&clcid=0x409) - [MSIX x64](https://go.microsoft.com/fwlink/?linkid=2196106) - [ARM64](https://go.microsoft.com/fwlink/?linkid=2196207&clcid=0x409) 3. Open a CMD as administrator and run: - `.\teamsbootstrapper.exe -p -o "c:\path\to\teams.msix"` ![](/blog-assets/supportende-classic-teams-client-in-vdi/03.webp) *Note: it can also be installed without an offline installer, meaning without `-o "path/to/msix"`. Then the newest version is simply downloaded and installed.* ### Uninstalling In PowerShell, run: ``` ./teamsbootstrapper -x ``` ![](/blog-assets/supportende-classic-teams-client-in-vdi/04.webp) ### Disabling new Teams auto-update To stop new Teams updating itself, use the following registry key on the virtual machine. Only new Teams builds higher than 23306.3314.2555.9628 in VDI can handle this key. ```text Location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams Name: disableAutoUpdate Type: DWORD Value: 1 ``` ### Profile and cache location for the new Teams client All user settings and configuration are now stored in these locations, so they can be carried into DEM for example: For Teams to work properly, these folders and files have to be persisted. - `%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams` - `%localappdata%\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\app_switcher_settings.json` - `%localappdata%\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\tma_settings.json` **TeamsSharedConfig** holds the user configuration for switching the Teams app, including which should be the default, classic or new Teams, and for the Teams meeting add-in for Outlook. The "meeting-addin" folder under TeamsSharedConfig should not be persisted, as that can cause problems with the default meeting coordinates in the meeting templates inserted into Outlook. Excluding these paths reduces the size of the user cache and optimises a non-persistent setup further: - `\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs` - `\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs` - `\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage` Excluding the WebStorage folder, which is used for domains hosted inside Teams such as SharePoint or Viva Learning, saves considerable storage. It can also affect performance, because users lose the benefit of the cache. ### **Important** Customers using FSLogix have to install hotfix [2.9.8716.30241](https://learn.microsoft.com/en-us/fslogix/overview-release-notes#fslogix-2210-hotfix-3-preview-29871630241) for the new Teams client to integrate correctly in VDI. The hotfix fixes these problems: In non-persistent multi-user environments, new Teams could end up unregistered for some users after a new Teams update. - During a user logoff, the new Teams client user data and cache in %LocalAppData%\\Packages\\MSTeams\_8wekyb3d8bbwe\\LocalCache was **not saved into the FSLogix profile or ODFC containers.** *Note: customers using profile and ODFC containers, or only ODFC containers, still have to add the 'IncludeTeams' setting for the new Teams user data and cache to be kept.* ## Installing the old Teams client in a VDI 1. Download the Teams MSI package: 1. [32-bit version](https://teams.microsoft.com/downloads/desktopurl?env=production&plat=windows&managedInstaller=true&download=true) 2. [64-bit version](https://teams.microsoft.com/downloads/desktopurl?env=production&plat=windows&arch=x64&managedInstaller=true&download=true) 2. Install with these commands: - `reg add "HKLM\SOFTWARE\Microsoft\Teams" /v IsWVDEnvironment /t REG_DWORD /d 1 /f` - `msiexec /i "path_to_msi" /l*v "install_logfile_name" ALLUSERS=1`