Microsoft Teams Optimization with VMware Horizon | VMware - Applicable Products

Looking for:

- Teams vdi install download 

Click here to DOWNLOAD

     

- Optimization for Microsoft Teams | Citrix Virtual Apps and Desktops 7

 

Review the information in this section to ensure that you meet all requirements for proper functionality. You can download the latest version of Citrix Virtual Apps and Desktops at the Citrix downloads site. You'll need to sign in first.

For the latest server and client requirements, see the Optimization for Microsoft Teams article on the Citrix website. VMware Horizon is a modern platform for secure delivery of virtual desktops and apps across the hybrid cloud. To offer a great end-user experience, VMware Horizon provides media optimization for Teams. 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.

Root permission is required. Citrix Viewer app requires access to macOS Security and Privacy preferences for screen sharing to work. If you want to disable Microsoft Teams optimization, run this command in a terminal and restart the Citrix Workspace app:. This section provides recommendations and guidance to estimate how many users or virtual machines VMs can be supported on a single physical host. The idea is to find out how many users or VMs can be ran on a single piece of hardware running a major hypervisor.

This section includes guidance to estimate SSS. Note that the guidance is high level and might not necessarily be specific to your unique situation or environment. Citrix recommends using this guidance and these simple rules to quickly estimate SSS only. However, Citrix recommends using Login VSI or the load testing tool of your choice to validate results, especially before purchasing hardware or making any financial decisions. To enable optimization for Microsoft Teams, use the Manage console policy described in the Microsoft Teams redirection policy.

This policy is ON by default. In addition to this policy being enabled, HDX checks to verify that the version of the Citrix Workspace app is at least the minimum required version. Microsoft Teams reads the key to load in VDI mode.

Loading the API is the first step toward redirection. Exit Microsoft Teams by right-clicking the notification area icon and restarting. Microsoft Teams relies on Media Processor servers in Microsoft for meetings or multiparty calls. So the network health between the peer and the Microsoft cloud determines the performance of the call. Please refer to Microsoft network connectivity principles for detailed guidelines around network planning. We recommend evaluating your environment to identify any risks and requirements that can influence your overall cloud voice and video deployment.

For support information, see Support. The manner in which this is accomplished will vary depending on the VPN product and machine platform used but most VPN solutions will allow some simple configuration of policy to apply this logic.

For more information on VPN platform-specific split tunnel guidance, see this Microsoft article. Citrix minimum recommendations per user are:. About performance, encoding is more expensive than decoding for CPU use at the client machine. You can hardcode the maximum encoding resolution in the Citrix Workspace app for Linux and Windows. See Encoder performance estimator and Optimization for Microsoft Teams.

If you configure an explicit proxy server in the VDA and route connections to localhost through a proxy, redirection fails. If not, optimization fails. If the branch office is configured to access the internet through a proxy, these versions support proxy servers:. If DNS requests are unsuccessful, P2P calls with outside users and conference calls media establishment fails.

This support means that the endpoint must be able to perform DNS resolutions. Consider a scenario where there is no direct path between the two peers or between a peer and a conference server and you are joining a multi-party call or meeting. The HdxRtcEngine. These ranges include both Transport Relays and media processors, front-ended by an Azure Load Balancer. Call quality depends on the underlying network protocol. Meetings fail. Use this architecture diagram as a visual reference for the call flow sequence.

The corresponding steps are indicated in the diagram. Citrix media engine and Teams. With Direct Routing, you connect your own supported session border controller to the Microsoft Phone System directly without any additional on-premises software.

Call queues, transfer, forward, hold, mute, and resume a call are supported. Starting with version , Citrix Workspace app supports dynamic emergency calling. The notification is provided based on the current location of the Citrix Workspace app that runs on the endpoint, instead of the Microsoft Teams client that runs on the VDA.

To enable dynamic emergency calling, the administrator must use the Microsoft Teams Admin Center and configure the following to create a network or emergency location map:. When users start an optimized call using the Microsoft Teams client for the first time, they might notice a warning with the Windows firewall settings.

The warning asks for users to allow communication for HdxTeams. You can apply more restrictive rules if you want. You can deploy Microsoft Teams and Skype for Business side by side as two separate solutions with overlapping capabilities.

For more information, see Understand Microsoft Teams and Skype for Business coexistence and interoperability. Examples include island modes and Skype for Business with Microsoft Teams collaboration. Also, Skype for Business with Microsoft Teams collaboration and meetings. Peripheral access can be granted only to a single application at the time. For example, webcam access by the RealTime Media Engine during a call locks the imaging device during a call.

When the device is released, it becomes available for Microsoft Teams. Optimal audio and video quality require a network connection to the Microsoft cloud that has low latency, low jitter, and low packet loss. Backhauling of Microsoft Teams audio-video RTP traffic from Citrix Workspace app users at branch office locations to a data center before going to the internet can add excessive latency.

It might also cause congestion on WAN links. This use is to identify, categorize, and steer Microsoft Teams traffic. Business broadband internet connections in many areas suffer from intermittent packet loss, periods of excessive jitter, and outages. You can use multiple meetings or chat windows for Microsoft Teams in Windows. 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. 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. Fallback mode has the same limitations as optimized mode. Microsoft is continuously adding features. For the latest supported features list, see the Microsoft document Teams for Virtualized Desktop Infrastructure. You can also try running Microsoft Teams from within a Chrome browser, which will give you an idea of the available functionality.

If you have full-clone persistent desktops, can you apply the GPO to only those users who will be able to run in optimized mode? If your end users do not fall neatly into a group that can run the supported versions of Horizon Clients on Windows, Linux, or Mac platforms, how many of your users are running older versions or some other unsupported OS? Can you be sure that your endpoints are running the latest version of Horizon Client for Windows, Linux, or Mac platforms?

If you decide that the benefits of optimization are worth having some users running in fallback mode, plan on resourcing your VMs to run either in optimized mode or in fallback mode. See the requirements below.

Additional Considerations When deploying this feature, also take the following guidelines into account. Optional Configuration Settings for Issues with Echo In certain low-powered clients, users may want to turn off software acoustic echo cancellation to reduce CPU usage.

Set to 1 — Enable software acoustic echo cancellation irrespective of whether or not acoustic echo cancellation is available in the hardware. Registry key not present default — Software acoustic echo cancellation is enabled only if hardware acoustic cancellation is not available.

Troubleshooting 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 the registry key is correctly set, continue to the next action item. Action 3: Restart the Microsoft Teams Application In the virtual desktop, restart Microsoft Teams to ensure that the correct settings have been applied by the Microsoft Teams client.

Action 5: Check for a Conflicting Agent Installation To ensure that Microsoft is not detecting a conflicting Citrix Agent installation on the desktop, review the Microsoft logs. 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.

Action 4: Check the html5Server Logs in the Virtual Desktop Important : For the following step, you need to have administrator privileges on your virtual desktop operating system. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Watch the following session to learn about the benefits of the Windows Desktop Client, how to plan for it and how to deploy it: Teams Windows Desktop Client.

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.