Looking for:

Teams for Virtualized Desktop Infrastructure – Microsoft Teams | Microsoft Docs

Click here to Download


Making a video call from a virtual desktop can be tricky. But the RTAV feature still sends a lot of data across the wire, and the virtual desktop has to process the data and send it out over the network to complete the call. At the same time, the virtual desktop is capturing the video feed and sending it back over the network, using the VMware Blast display protocol, to the endpoint so that the end user can see the video feed.

Horizon Client draws over the Microsoft Teams window in the virtual desktop Install teams in vdi, giving users the impression that they are still in the VM, but the media is actually traveling directly between the local endpoint and the remote peer as shown in Figure 1.

The load disappears from the network, ссылка на продолжение the processing moves from the data center to the endpoint. Often the end-user experience improves as well because the data has one less hop to make.

Using this mechanism, this process avoids using RTAV altogether. The Media Optimization for Microsoft Teams feature is a boon for organizations using Microsoft Teams for audio and video calls. This document helps you plan for deploying it. The following diagram describes the flow of data between the various components of the Microsoft Teams optimization feature in Horizon.

Figure 1: Microsoft Teams Optimization Flow. Horizon supports audio, video, and screen-sharing offload to the local endpoint on Windows, Mac, and Linux platforms. Below is a list of the minimum supported versions for each platform. For a complete list of features supported on each platform, see the product documentation topic for the version of Horizon that you are using. Note : For Horizon documentation references, we will be using Horizon 8 product documentation links throughout this guide.

X and later. Microsoft also turned on the service on their side on August 11, To take advantage install teams in vdi the install teams in vdi capability, you must use Horizon Client for Windows or later, Horizon Client for Mac or later, or Horizon Client for Linux or later.

The Install teams in vdi Optimization for Microsoft Teams group policy setting must be enabled in the virtual desktop. Web browser media offload is supported with the Browser Redirection feature. See Configuring Browser Redirection нажмите для продолжения support details.

/9556.txt section briefly lists the system requirements for both the client and the virtual desktop when using the Увидеть больше Optimization for Microsoft Teams feature. Client system for OSes supported with a specific release, see the appropriate Horizon Client release notes. You can see the setting if you select Customize installation in the installer.

Double-click the. If you are using the installation wizard, you can see that the Media Optimization for Microsoft Teams option is selected, install teams in vdi shown below. Media Optimization for Microsoft Teams is also installed by default in install teams in vdi Horizon Agent, but it is controlled ссылка a GPO, which is not enabled by default. After setting this policy, you must log out of the Horizon desktop for the GPO policy to take effect.

Horizon Agent must be installed before Microsoft Teams. If the order is reversed, then on first run, Microsoft Teams does not detect Horizon Agent and caches an environment value that indicates the feature is running on an unsupported remote desktop. This results in Microsoft Teams never supporting the Media Optimization feature unless the cache is deleted. To avoid this issue, be sure to install Horizon Agent before you install Microsoft Teams.

Then, on first run, Microsoft Teams detects Horizon Agent and caches the correct environment value, which verifies that the feature is running on a supported remote desktop. As described in the overview of this guide, there are significant advantages to running Microsoft Teams in optimized mode. However, as you are planning your implementation, keep install teams in vdi mind that end users who are not running supported Horizon Client versions Horizon Client or later for Windows, Horizon Client or later for Mac, or Horizon Client or later for Linux will not be able to take advantage of this feature.

They will not, however, go back to running the full client in the virtual desktop because the GPO has set Microsoft Teams to offload audio and video to the client. Those users will instead run in fallback mode. A user can check if Microsoft Teams is running in optimized mode, fallback mode, or natively no optimization in the virtual desktop. Audio and жмите сюда quality may be reduced.

Talk to your IT admin. If you enable the optimization GPO in the virtual desktop, these clients, although not officially supported, will begin implementing install teams in vdi.

The bugs we found in these clients during beta testing are fixed in Horizon Client for Windows version or later for Horizon 8 or Horizon Client for Windows 5. VMware strongly recommends using the officially supported versions. For beta testing, VMware published the Horizon Client beta installer for Mac via the beta portal that supports optimization. VMware recommends that you use the officially install teams in vdi version, Horizon Client or later for Mac, to get the latest functionality and bug fixes for the Mac client.

Similarly, VMware published a beta version of Horizon Client for Linux that supports optimization via the beta portal. VMware recommends using the officially supported version, Horizon Client or later for Linux, to get the latest functionality and bug fixes for the Linux client.

The ports described on that page are required to be opened on the client device. Note : The usual Horizon ports are also required, as detailed in the following documents:. Some organizations might require that the process name of the Teams Optimization Pack be added to a firewall allowlist, to allow communication to the Microsoft Teams Cloud server.

The process name is vmware-remotemks. This is a Microsoft restriction. In certain low-powered clients, users may want to turn off software acoustic echo cancellation to reduce CPU usage. In most cases, VMware recommends using the default configuration, which is designed for install teams in vdi audio experience.

But if you are having issues with echo, software acoustic echo cancellation can be configured by using a GPO on the Horizon Agent or by setting a registry key on the Horizon Client. Note that this configuration is only supported on Windows Clients. After setting this policy, you must log out of the Horizon desktop for the GPO policies to take effect.

This configuration can also be applied on the На этой странице Client for Windows device by setting the following registry key:. To troubleshoot, start by checking whether Microsoft Teams launched in optimized mode and whether the correct local client device names are being picked up.

If so, you can check whether the Microsoft Teams redirection plugin has been installed and check the logs to verify that optimization has been enabled. Procedures for these tasks are described in the following sections:. Figure 9: Version Box for Microsoft Teams. If the registry key is not set, follow the installation guidance for Horizon Agent, as described in Horizon Agent Installation and Configuration.

Also install teams in vdi that you need to log out of the Horizon desktop for the GPO policies to be applied. In the virtual desktop, restart Microsoft Teams to ensure that the correct settings have install teams in vdi applied by the Microsoft Teams client. We have seen issues in Microsoft Teams where incorrect flags get applied. Restarting Teams ensures that the correct flags are pulled in and applied.

Quit the Microsoft Teams application. This will force Microsoft Teams to reload its cache, which may have contained outdated values related to the environment. To ensure that Microsoft is not detecting a conflicting Citrix Agent installation on the desktop, review the Microsoft logs. Instructions подробнее на этой странице collecting Microsoft logs are provided in the Microsoft documentation topic Use log files to monitor and troubleshoot Microsoft Teams. In Microsoft Teams, click the ellipsis points … next to your profile picture at the top, and then select Settings install teams in vdi go to the Install teams in vdi section.

Under Audio devicesyou should see the local headset names in the Speakers and Microphone drop-down lists. Figure Device Settings for Microsoft Teams.

If you see the local device names in the Microsoft Teams device settings, then Microsoft Teams optimization install teams in vdi been enabled in your environment. Check if html5Server. If you do not see html5server. If you still do not see html5server. If you see that html5server. Similarly, if you are using a. Otherwise, html5server will not work as expected.

Because html5server. This is an internal registry key used by html5Server. Backing up and restoring the registry key may result in erroneous behavior. If install teams in vdi do not have any user profile management software installed or have excluded the above-mentioned registry key from the list, follow the next action item.

Important : For the following step, you need to have administrator privileges on your virtual desktop operating system. If you see the below highlighted section, then Microsoft Teams optimization has been enabled on your VM. Note : For your convenience, the highlighted text you can search for includes the following settings:.

If the above settings are missing from the logs or if the logs display « allow:false » then Microsoft Teams optimization has not been enabled in your environment. Go through the installation guidance for Horizon Client for Windows or Linux, as described in Client Installationand ensure that Media Optimization for Microsoft Teams check box has been selected in the Horizon Client Installation wizard.

For the Mac platform, ensure that you have the supported version of Horizon Client installed. If you have the supported versions installed and have selected the right configuration for Media Optimization for Microsoft Teams, contact VMware support. If you see the below highlighted section in the logs, then Microsoft Install teams in vdi optimization has been correctly enabled for your session.

If the above settings are missing from the logs or install teams in vdi the logs display « allow »: »false » then Microsoft Teams optimization has not been enabled in your environment. Contact VMware for further assistance. If Microsoft Teams on VDI is optimized and you are running into generic issues, or if you find that features are missing, check if you see the same behavior when using the Microsoft Teams web client.

If you see the same behavior on the web client, or if you find that a feature is missing, contact Microsoft for further assistance. This section describes how to collect logs from the virtual приведу ссылку, the client device, and the Microsoft Teams app. The improved end-user experience, decreased load on the data center, and decrease in network traffic make Media Optimization for Microsoft Teams a compelling feature.



Install teams in vdi.Teams for Virtualized Desktop Infrastructure


This makes complete sense for a VDI environment. They found a series of laptops that would not update to the latest Teams client no matter what they did. The only recourse was to uninstall and reinstall the client. This credit goes to one our engineers, Jeremy Coleman, who did all of the hard work of tracking down what was happening. That entry may also have a value of 1, either case indicates you are in VDI mode.

If it does not exist or has the value of 0, you are not in VDI mode. To get to the diagnostic logs, you can follow the steps laid out in the Microsoft Docs. That is where Process Monitor comes to the rescue. So they fired up ProcMon during the installation of Teams and found this:. If either of those registry keys are present then the client will go into VDI mode during installation, regardless if you add any specific switches during the install.

You can have extra fun, if you try adding this switch:. So the question becomes, what app is putting those register keys on the workstation. After a bunch of hunting, is appears there is a Password Management application laying down the Citrix keys, why? But at least we have the cause figured out. These are just some random thoughts and ideas from a Microsoft MVP.

The Argyle MVP. AMA 1. Azure 4. Bots 1. Development Essential PH-1 1. Bulk deployments are useful because users don’t need to download and install the Teams client manually. Rather, Teams will be deployed to computers and then auto-launch the first time users sign into a computer. We recommend that you deploy the package to computers rather than a specific user.

By targeting computers, all new users of those computers will benefit from this deployment. Teams can also be distributed to your organization as part of Microsoft Apps for enterprise. Download the MSI that you want to install on computers in your organization. The x86 architecture bit or bit Teams supports is independent of other Office apps installed on a computer. If you have bit computers, we recommend installing the bit Teams MSI even if the computer is running a bit version of Office.

Install the bit version of Teams only on bit operating systems. If you try to install the bit version of Teams on a bit operating system, the installation won’t be successful and you won’t receive an error message. MSI files can’t be used to deploy updates. The Teams client will auto-update when it detects a new version is available from the service.

To re-deploy the latest installer, use the process of redeploying MSI described below. If you deploy an older version of the MSI file, the client will auto-update except in VDI environments when possible for the user. If a very old version gets deployed, the MSI will trigger an app update before the user is able to use Teams. We don’t recommended that you change the default install locations as this could break the update flow.

Having too old a version will eventually block users from accessing the service. Make sure the computers you install Teams on meeting the requirements listed in Hardware requirements for Microsoft Teams. If a user uninstalls Teams from their user profile, the MSI installer will track that the user has uninstalled the Teams app and no longer install Teams for that user profile. To redeploy Teams for this user on a particular computer where it was uninstalled, do the following:.

The next steps contain information about how to modify the registry. Make sure that you back up the registry before you modify it and that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see Windows registry information for advanced users. You can also use our Teams deployment clean up script to complete steps 1 and 2. The default behavior of the MSI is to install the Teams app as soon as a user signs in and then automatically start Teams.

If you don’t want Teams to start automatically for users after it’s installed, you can use Group Policy to set a policy setting or disable auto launch for the MSI installer. Enable the Prevent Microsoft Teams from starting automatically after installation Group Policy setting.


Install teams in vdi


Additionally this works on both Windows 10, and Windows Shared computer activation is an optional activation method built inside of Office and Microsoft , designed to control and manage activations on shared computers. Originally this technology was used for Office on RDS Remote Desktop Servers to handle multiple users since Office is activated and licensed per user. Later, this technology was modified to handle Office activations in non-persistent VDI environments. These activation tokens are saved to a network location that the users has access to which allows the user to roam.

Due to the nature of non-persistent VDI, a user will always be logging in to a system they have never logged in to before. This is also handy with persistent VDI, where you can have a roaming activation token be used on multiple desktop pools as it follows the users. These activation tokens once generated are valid for 30 days and remove the need to activate Office during that timeframe. The licensing information and activation without SCA is stored in the following directory:.

You can configure Shared Computer Activation and the location of the roaming activation token using Group Policy, the local registry, or the configuration. If you are using persistent VDI where users are assigned a desktop they are frequently using, shared computer activation is not necessary and does not need to be used. You can either modify and edit the Office configuration. Using the Office Deployment Tool and the Office Customization Tool, you can customize your Office installation to your specific needs and requirements.

Once you have a configuration. The configurations you use will vary depending on your VDI deployment type which I will get in to below. The behavior will match that of a typical workstation as far as software updates are concerned. Even if you are using persistent VDI, I highly recommend you read the notes below on installing Office on non-persistent VDI as you may want to incorporate that configuration in to your deployment.

To deploy Office with non-persistent VDI, things are a little different than with persistent. Using the Office installer for the above products will cause issues as the software gets installed in the user profile instead of the operating system itself. This is because these are not used in my environment.

We also choose to accept the EULA for users so they are not prompted. Go ahead and download the MSI installers from below and follow the instructions below:. In persistent VDI environments, the auto-update mechanism will be enabled and activated unless you chose to disable it , and Office will update as it does with normal windows instances.

In non-persistent VDI environments the updating mechanism will be disabled as per the XML configuration example above. We run the following commands on the base image to update Office The commands above will download and install the most up to date version of Office using the channel specified in the XML file.

You then deploy the updated base image. You may have configured a special location for these, or may just store them with your user profiles. We will now configure the User Configuration items. As most of you know, when running Microsoft Office for the first time, there are numerous windows, movies, and wizards for the first time run.

We want to disable all of this so it appears that Office is pre-configured to the user, this will allow them to just log on and start working. Again, just another step to let them log in and get to work right away. Using the One time Only will not try to apply the configuration on all subsequent Outlook runs.

We can stop this by disabling Exchange caching. This setting is not required when using FSLogix. When troubleshooting this, one may think that the issue is related to SCA, when it is actually not. This prompt is occurring because of authentication issues with Office This will delete the Identity key on login, and allow Office to function. This may not be needed if using FSLogix or other profile management suites.

At this point you can push and deploy the base image and have users log in to the VDI environment and Office should be fully functioning.

Please keep in mind there are different methods for deploying and configuring Office depending on what application delivery and profile management software you may be using. This is just a guide to get you started! Great post! Have you figured out first-run SSO for Teams machine wide installations? New users will have their username filled in when Teams opens but they still need to hit Connect and enter their password and MFA code if enabled one time for Teams to stay signed in.

I think with roaming profiles it only occurred once, and then worked normally after that. This guide was amazing for our transition to Microsoft in our VDI environment. Amazing guides, keep it up!

Great article, good info. What are your thoughts on stacking Visio into O with App Volumes? Any other way blows up licensing. How do you have the existing O suite installed? Do you have it baked in the image, or are you using App Volumes? I just want to compliment you for this super guide. It helped us a lot to implement Office in our VDI environment. Many thanks from Heerenveen, Holland! This is really good information and very helpful.

The only thing I miss is SSO. Any immediate thoughts? I have disabled it in the GPO. Also, are your ADMX templates the latest version? It should be a fairly straightforward process to update these. Simply make sure you update both the ADMX files as well as the applicable language files. So the same config we used initially with the above switches would update the version of office to latest?

In my example, I chose to store the roaming activation token in the user profile directory. You can store it here or you can create a share for the roaming activation tokens. Also in the example above, I have used GPOs to automatically sign in to and activate the users Office license. So yes, the user logs in and then it creates and stores the roaming activation token. Any known issues when using FsLogix on your experience?

After initial log-in, the users are prompted with Microsoft login prompts whenever they start an Officeapplication, OneDrive or Teams. Outlook is even asking twice, apparently for authentication towards the Exchange and towards Office-Licensing.

Any idea on why those prompts still show up? Should I still configure a separate path for the roaming activation token? I had the problem that the login window from the Office Apps did not appear. I was able to fix this with a logon script, but now people with MFA can no longer log in. Do you have any idea what this could be? No fix is required as this is the proper and best behaviour. Thank you for the answer, I use this script to make the login work.

When I do not use the script, the Office apps freezes in Horizon after requesting the mail address. I used this script from Microsoft for this:. Thanks for this article. The above was when opening Outlook, we were getting a prompt to have device managed by organisation.

We have one issue, which is becoming a pain point. When a user logs in for first time, they are being prompted to login to activate. There are a few blogs saying this is the norm but according to the above we should be able to skip that. Can you advice what the delete of the identity reg key and make sure its not roaming with profile bit does, that is only thing we havent applied yet and think may sort our problem.

The thing is that key appears when you start office app, so when you delete on login, dont know how that will help. For activation, as long as you configure the GPOs to auto-sign in using the users credentials, they should not be prompted. The key is required for profile management so that it can sign-in and activate instead of preparing a warning.

The identity key has computer identity specific information in it, and when logging in with different computers it needs to generate new values. That is excellent, sorted our issues and we good to go! Thanks for the article — we have one final question. When opening Edge, going to office. If the users UPN matches their e-mail, it should automatically sign in without prompting for an e-mail address.

Most of the configuration I do is via GPOs. You might have to reference the Microsoft documentation. I only need Word, PowerPoint, and Excel in my environment, no email.

Thank you for this guide, it is the most complete one I can find for VDI. Great article!