Looking for:
Optimize teams for vdi |
Optimize teams for vdi.Microsoft Teams Optimization with VMware Horizon
Discover best practices, product information, and IT tips that you can use to help your business. As a part of Covid precautions driving business trends, Microsoft Teams usage increased exponentially when the solution was added to the default Office suite and increased in functionality. Usage of Teams in compared to was up around percent and holds steady as businesses worldwide continue to figure out how to best support their remote workers.
At first glance, admins could believe Teams is a typical co llaboration tool, such as Citrix Podio, or a meetings app, such as Cit rix GoToMeeting. It is possible for Teams to replace these tools. However, getting there requires significant pre-planning and implementation of additional Microsoft components.
Managing Teams within a virtual desktop infrastructure VDI environment also requires some considerations. Install Location: Per-machine or Per-user? Endpoint Device. Citrix Optimization Feature. Is your VDI infrastructure or hardware making it difficult to use Teams?
Should I Install Per-machine or Per-user? A zero-day or a business enhancing feature released will be able to be introduced to the environment quickly. However, an environment breaking patch can also be released uncontrolled if installed per-user. For example, Citrix optimization was only available when deploying on the system drive.
But with a recent patch, this was no longer true, and Teams automatically switched to Citrix optimization mode, which has limited features. These types of issues result in a significant number of help desk calls until a workaround could be implemented. In early , it was recommended to install per-user as it allowed preventing Teams from auto-starting.
This let users who were not interested in Teams not have it launch and reduced the infrastructure resource requirements of every user having a Teams session. However, as Covid precautions stuck around and adoption drastically increased, it no longer made sense to allow per-user installs to persist and provide inconsistency in the environment.
The migration from per-user to per-machine is automatic. Microsoft will convert the install when a per-user logs into a per-machine image. We noticed that the Taskbar shortcut must be unpinned and repined as it still pointed to per-user install. Also, the Teams Outlook add-in pointed to the old per-user install and had to be fixed with a registry key update. And finally, on rare occasions, the migration did not work successfully; In the session as an admin, Teams had to be uninstalled and then reinstalled.
Pros and cons of per-machine and per-user installments:. How many end devices are needed is largely dependent on whether optimization will be enabled see section below.
If unoptimized, the end-device is less important as most of the computation occurs in the VDI. H owever , all audio and webcam must still traverse the network to the VDI. This can provide a wide disparity in end-user experience if a standard is not implemented. This increases outbound network load to the internet for your branch sites. Microsoft has worked together with virtual desktop vendors, such as Citrix and VMware, to implement an optimized mode of Teams.
This enables H. While significantly improved over , there are still feature limitations in the optimized version of Teams.
It can be tempting to include the Teams app with the rest of the Office installation to gauge end-user interest. However, Teams uses Electron and Optimization, and some of those limitations require a VDI architect to consider unique design decisions compared to the rest of the Office suite. The fast pace and complexity to implement Teams requires careful planning, design, and proper hardware prior to implementation to prevent data loss and performance degradation.
Consider using a managed virtual desktop infrastructure provider to help your team avoid set-up and implementation errors, and keep Teams running smoothly for your entire remote workforce. To learn more, download the complete solution brief: Deploying Microsoft Teams. Have VDI questions?
Our Info sessions are always free. Schedule one for your team:. Capital View Center S. Whitehat Virtual Blog Discover best practices, product information, and IT tips that you can use to help your business. There are three major design decisions for an admin deploying Teams for VDI: 1. Endpoint Device 3. Installing on the system drive prevents this scenario. Per-machine install prevents auto-updating, which allows proper QA of new Teams releases.
Most virtual desktop optimization clients recommend per-machine installs. Per-machine Cons: Teams updates frequently and bug fixes must be implemented often to keep up to date in the golden image. Once a user launches Teams, they are unable to prevent auto-launch. Teams will always auto-launch and cannot be turned off by the user. Teams consumes all session resources to launch. This effectively means auto-launching is increasing your user logon times because the session will be unusable until Teams finishes launching.
Per-user Pros: Teams can be prevented from auto-launching by an admin by default and a user can toggle auto-launch on or off. This reduces login times as well as resource consumption for virtual machines. Teams stays current by automatically updating.
Per-user Cons: Teams disk storage requirements multiplies by every user instead of the number of machines. Don't have time to read the entire article? Should I Leave on Optimization? Optimize Pros: Optimizing allows Teams to efficiently manage and redirect audio and video, improving performance while reducing server resource utilization.
Audio does not have to double hop between end-device, VDI, and Teams servers but instead goes directly to Teams servers. Also, audio and webcam video are not rendered in the VDI reducing resource utilization. Mapping of audio and webcam devices functions more natively without leveraging VDI vendor technologies, such as Citrix HDX audio, which can be buggy.
The pace with which versions are released provides a significant operational requirement to stay up to date. End-client agent versions must be released by vendor and then updated on the end-device.
The Teams version in the VDI must also be updated if per-machine installed. If thin-clients are used as end devices, the updates can be further delayed as the vendor agents are typically included as part of the thin-client OS. This means operations must validate and deploy new OS versions of thin clients as well as testing in VDI. Features are limited, as defined in section below. Unoptimized Pros: Almost the full feature set of Teams as compared to physical device install.
Teams functions the same way as all other conferencing tools, such as WebEx, reducing user confusion. Unoptimized Cons: Audio and video performance is reduced and heavily dependent on the end-device and VDI network stability. Any latency or bandwidth issues are compounded due to the double hop between device, VDI, and Teams servers. Audio and video device instability causes users to have to restart Teams, and sometimes the VDI session itself, to continue working after crashing.
Leave Comment. Subscribe Our Blog. Most Popular. Whitehat Virtual Technologies. Search website Search Google. Healthcare Finance Manufacturing Retail. P:
Optimize teams for vdi.Use Microsoft Teams on Azure Virtual Desktop
This reduces login times as well as resource consumption for virtual machines. Teams stays current by automatically updating.
Per-user Cons: Teams disk storage requirements multiplies by every user instead of the number of machines. Don't have time to read the entire article? Should I Leave on Optimization? Optimize Pros: Optimizing allows Teams to efficiently manage and redirect audio and video, improving performance while reducing server resource utilization.
Audio does not have to double hop between end-device, VDI, and Teams servers but instead goes directly to Teams servers. Also, audio and webcam video are not rendered in the VDI reducing resource utilization. Mapping of audio and webcam devices functions more natively without leveraging VDI vendor technologies, such as Citrix HDX audio, which can be buggy. The pace with which versions are released provides a significant operational requirement to stay up to date.
End-client agent versions must be released by vendor and then updated on the end-device. The Teams version in the VDI must also be updated if per-machine installed. If thin-clients are used as end devices, the updates can be further delayed as the vendor agents are typically included as part of the thin-client OS. This means operations must validate and deploy new OS versions of thin clients as well as testing in VDI. Features are limited, as defined in section below.
Unoptimized Pros: Almost the full feature set of Teams as compared to physical device install. Teams functions the same way as all other conferencing tools, such as WebEx, reducing user confusion.
Unoptimized Cons: Audio and video performance is reduced and heavily dependent on the end-device and VDI network stability. Any latency or bandwidth issues are compounded due to the double hop between device, VDI, and Teams servers.
Audio and video device instability causes users to have to restart Teams, and sometimes the VDI session itself, to continue working after crashing. 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.
It's important to understand the difference between these parameters. We utilize HP ThinPro devices flavor of Linux in our environment and the latest Linux client now has optimization built in.
It only shows the version we are running, unfortunately. Thank you for the post. Great article. Is the optimization wiring for the ChromeOS client as well? Nevertheless I can share my screen and others can see it. If I turn off teams optimisation everything works fine. This might be why when you disable it, everything works fine. Can you also post Dynamic Environment manager configuration that goes with this installation.
Your Comment. 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.
Microsoft Teams VDI Optimization for VMware Horizon - The Tech Journal.Teams for Virtualized Desktop Infrastructure
Talk to your IT admin. If you enable the optimization GPO in the virtual desktop, these clients, although not officially supported, will begin implementing offload.
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 supported 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 optimal 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 Horizon 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 note 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 been 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 for 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 and go to the Devices section. Under Audio devices , you 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 has 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 you 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 Installation , and 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 Teams optimization has been correctly enabled for your session. 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. 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 desktop, 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.
A thoughtful rollout plan will keep users productive. See the Microsoft Documentation for details about Microsoft Teams installation, performance considerations, and feature limitations. See the VMware Horizon Documentation for details about supported features and limitations. This message will close in seconds.
You are about to be redirected to the central VMware login page. Minimum Supported Horizon Client Versions Horizon supports audio, video, and screen-sharing offload to the local endpoint on Windows, Mac, and Linux platforms.
Horizon 7. System Requirements This section briefly lists the system requirements for both the client and the virtual desktop when using the Media Optimization for Microsoft Teams feature.
Pairing Modes As described in the overview of this guide, there are significant advantages to running Microsoft Teams in optimized mode. Products 68 Special Topics 42 Video Hub Most Active Hubs Microsoft Teams.
Security, Compliance and Identity. Microsoft Edge Insider. Microsoft FastTrack. Microsoft Viva. Core Infrastructure and Security. Education Sector. Microsoft PnP. AI and Machine Learning. Microsoft Mechanics. Healthcare and Life Sciences. Small and Medium Business. Internet of Things IoT. Azure Partner Community.
Microsoft Tech Talks. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for. Show only Search instead for.
No comments:
Post a Comment