Step-by-Step Guide to Installing and Configuring the New Teams App in a Multi-Session Environment

1. Prerequisites:

Since you already have Classic Teams running, you may have already covered most of the prerequisites. However, I’ve still listed the necessary prerequisites that need to be in place for the new Teams.

1. Appropriate license for MS Teams. In my case I am using a Microsoft 365 Business Premium license.

2. Make sure you've opened the ports and IP addresses listed for Teams in Microsoft 365 URLs and IP address ranges - Microsoft 365 Enterprise | Microsoft Learn

3. Create a new VM on the existing latest version.

4. You can choose either a Windows 10 or 11 multi-session image, or a Windows 10 or 11 Enterprise image for the session hosts. The image I’ve been using is Windows 10 Multi-session 22H2

5. Install the latest version of the Microsoft Visual C++ Redistributable on your client device and session hosts from https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads

6. If using FSLogix, make sure it is up to date.

7. Update the version of webview2 on the VM. Download it from Microsoft Edge WebView2 | Microsoft Edge Developer

8. Turn on the Show Notification Banners setting in System > Notifications > Microsoft Teams to receive Teams Notifications.

9. Enable media optimization for Teams: (if not done already)

To enable media optimization for Teams run the following commands from an elevated PowerShell session:

New-Item -Path "HKLM:\SOFTWARE\Microsoft\Teams" -Force

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Teams" -Name IsWVDEnvironment -PropertyType DWORD -Value 1 -Force

2. Install the Remote Desktop WebRTC Redirector Service:

1. Download the .msi installer from https://aka.ms/msrdcwebrtcsvc/msi

2. Accept the terms and click on Install.

3. Click on Finish.

3. Uninstall existing Classic Teams App:

1. Uninstall the existing Classic Teams machine wide installer from the Control Panel.

4. Install the New Teams App:

1. Download the teamsbootstrapper.exe from https://go.microsoft.com/fwlink/?linkid=2243204&clcid=0x409

2. Download the MSIX from https://go.microsoft.com/fwlink/?linkid=2196106

3. Copy both the installers into a temp folder inside C:\

4. Open the Command Prompt as an Admin.

5. Change the directory to the temp folder where we have placed the installers.

6. Run .\teamsbootstrapper.exe -p -o "C:\temp\MSTeams-x64.msix"

7. You can verify by going to C:\Program Files\WindowsApps (Note: WindowsApps folder is hidden)

You would not find the New MS Teams in Control Panel.

5. Teams Meeting add-in:

TMA lets you schedule a Teams meeting from Outlook. As per the design, the Microsoft Teams add-in data in Outlook is stored in the AppData folder within each individual user's folder (as shown below), which may cause issues in a multi-session environment. To address this, we need the Teams Meeting add-in data to be stored in C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in.

To achieve this, the following steps need to be performed:

1. Go to C:\Program Files\WindowsApps. Inside this folder, navigate to the MSTeams folder and search for MicrosoftTeamsMeetingAddin.msi. Copy the full path as shown below:

"C:\Program Files\WindowsApps\MSTeams_24295.605.3225.8804_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi"

2. To get the binary version number of TMA run this command in PowerShell:

Get-AppLockerFileInformation -Path "C:\Program Files\WindowsApps\MSTeams_24295.605.3225.8804_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" | Select -ExpandProperty Publisher | select BinaryVersion

3. Open Command Prompt with elevated permission and run the below command:

msiexec.exe /i "C:\Program Files\WindowsApps\MSTeams_24295.605.3225.8804_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" ALLUSERS=1 /qn /norestart TARGETDIR="C:\Program Files (x86)\Microsoft\TeamsMeetingAdd-in\1.24.2203.0\"

Basically, in points 1 and 2, we were trying to find the complete path and the binary version number so that we can incorporate them in point 3

4. We can verify the installation by going to the Control Panel.

5. Now, it is pointing to the correct direction:

6. Publish Teams as a RemoteApp:

1. Select the appropriate Subscription, Resource Group and the Host pool

2. For Application group type, Remote App is selected as default.

3. Give a suitable name for Application group name.

4. Click Next.

5. Click on Add applications.

6. For Application source select File path.

7. For Application path give shell:appsFolder\MSTeams_8wekyb3d8bbwe!MSTeams

8. For Application identifier give a number.

9. Give a Display name

10. For require command line select No.

11. Click Next.

12. Give the icon path: C:\Program Files\WindowsApps\MSTeams_24295.605.3225.8804_x64__8wekyb3d8bbwe\ms-teams.exe

13. Icon Index as 0.

14. Click Next.

15. Click Add.

16. Click Next: Assignments.

17. Add appropriate users or groups.

18. Click Next: Workspace.

19. Select Yes for Register application group.

20. Click Next: Advanced.

21. Click Next: Tags

22. Click Create.

23. MS Teams is published successfully.

24. Teams is launched successfully.

7. Pro Tips:

1. Enabling device redirections isn't required when using Teams with media optimization. However to be on a safer side, set the following RDP properties to enable microphone and camera redirection:

audiocapturemode:i:1 enables audio capture from the local device and redirects audio applications in the remote session.

audiomode:i:0 plays audio on the local computer.

camerastoredirect:s:* redirects all cameras.