Teams for Virtualized Desktop Infrastructure - Microsoft Teams | Microsoft Docs

Looking for:

Microsoft Teams on Azure Virtual Desktop - Azure | Microsoft Docs 

Click here to DOWNLOAD

     

Install microsoft teams for vdi -

 

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.

Cannot install for all users when a VDI environment is not detected. All users can then uninstall Teams if they have admin credentials. PowerShell script : You can use the Teams deployment cleanup PowerShell script to uninstall Teams and remove the Teams folder for a user. Run the script for each user profile in which Teams was installed on the computer.

There are a variety of virtualized setup configurations, each with a different focus for optimization. For example, a configuration might focus on user density. When planning, consider the following to help optimize your setup based on your organization's workload needs.

In addition to chat and collaboration, Teams on VDI with calling and meetings is available with supported virtualization provider platforms. Supported features are based on the WebRTC media stack and virtualization provider implementation. The following diagram provides an overview of the architecture.

If you currently run Teams without AV optimization in VDI and you use features that are not supported yet for optimization such as Give and take control when app sharing , you have to set virtualization provider policies to turn off Teams redirection. This means that Teams media sessions won't be optimized. For steps on how to set policies to turn off Teams redirection, contact your virtualization provider.

We recommend that you evaluate your environment to identify any risks and requirements that can influence your overall cloud voice and video deployment. To learn more about how to prepare your network for Teams, see Prepare your organization's network for Teams.

The chat and collaboration experience works as expected. When media is needed, there are some experiences that might not meet user expectations on the Chrome browser:. If your organization wants to only use chat and collaboration features in Teams, you can set user-level policies to turn off calling and meeting functionality in Teams. You can set policies by using the Teams admin center or PowerShell. It up to a few hours for the policy changes to propagate. If you don't see changes for a given account immediately, try again in a few hours.

Calling polices : Teams includes the built-in DisallowCalling calling policy, in which all calling features are turned off. Assign the DisallowCalling policy to all users in your organization who use Teams in a virtualized environment. Meeting policies : Teams includes the built-in AllOff meeting policy, in which all meeting features are turned off.

Assign the AllOff policy to all users in your organization who use Teams in a virtualized environment. To assign the DisallowCalling calling policy and the AllOff meeting policy to a user:. If you have an existing implementation of Teams on VDI with chat and collaboration in which you had set user-level policies to turn off calling and meeting functionality, and you're migrating to Teams with AV optimization, you must set policies to turn on calling and meeting functionality for those Teams on VDI users.

You can use the Teams admin center or PowerShell to set and assign calling and meeting policies to your users. It can take some time a few hours for policy changes to propagate. If you don't see changes for a given account immediately, try again after a few hours.

Specialty keyboards. TWAIN devices. WIA devices. HDX 3D Pro. Text-based session watermark. Screen sharing. Virtual display layout.

Audio features. Browser content redirection. HDX video conferencing and webcam video compression. HTML5 multimedia redirection. Optimization for Microsoft Teams. Monitor, troubleshoot, and support Microsoft Teams. Windows Media redirection.

General content redirection. Client folder redirection. Host to client redirection. Bidirectional content redirection. Generic USB redirection and client drive considerations.

Printing configuration example. Best practices, security considerations, and default operations. Printing policies and preferences. Provision printers. Maintain the printing environment.

Work with policies. Policy templates. Create policies. Compare, prioritize, model, and troubleshoot policies. Default policy settings. Policy settings reference. ICA policy settings. HDX features managed through the registry. Load management policy settings. Profile management policy settings. User personalization policy settings.

Virtual Delivery Agent policy settings. Virtual IP policy settings. Connector for Configuration Manager policy settings. Multi-type licensing. FAQ for licensing. Universal Windows Platform Apps. Connections and resources. Local Host Cache. Virtual IP and virtual loopback. Delivery Controllers. VDA registration. Use Search in Studio. User profiles. Citrix Insight Services. Citrix Scout. Configuration logging. Event logs.

Advanced configuration. PIV smart card authentication. Network analysis. Delegated Administration and Director. Secure Director deployment. Configure with Citrix Analytics for Performance. Site analytics. Alerts and notifications. Filters data. Historical trends. Troubleshoot deployments. User issues. Feature compatibility matrix. Data granularity and retention.

Troubleshoot Director failure reasons. Third party notices. Document History. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. The endpoint decodes and provides the multimedia locally, moving the Citrix Workspace app window back into the hosted Microsoft Teams app.

Authentication and signaling occur natively on the Microsoft Teams-hosted app, just like the other Microsoft Teams services for example chat or collaboration. Citrix and Microsoft recommend the latest available version of Microsoft Teams and to keep it up to date. Unsupported Microsoft Teams desktop app versions show a blocking page to users and request to update the app.

We recommend that you follow the Microsoft Teams machine-wide installation guidelines. Also, avoid using the. All users can then uninstall Microsoft Teams if they have administrator credentials.

Suppose you have Windows 10 dedicated persistent VDI environments. In this case, use the. We recommend that you install Microsoft Teams version 1. Version 1. For example, Breakout Rooms, pop out windows for meetings and chat, or meeting reactions. For information, see Optimization for Microsoft Teams with Citrix App Layering in the list of features that managed through the registry.

The following is an example of folders, desktop shortcuts, and registries created by installing Microsoft Teams machine-wide installer on a Windows Server bit VM:. When using the. All the files are placed in AppData. The best practice recommendations are based on the use-case scenarios.

Using Microsoft Teams with a non-persistent setup requires a profile caching manager for efficient Microsoft Teams runtime data synchronization. With a profile caching manager, the appropriate user-specific information is cached during the user session. For example, the user-specific information includes, user data, profile, and settings. Synchronize the data in these two folders:. Exclude the files and directories from the Microsoft Teams caching folder as described in the Microsoft documentation.

This action helps you to reduce the user caching size to further optimize your non-persistent setup. In this scenario, the end user uses Microsoft Teams in one location at a time. In a common virtual desktop deployment, each user is assigned to one desktop, and Microsoft Teams is deployed in the virtual desktop as one application. We recommend enabling the Citrix Profile container and redirecting the per-user directories listed in Per-user installer into the container.

List all the per-user directories into this configuration. For a complete list of verified endpoints, see Thin Clients. For more information, see Prerequisites to install Citrix Workspace app. After the update is complete, restart the Session.

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.