Teams for Virtualized Desktop Infrastructure – Microsoft Teams | Microsoft Learn

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Microsoft Teams on Azure Virtual Desktop supports chat and collaboration. With media optimizations, it also supports calling and meeting functionality. With media optimization for Microsoft Teams, the Remote Desktop client handles audio and video locally for Teams calls and meetings. You can still use Microsoft Teams on Azure Virtual Desktop with other clients without optimized calling and meetings.

Teams chat and collaboration features are supported on all platforms. To redirect local devices in your remote session, check out Customize Remote Desktop Protocol properties for a host pool. This section will show you how to install the Teams desktop app on your Windows 10 or 11 Multi-session or Windows 10 or 11 Enterprise VM image.

From the start menu, run RegEdit as an administrator. Create the Teams key if it doesn’t already exist. You can deploy the Teams desktop app using a per-machine or per-user installation. Download the Teams MSI package that matches your environment. We recommend using the bit installer on a bit operating system. Teams won’t work properly with per-user installation on a non-persistent setup. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.

This optimization improves overall productivity across virtual desktops and apps, and enhances user experience when calling and meeting using Teams. The required media optimization components are part of the Horizon Agent and Horizon Client by default and there’s no need to install any additional plug-in to use the optimization feature for Teams.

To get the latest requirements and instructions on how to configure media optimization for Teams, see the Configuring Media Optimization for Microsoft Teams article on the VMware website. Deciding on which approach to use depends on whether you use a persistent or non-persistent setup and the associated functionality needs of your organization. For a dedicated persistent setup, both per-machine and per-user installation will work. However, for a non-persistent setup, Teams requires a per-machine installation in order to work efficiently.

See the Non-persistent setup section. With per-machine installation, automatic updates are disabled. This means that to update the Teams app, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates are enabled.

Keep the Teams desktop app in your VDI environment up to date. Teams desktop app versions with release dates that are more than 90 days older than the current version’s release date aren’t supported.

Unsupported Teams desktop app versions show a blocking page to users and request that they update their app. For most VDI deployments, we recommend you deploy Teams using per-machine installation. To update to the latest Teams version, start with the uninstall procedure followed by latest Teams version deployment.

For Teams AV optimization in VDI environments to work properly, the thin-client device must have access to the internet.

If internet access isn’t available at the thin-client device, optimization startup won’t be successful. This means that the user is in a non-optimized media state. In a dedicated persistent setup, users’ local operating system changes are retained after users log off. For persistent setup, Teams supports both per-user and per-machine installation. In a non-persistent setup, users’ local operating system changes are not retained after users log off.

Such setups are commonly shared multi-user sessions. VM configuration varies based on the number of users and available physical server resources. For a non-persistent setup, the Teams desktop app must be installed per-machine to the golden image.

This ensures an efficient launch of the Teams app during a user session. Using Teams in a non-persistent setup also requires a profile-caching manager for efficient Teams runtime data synchronization. Efficient data synchronization ensures that the appropriate user-specific information such as a user’s data, profile, or settings is cached during the user’s session.

Make sure data in these two folders are synced:. A roaming folder or, if you are using folder redirection, a caching manager is required to ensure that the Teams app has the runtime data and files required to run the application. This is necessary to mitigate network latency issues or network glitches, which would otherwise cause application errors and a slow experience due to unavailable data and files.

There are a variety of caching manager solutions available, such as FSLogix. Consult your caching manager provider for specific configuration instructions.

Excluding these items helps reduce the user caching size to further optimize your non-persistent setup. Before you deploy Teams through Microsoft Apps for enterprise, you must first uninstall any pre-existing Teams apps if they were deployed using per-machine installation. Teams through Microsoft Apps for enterprise is installed per-user. Teams is also being added to existing installations of Microsoft Apps for enterprise. Microsoft Apps for enterprise doesn’t support per-machine installations of Teams.

To use per-machine installation, you must exclude Teams from Microsoft Apps for enterprise. To learn more about Teams and Microsoft Apps for enterprise, see How to exclude Teams from new installations of Microsoft Apps for enterprise and Use Group Policy to control the installation of Teams.

At this point, the golden image setup is complete. This process adds a required registry key to the machine that lets the Teams installer know it is a VDI instance. Without it, the installer will error out, stating: “Installation has failed. Now, if you exit out of maximized mode, it will then auto rescale the screen share in Teams to only the single display.

So if someone is presenting, they can use this as a workaround, but will have to only use the app on the single display for the time being. By the way This is a complete nightmare for me. I just don’t get it. Hello Phoeunix1 ,. Thanks for coming back to me.

My end -users actually use this work-around to get their Teams shared. And to answer you question, I don’t have any mac users so far. So I can’t really help you on this one. Choose where you want to search below Search Search the Community. Search the community and support articles Microsoft Teams Teams for business Search Community member.

Is there a way to have only one screen shared in this configuration? Thanks for your help! Regards, Dom. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 0. Report abuse.

Details required :. Cancel Submit. Hello, I am Celso a member of the Microsoft community and a user like you. How can I help you today? Sorry for what happened! Please check the link below to check your configuration.

 
 

 

Microsoft teams in windows virtual desktop. Please wait while your request is being verified…

 
Teams in a virtualized environment supports chat and collaboration. And with the Azure Virtual Desktop, Citrix, and VMware platforms, calling. How to setup Microsoft Teams in Windows Virtual Desktop? · Step 1: Enable media optimization for Microsoft Teams · Step 2: Install the Teams WebSocket Service.

 
 

Microsoft Teams on Azure Virtual Desktop – Azure | Microsoft Docs – Teams on VDI components

 
 

In this article, I will run through the summary stages of preparing for MS Teams on Windows Virtual Desktop and discuss the tool I have created to streamline the whole process. The link and video for this is provided at the end of this article. This method creates latency, that then impacts the performance and quality of the video and possibly the underlining host performance.

It is also important to note, that re-encoding on a VM without a GPU is CPU intensive and most often impacts the host and other users logged using the desktop. This does not mean all the problems go away when using a GPU…. This provides a better user experience for the WVD users on the Teams call. This method uses the client hardware to encode and decode.

The first step step 1. Microsoft Official Article covers the various different recommendations. The following can be run using the Command line or PowerShell. Check to ensure the runtime has been installed. As shown in the screenshot below, you can see this is now installed on my lab.

This can be downloaded here: WebSocket Service. If configured correctly and you have rebooted the host….. To check if you have configured correctly, click on your Profile icon, then About , and finally Version. This will then show the required information.

To speed up the process of preparing and deploying teams on Windows Virtual Desktop. I have written a tool that completes all the pre-requests, downloads the installers and installs all the required components.

All you need to do is ensure you run the application as a admin and you remember to reboot once the install has completed. Also see my other blog post that automates the full teams process using a Custom Script Extension. What do you think about using redirection to lower the size of profiles? Another person recommends something like this in a file then redirect via GPO call to the file. The concept of a profile stored in a virtual disk, is to facilitate the ability to detach the user profile data from the underlining OS.

In most cases, yes. This enables the flexibility of this data roaming with the user in the format of a mountable vDisk. Yes redirecting reduces the profile size, but for what reason? Moving the data to the local profile local disk. What would be the impact….. Reduction of disk space on the OS local disk possibly performance issues? Meaning the data stored locally is temporary as long as you have configured the XML file correctly.

Design and sizing of the local disk is important, as well as understanding what would be beneficial for redirection. When you look at the significate reduction in profile size by redirecting teams to a temporary local profile.

This should be tested as there may be user experience changes due to the teams data being temporary. I Ryan, in your opinion, this configuration could be used with classic RDP as well? We have people at home connected to their pc in the office.

But when a call is made via a PSTN line, the call is received in Teams remoteapp but when answered, there is no call media as in no voice is heard.

Is there any additional configuration that is required for voice call over PSTN? Many thanks in advance. Ryan, thank you for putting this together. This is really informational. I followed all the steps and being able to redirect audio just fine and people are able to see my video and screen shares but I am not able to view incoming video or screen shares. Can you suggest any solution. You are commenting using your WordPress. You are commenting using your Twitter account. You are commenting using your Facebook account.

Notify me of new comments via email. Notify me of new posts via email. This site uses Akismet to reduce spam. Learn how your comment data is processed. Create a website or blog at WordPress. Like this: Like Loading Challenges and risks: Yes redirecting reduces the profile size, but for what reason? Conclusion and summary: Redirection is useful for redirecting caches, log files and none essential profile data. Hi, I have not tried this as of yet with remote apps.

Just desktop only. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public.

Name required. All rights reserved. Blog Stats 3,, hits. Follow me on Twitter My Tweets. Follow Following. Sign me up. Already have a WordPress. Log in now. Loading Comments Email Required Name Required Website. By continuing to use this website, you agree to their use.

To find out more, including how to control cookies, see here: Cookie Policy. IP addresses.