Teams for Virtualized Desktop Infrastructure

  • Article
  • 21 minutes to read
  • Applies to:
    Microsoft Teams

This commodity describes the requirements and limitations of using Microsoft Teams in a virtualized environment.

What is VDI?

Virtual Desktop Infrastructure (VDI) is virtualization technology that hosts a desktop operating system and applications on a centralized server in a data centre. This enables a complete, and personalized, desktop experience for users with a fully secured and compliant centralized source.

Teams in a virtualized surround supports conversation and collaboration. And with the Azure Virtual Desktop, Citrix, and VMware platforms, calling and meeting functionality is besides supported.

Teams also supports multiple configurations in virtual environments. These include VDI, dedicated, shared, persistent, and non-persistent modes. Features are in continuous development and are added on a regular footing, and functionality will expand over time.

Using Teams in a virtualized environment might be somewhat different from using Teams in a non-virtualized environment. For example, some advanced features might not be bachelor in a virtualized environment, and video resolution might differ.

To ensure an optimal user experience, follow the guidance in this article.

Teams on VDI components

Using Teams in a virtualized environment requires the post-obit components.

  • Virtualization broker: The resource and connection director to the virtualization provider, such as Azure
  • Virtual desktop: The Virtual Machine (VM) stack that runs Teams
  • Thin customer: The device that the user physically interfaces with
  • Teams desktop app: The Teams desktop customer app

Teams on VDI requirements

Virtualization provider requirements

The Teams desktop app was validated with leading virtualization solution providers. With multiple market providers, we recommend that yous consult your virtualization solution provider to ensure that you meet the minimum requirements.

Currently, Teams on VDI with sound/video (AV) optimization is certified with Azure Virtual Desktop, Citrix, and VMware. Review the information in this section to ensure that you meet all requirements for proper functionality.

Platforms certified for Teams

The post-obit platforms have virtual desktop infrastructure solutions for Teams.

Platform Solution
The logo representing Microsoft. Azure Virtual Desktop, Windows 365
The logo representing Citrix. Citrix Virtual Apps and Desktops
The logo representing VMware. VMware Horizon

Azure Virtual Desktop

Azure Virtual Desktop provides AV optimization for Teams on VDI. To learn more on requirements and installation, meet Use Teams on Azure Virtual Desktop.

Windows 365

Windows 365 uses AV optimization provided by Azure Virtual Desktop to ensure optimal Teams experiences from Cloud PCs. To learn more on requirements and installation, see Utilize Teams on Deject PC.

Citrix Virtual Apps and Desktops requirements

Citrix Virtual Apps and Desktops (formerly known as XenApp and XenDesktop) provides AV optimization for Teams on VDI. With Citrix Virtual Apps and Desktops, Teams on VDI supports calling and meeting functionality in add-on to chat and collaboration.

You tin can download the latest version of Citrix Virtual Apps and Desktops at the Citrix downloads site. (Y'all'll demand to sign in get-go.) The necessary components are bundled into the Citrix Workspace app (CWA) and Virtual Delivery Agent (VDA) by default. You don't need to install any additional components or plugins on CWA or the VDA.

For the latest server and client requirements, see the Optimization for Microsoft Teams commodity on the Citrix website.

VMware Horizon Workspace and Desktop requirements

VMware Horizon is a modern platform for secure delivery of virtual desktops and apps across the hybrid cloud. To offer a great stop-user feel, VMware Horizon provides media optimization for Teams. This optimization improves overall productivity across virtual desktops and apps, and enhances user experience when calling and coming together using Teams.

Yous can download the latest version of VMware Horizon from the VMware Downloads page. The required media optimization components are part of the Horizon Agent and Horizon Client past default and in that location's no need to install any additional plug-in to employ the optimization characteristic 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.

Install or update the Teams desktop app on VDI

You can deploy the Teams desktop app for VDI using a per-machine installation or per-user installation using the MSI package. Deciding on which approach to use depends on whether y'all apply a persistent or non-persistent setup and the associated functionality needs of your organization.

For a defended persistent setup, both per-car and per-user installation will work. However, for a non-persistent setup, Teams requires a per-motorcar installation in social club to work efficiently. Come across the Non-persistent setup section.

With per-car installation, automatic updates are disabled. This ways that to update the Teams app, you must uninstall the electric current version to update to a newer version. With per-user installation, automatic updates are enabled.

Important

Continue the Teams desktop app in your VDI environment up to appointment. Teams desktop app versions with release dates that are more 90 days older than the current version'southward 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, nosotros recommend you deploy Teams using per-machine installation. To update to the latest Teams version, starting time with the uninstall process followed by latest Teams version deployment.

For Teams AV optimization in VDI environments to work properly, the thin-client device must accept admission to the internet. If internet access isn't available at the thin-customer device, optimization startup won't exist successful. This means that the user is in a non-optimized media land.

Dedicated persistent setup

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.

The following is the recommended minimum VM configuration.

Parameter Workstation operating system Server operating system
vCPU 2 cores 4, 6, or viii cores
It's important to understand the underlying non-uniform memory access (NUMA) configuration and configure your VMs accordingly.
RAM iv GB 512 MB to ane GB per user
Storage 8 GB 40 GB to 60 GB

Not-persistent setup

In a non-persistent setup, users' local operating organization changes are not retained after users log off. Such setups are normally shared multi-user sessions. VM configuration varies based on the number of users and available physical server resources.

For a not-persistent setup, the Teams desktop app must be installed per-machine to the gilded image. This ensures an efficient launch of the Teams app during a user session. To learn more, see the Install or update the Teams desktop app on VDI department.

Using Teams in a non-persistent setup likewise 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 information, profile, or settings) is cached during the user'south session. Make certain data in these two folders are synced:

  • C:\Users\username\AppData\Local\Microsoft\IdentityCache (%LocalAppData%\Microsoft\IdentityCache)
  • C:\Users\username\AppData\Roaming\Microsoft\Teams (%AppData%\Microsoft\Teams)

Note

A roaming binder (or, if you are using folder redirection, a caching director) 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 feel due to unavailable data and files.

At that place are a diverseness of caching manager solutions bachelor, such as FSLogix. Consult your caching manager provider for specific configuration instructions.

Teams buried content exclusion listing for non-persistent setup

Exclude the post-obit from the Teams caching folder, %AppData%/Microsoft/Teams. Excluding these items helps reduce the user caching size to further optimize your non-persistent setup.

  • .txt files
  • Media-stack binder
  • %AppData%\Microsoft\Teams\meeting-addin\Cache

Microsoft 365 Apps for enterprise considerations

Consider the following when yous deploy Teams with Microsoft 365 Apps for enterprise on VDI.

New deployments of Teams through Microsoft 365 Apps for enterprise

Before yous deploy Teams through Microsoft 365 Apps for enterprise, you must first uninstall any pre-existing Teams apps if they were deployed using per-machine installation.

Teams through Microsoft 365 Apps for enterprise is installed per-user. To acquire more, see the Install or update the Teams desktop app on VDI section.

Teams deployments through Microsoft 365 Apps for enterprise updates

Teams is besides beingness added to existing installations of Microsoft 365 Apps for enterprise. Since Microsoft 365 Apps for enterprise installs Teams per-user only, see the Install or update the Teams desktop app on VDI section.

Using Teams with per-machine installation and Microsoft 365 Apps for enterprise

Microsoft 365 Apps for enterprise doesn't support per-machine installations of Teams. To apply per-machine installation, you must exclude Teams from Microsoft 365 Apps for enterprise. See the Deploy the Teams desktop app to the VM and How to exclude Teams deployment through Microsoft 365 Apps for enterprise sections.

How to exclude Teams deployment through Microsoft 365 Apps for enterprise

To acquire more about Teams and Microsoft 365 Apps for enterprise, meet How to exclude Teams from new installations of Microsoft 365 Apps for enterprise and Employ Group Policy to control the installation of Teams.

Deploy the Teams desktop app to the VM

  1. Download the Teams MSI package that matches your VDI VM operating arrangement using one of the post-obit links:

    • 32-bit version
    • 64-bit version

    The minimum version of the Teams desktop app that's required is version ane.3.00.4461. PSTN hold isn't supported in earlier versions.

  2. Install the MSI to the VDI VM by running one of the following commands:

    • Per-user installation (default)

                            msiexec /i <path_to_msi> /fifty*v <install_logfile_name> ALLUSERS=1

      This process is the default installation, which installs Teams to the %AppData% user binder. At this point, the gold image setup is complete.

      Of import

      Teams won't work properly with per-user installation on a not-persistent setup.

    • Per-auto installation

                            reg add "HKLM\SOFTWARE\Microsoft\Teams" /v IsWVDEnvironment /t REG_DWORD /d ane /f

      This process adds a required registry fundamental to the car that lets the Teams installer know it is a VDI case. Without information technology, the installer volition error out, stating: "Installation has failed. Cannot install for all users when a VDI environs is not detected."

                            msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=ane ALLUSERS=1

      This process installs Teams to the %ProgramFiles(x86)% folder on a 64-bit operating system and to the %ProgramFiles% folder on a 32-bit operating system. At this point, the golden image setup is complete.

      Important

      Installing Teams per-machine is required for not-persistent setups.

      When the adjacent interactive logon session starts, Teams starts and asks for credentials.

      Note

      These examples also use the ALLUSERS=i parameter. When you set this parameter, Teams Auto-Wide Installer appears in Programs and Features in Control Panel and in Apps & features in Windows Settings for all users of the reckoner. All users can then uninstall Teams if they have admin credentials.

      It's important to understand the difference between ALLUSERS=1 and ALLUSER=i. The ALLUSERS=1 parameter tin can be used in not-VDI and VDI environments, while the ALLUSER=i parameter is used just in VDI environments to specify a per-machine installation.

  3. Uninstall the MSI from the VDI VM. There are two ways to uninstall Teams.

    • PowerShell script: You can use the Teams deployment cleanup PowerShell script to uninstall Teams and remove the Teams binder for a user. Run the script for each user profile in which Teams was installed on the figurer.

    • Command line: Run the following command.

                            msiexec /passive /x <path_to_msi> /l*v <uninstall_logfile_name>

      This procedure uninstalls Teams from the %ProgramFiles(x86)% folder or %ProgramFiles% folder, depending on the operating organisation environment.

Teams on VDI performance considerations

In that location are a diversity of virtualized setup configurations, each with a different focus for optimization. For case, a configuration might focus on user density. When planning, consider the post-obit to help optimize your setup based on your organization's workload needs.

  • Minimum requirement: Some workloads might require a setup using resources that are higher up the minimum requirements. For instance, workloads for developers who use applications that demand more than calculating resource.
  • Dependencies: These include dependencies on infrastructure, workload, and other environmental considerations outside the Teams desktop app.
  • Disabled features on VDI: Teams disables GPU-intensive features for VDI, which can assistance ameliorate transient CPU utilization. The following features are disabled:
    • Teams CSS animation
    • Giphy auto-start

Teams on VDI with calling and meetings

In add-on 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 post-obit diagram provides an overview of the architecture.

Diagram showing Teams on VDI architecture.

Important

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

Network requirements

We recommend that you evaluate your environment to identify any risks and requirements that tin influence your overall deject voice and video deployment. Utilise the Skype for Business concern Network Assessment Tool to test whether your network is ready for Teams.

To learn more most how to prepare your network for Teams, see Prepare your organization'southward network for Teams.

Migrate from Skype for Business concern on VDI to Teams on VDI

If yous're migrating from Skype for Business on VDI to Teams on VDI, besides the differences betwixt the two applications, in that location are some differences when VDI is also implemented. Some capabilities that aren't currently supported in Teams VDI that are in Skype for Business VDI are as follows:

  • Per-platform policy to disable some AV features in VDI
  • Give and take control when app sharing
  • Screen share from chat without audio
  • Simultaneous video and screen sharing send and receive

Teams on Chrome browser versus Teams desktop app for VDI

Teams on Chrome browser doesn't provide a replacement for the Teams desktop app for VDI with AV optimization. The conversation and collaboration feel works as expected. When media is needed, there are some experiences that might non meet user expectations on the Chrome browser:

  • The audio and video streaming experience might not be optimal. Users might experience delays or reduced quality.
  • Device settings aren't available in browser settings.
  • Device management is handled through the browser and requires multiple settings in browser site settings.
  • Device settings might besides need to be set up in Windows device direction.

Teams on VDI with conversation and collaboration

If your organization wants to only utilise chat and collaboration features in Teams, you can set user-level policies to turn off calling and meeting functionality in Teams.

Set policies to turn off calling and coming together functionality

You can gear up policies by using the Teams admin center or PowerShell. Information technology up to a few hours for the policy changes to propagate. If y'all don't run across changes for a given business relationship immediately, try over again in a few hours.

Calling polices: Teams includes the congenital-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 congenital-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 surround.

Assign policies using the Teams admin eye

To assign the DisallowCalling calling policy and the AllOff meeting policy to a user:

  1. In the left navigation of the Teams admin center, go to Users.
  2. Select the user by clicking to the left of the user proper noun, and then click Edit settings.
  3. Practise the following:
    1. Nether Calling policy, click DisallowCalling.
    2. Under Meeting policy, click AllOff.
  4. Click Apply.

To assign a policy to multiple users at a time:

  1. In the left navigation of the Teams admin center, go to Users, and then search for the users or filter the view to show the users y'all want.
  2. In the ✓ (bank check mark) column, select the users. To select all users, click the ✓ (cheque mark) at the top of the table.
  3. Click Edit settings, make the changes that you want, and and so click Utilise.

Or, you can also exercise the following:

  1. In the left navigation of the Teams admin center, become to the policy you want to assign. For example:
    • Get to Voice > Calling policies, and then click DisallowCalling.
    • Go to Meetings > Meeting policies, and and then click AllOff.
  2. Select Manage users.
  3. In the Manage users pane, search for the user by brandish proper noun or past user proper name, select the name, and then click Add. Repeat this step for each user that yous want to add together.
  4. When you're finished adding users, click Save.

Assign policies using PowerShell

The following example shows how to use the Grant-CsTeamsCallingPolicy to assign the DisallowCalling calling policy to a user.

              Grant-CsTeamsCallingPolicy -PolicyName DisallowCalling -Identity "user e-mail id"

To learn more virtually using PowerShell to manage calling policies, run into Fix-CsTeamsCallingPolicy.

The post-obit example shows how to use the Grant-CsTeamsMeetingPolicy to assign the AllOff meeting policy to a user.

              Grant-CsTeamsMeetingPolicy -PolicyName AllOff -Identity "user email id"

To acquire more than about using PowerShell to manage meeting policies, encounter Set-CsTeamsMeetingPolicy.

Migrate Teams on VDI with chat and collaboration to optimize Teams with calling and meetings

If you accept an existing implementation of Teams on VDI with chat and collaboration in which you had set up user-level policies to plough off calling and meeting functionality, and yous're migrating to Teams with AV optimization, you must fix policies to turn on calling and meeting functionality for those Teams on VDI users.

Ready policies to plow on calling and meeting functionality

You can use the Teams admin center or PowerShell to set and assign calling and meeting policies to your users. Information technology tin can have some time (a few hours) for policy changes to propagate. If you lot don't see changes for a given account immediately, endeavor again afterward a few hours.

Calling polices: Calling policies in Teams control which calling features are bachelor to users. Teams includes the built-in AllowCalling calling policy, in which all calling features are turned on. To plough on all calling features, assign the AllowCalling policy. Or, create a custom calling policy to turn on the calling features that you want and assign it to users.

Meeting policies: Meeting policies in Teams command the types of meetings that users can create and the features that are available to meeting participants that are scheduled by users in your organisation. Teams includes the built-in AllOn coming together policy, in which all meeting features are turned on. To plow on all meeting features, assign the AllOn policy. Or, create a custom meeting policy to turn on the coming together features that you want and assign it users.

Assign policies using the Teams admin center

To assign the AllowCalling calling policy and the AllOn meeting policy to a user:

  1. In the left navigation of the Teams admin center, go to Users.
  2. Select the user by clicking to the left of the user proper name, and and then click Edit settings.
  3. Do the following:
    1. Under Calling policy, click AllowCalling.
    2. Under Meeting policy, click AllOn.
  4. Click Use.

To assign a policy to multiple users at a fourth dimension:

  1. In the left navigation of the Teams admin center, go to Users, and and then search for the users or filter the view to bear witness the users yous want.
  2. In the ✓ (check marker) column, select the users. To select all users, click the ✓ (bank check mark) at the top of the tabular array.
  3. Click Edit settings, make the changes that you want, and so click Apply.

Or, you can also practice the post-obit:

  1. In the left navigation of the Teams admin eye, go to the policy you lot want to assign. For example:
    • Become to Vocalisation > Calling policies, and then click AllowCalling.
    • Go to Meetings > Meeting policies, and so click AllOn.
  2. Select Manage users.
  3. In the Manage users pane, search for the user past display proper noun or by user name, select the name, and and so click Add. Repeat this step for each user that you desire to add.
  4. When you're finished adding users, click Relieve.

Assign policies using PowerShell

The following example shows how to use the Grant-CsTeamsCallingPolicy to assign the AllowCalling calling policy to a user.

              Grant-CsTeamsCallingPolicy -PolicyName AllowCalling -Identity "user email id"

To acquire more than nearly using PowerShell to manage calling policies, see Set-CsTeamsCallingPolicy.

The following case shows how to use the Grant-CsTeamsMeetingPolicy to assign the AllOn meeting policy to a user.

              Grant-CsTeamsMeetingPolicy -PolicyName AllOn -Identity "user email id"

To larn more most using PowerShell to manage meeting policies, see Set-CsTeamsMeetingPolicy.

Control fallback mode in Teams

When users connect from an unsupported endpoint, the users are in fallback mode, in which AV isn't optimized. You lot can disable or enable fallback mode by setting one of the following registry DWORD values:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\DisableFallback
  • HKEY_CURRENT_USER\SOFTWARE\Microsoft\Function\Teams\DisableFallback

To disable fallback manner, gear up the value to 1. To enable audio just, set the value to 2. If the value isn't present or is set to 0 (zero), fallback fashion is enabled.

This characteristic is bachelor in Teams version 1.3.00.13565 and later.

Disable audio and video settings for VDI

Teams VDI policies are available in the Teams module. These policies are active and enforced on non-optimized VDI environments.

  • New-CsTeamsVdiPolicy
  • Grant-CsTeamsVdiPolicy
  • Remove-CsTeamsVdiPolicy
  • Set up-CsTeamsVdiPolicy

Note

This is only for not-optimized environments.

Update a module name

              Update-Module -Proper noun MicrosoftTeams -AllowPrerelease  <# Import and connect to online (CSOnline runs the policies) #> Import-Module microsoftTeams if( -not $sess){     $session = New-CsOnlineSession     $pss = Import-PSSession $session } <# Cheque out the commands #> Get-Command -Noun *VDI* <#

Set policies to limit calling features

When users whose VDI DisableCallsAndMeetings policy is gear up to $true sign into Teams on VDI, they tin can't:

  • Make calls.
  • Bring together meetings.
  • Screen share from chat.

All types of calling should be disabled.

Note

This is merely for non-optimized environments.

              New-CsTeamsVdiPolicy -Identity DisableCallsAndMeetingsTrue -DisableCallsAndMeetings $true -DisableAudioVideoInCallsAndMeetings $fake  <# Assign policy #> $user = 'meganb@jvteams.xyz' Grant-CsTeamsVdiPolicy -Identity $user -PolicyName DisableCallsAndMeetingsTrue  <# Expect for some time until the policy is practical #> Get-CSOnlineUser -Identity $user | FL UserPrincipalName, *vdi*  <# Bear witness all policies #> Get-CsTeamsVdiPolicy | FT Iden*, Disable*

When users whose VDI DisableAudioVideoInCallsAndMeetings policy is set to $true sign in to Teams on VDI, they:

  • Tin can screen share from conversation.
  • Can join a meeting and share a screen and move their sound to a telephone.
  • Can't hold person-to-person audio and video calls from VDI.

Note

This is simply for not-optimized environments.

              $PolName = "DisableCallsAndMeetingsAV"  New-CsTeamsVdiPolicy -Identity $PolName -DisableCallsAndMeetings $false -DisableAudioVideoInCallsAndMeetings $true Grant-CsTeamsVdiPolicy -Identity $user -PolicyName $PolName  <# Look for some time until the policy is practical #> Get-CSOnlineUser -identity $user | FL UserPrincipalName, *vdi*  <# Cleanup later #> $cleanup = $fake if($cleanup){      "Doing cleanup"      # De-assign policy from user       Grant-CsTeamsVdiPolicy -Identity $user -PolicyName $null     Get-CSOnlineUser -identity $user | FL UserPrincipalName, *vdi*      # Remove policies     Get-CsTeamsVdiPolicy | ?{$_.identity -ne 'Global'} | remove-csTeamsVdiPolicy }

Known bug and limitations

Customer deployment, installation, and setup

  • With per-machine installation, Teams on VDI isn't automatically updated in the way that non-VDI Teams clients are. You accept to update the VM image by installing a new MSI as described in the Install or update the Teams desktop app on VDI section. You must uninstall the current version to update to a newer version.
  • In Citrix environments, if the user disconnects from the Virtual Machine while Teams is running, Teams updates can result in the user to be in a non-optimized state for AV when they reconnect. We recommend that users quit Teams earlier they disconnect from Citrix Virtual Machine to avoid this scenario.
  • Teams should be deployed either per user or per auto. Deployment of Teams for concurrent per user and per automobile is not supported. To migrate from either per motorcar or per user to 1 of these modes, follow the uninstall procedure and redeploy to either style.
  • Azure Virtual Desktop doesn't back up macOS and Linux-based clients at this time.
  • Fast tenant switch can effect in calling-related bug on VDI such equally screen sharing non available. Restarting the client will mitigate these issues.

Notifications

  • Message count notification and presence on the Windows taskbar is non supported on a Windows Server 2016 host.

Calling and meetings

The following calling and meeting features are not supported:

  • Any multi-window functionality similar the new coming together experiences or any functionality that comes with the new coming together experience
  • HID buttons and LED controls between the Teams app and devices for Citrix and VMware
  • Background mistiness and effects
  • Broadcast and live event producer and presenter roles
  • Location-Based Routing (LBR)
  • PSTN call ringback tone
  • Shared system sound/reckoner sound
  • Media bypass for Straight Routing
  • Zoom command

Annotation

Nosotros're working on calculation calling and meeting features that are currently only available in non-VDI environments. These might include more admin command over quality, boosted screen sharing scenarios, and advanced features recently added to Teams. Contact your Teams representative to larn more almost upcoming features.

The following are known issues and limitations for calling and meetings:

  • Interoperability with Skype for Business is express to audio calls; in that location is no video modality.
  • Incoming and approachable video stream resolution is limited to 720p resolution.
  • Simply one video stream from an incoming camera or screen share stream is supported. When there's an incoming screen share, that screen share is shown, instead of the video of the ascendant speaker.
  • Teams doesn't switch to utilise the last audio device that a user selected, if the device is disconnected, and and so reconnected.
  • Live events are not optimized.
  • Outgoing screen sharing:
    • Application sharing is not supported.
  • Requite control and take control:
    • Not supported during a screen sharing or awarding sharing session.
    • Supported during a PowerPoint sharing session.

For Teams known problems that aren't related to VDI, meet Support Teams in your system.

Troubleshooting

Troubleshoot Citrix components

Teams crashes or the Teams sign in screen is blank

This is a known consequence with Citrix VDA versions 1906 and 1909. To work effectually this issue, add the following registry DWORD value, and set it to 204 (hexadecimal).

                              HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_Dlls\SfrHook\Teams.exe

Then, restart VDA. To learn more, see this Citrix support article, Troubleshooting HDX optimization for Microsoft Teams.

  • Bulk install Teams using Windows Installer (MSI)
  • Teams PowerShell overview
  • Apply Microsoft Teams on Azure Virtual Desktop