Citrix Workspace Vdi

Citrix Workspace Vdi Download
Citrix Workspace Vdi
Citrix Workspace Vdi Login

-->

Citrix Virtual Apps and Desktops makes VDI intuitive and affordable and ensures that users have access to the apps they need to remain productive within today’s digital workspaces. Alongside Citrix Workspace, it can ensure the best possible VDI experience within the context of complex multi-device, multi-app workflows. 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 addition to chat and collaboration. A VDI desktop is a desktop running on a server in the datacenter that a user can access from virtually any device. To use VDI with Citrix, you need to purchase Citrix Virtual Apps and Desktop (formerly Citrix XenDesktop).

This article describes the requirements and limitations for 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 center. This enables a fully personalized desktop experience to users with a fully secured and compliant centralized source.

Microsoft Teams in a virtualized environment supports chat and collaboration. And with the Windows Virtual Desktop, Citrix, and VMware platforms, calling and meeting functionality is also supported.

Teams in a virtualized environment supports multiple configurations. These include VDI, dedicated, shared, persistent, and non-persistent modes. Features are in continuous development and are added on a regular basis, and functionality will expand in the coming months and years.

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 available in a virtualized environment, and video resolution might differ.

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

Note

For details about Teams VDI on different platforms, see Teams features by platform.

Teams on VDI components

Using Teams in a virtualized environment requires the following components.

Virtualization broker: The resource and connection manager to the virtualization provider, such as Azure
Virtual desktop: The Virtual Machine (VM) stack that runs Microsoft Teams
Thin client: The endpoint that the user physically interfaces with
Teams desktop app: The Teams desktop client 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 you consult your virtualization solution provider to ensure that you meet the minimum requirements.

Currently, Teams on VDI with audio/video (AV) optimization is certified with Windows 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 following platforms have virtual desktop infrastructure solutions for Teams.

Platform	Solution
Windows Virtual Desktop
Citrix Virtual Apps and Desktops
VMware Horizon

Windows Virtual Desktop

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

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 addition to chat and collaboration.

You can download the latest version of Citrix Virtual Apps and Desktops at the Citrix downloads site. (You'll need to sign in first.) 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 this 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 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.

You 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 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 this 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 you use a persistent or non-persistent setup and the associated functionality needs of your organization.

For a dedicated persistent setup, either approach would 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 is 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 is enabled. 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 endpoint must have access to the internet. If internet access isn't available at the thin client endpoint, optimization startup won't be successful. This means that the user is in a non-optimized media state.

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 8 It's important to understand the underlying non-uniform memory access (NUMA) configuration and configure your VMs accordingly.
RAM	4 GB	512 to 1024 MB per user
Storage	8 GB	40 to 60 GB

Non-persistent setup

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 box resources.

For a non-persistent setup, the Teams desktop app must be installed per-machine to the golden image. (To learn more, see the Install or update the Teams desktop app on VDI section.) 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 synched:

C:UsersusernameAppDataLocalMicrosoftIdentityCache (%localAppdata%MicrosoftIdentityCache)
C:UsersusernameAppDataRoamingMicrosoftTeams (%appdata%MicrosoftTeams)

Note

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. For example, FSLogix. Consult your caching manager provider for specific configuration instructions.

Teams cached content exclusion list for non-persistent setup

Exclude the following 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 folder
meeting-addinCache (%appdata%MicrosoftTeamsmeeting-addinCache)

Microsoft 365 Apps for enterprise considerations

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

New deployments of Teams through Microsoft 365 Apps for enterprise

Before you 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 learn more, see the Install or update the Teams desktop app on VDI section.

Teams deployments through Microsoft 365 Apps for enterprise updates

Teams is also being 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 use 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 learn more about Teams and Microsoft 365 Apps for enterprise, see How to exclude Teams from new installations of Microsoft 365 Apps for enterprise and Use Group Policy to control the installation of Teams.

Deploy the Teams desktop app to the VM

Download the Teams MSI package that matches your VDI VM operating system using one of the following links:
Note
For government clouds, see Install Microsoft Teams using Microsoft Endpoint Configuration Manager for the download links to the MSI files.
The minimum version of the Teams desktop app that's required is version 1.3.00.4461. (PSTN hold isn't supported in earlier versions.)
Install the MSI to the VDI VM by running one of the following commands:
- Per-user installation (default)
  This process is the default installation, which installs Teams to the %AppData% user folder. At this point, the golden image setup is complete. Teams won't work properly with per-user installation on a non-persistent setup.
- Per-machine installation
  This process installs Teams to the Program Files (x86) folder on a 64-bit operating system and to the Program Files folder on a 32-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.
  The next interactive logon session starts Teams and asks for credentials.
  Note
  These examples also use the ALLUSERS=1 parameter. When you set this parameter, Teams Machine-Wide Installer appears in Programs and Features in Control Panel and in Apps & features in Windows Settings for all users of the computer. All users can then uninstall Teams if they have admin credentials.It's important to understand the difference between ALLUSERS=1 and ALLUSER=1. The ALLUSERS=1 parameter can be used in non-VDI and VDI environments, while the ALLUSER=1 parameter is used only in VDI environments to specify a per-machine installation.
Uninstall the MSI from the VDI VM. There are two ways to uninstall Teams.
- PowerShell script: You can use this 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.
- Command line: Run the following command.
  This process uninstalls Teams from the Program Files (x86) folder or Program Files folder, depending on the operating system environment.

Teams on VDI performance considerations

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.

Minimum requirement: Some workloads might require a setup using resources that are above the minimum requirements. For example, workloads for developers who use applications that demand more computing resources.
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 help improve transient CPU utilization. The following features are disabled:
- Teams CSS animation
- Giphy auto-start

Teams on VDI with calling and meetings

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.

Important

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.

Network requirements

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

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

Migrate from Skype for Business on VDI to Teams on VDI

If you're migrating from Skype for Business on VDI to Teams on VDI, besides the differences between the two applications, there 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 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:

The audio and video streaming experience might not be optimal. Users might experiences 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 also need to be set in Windows device management.

Teams on VDI with chat and collaboration

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.

Set policies to turn off calling and meeting functionality

You can set policies by using the Microsoft Teams admin center or PowerShell. It might take some time (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.

Assign policies using the Microsoft Teams admin center

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

In the left navigation of the Microsoft Teams admin center, go to Users.
Select the user by clicking to the left of the user name, and then click Edit settings.
Do the following:
1. Under Calling policy, click DisallowCalling.
2. Under Meeting policy, click AllOff.
Click Apply.

To assign a policy to multiple users at a time:

In the left navigation of the Microsoft Teams admin center, go to Users, and then search for the users or filter the view to show the users you want.
In the ✓ (check mark) column, select the users. To select all users, click the ✓ (check mark) at the top of the table.
Click Edit settings, make the changes that you want, and then click Apply.

Or, you can also do the following:

In the left navigation of the Microsoft Teams admin center, go to the policy you want to assign. For example:
- Go to Voice > Calling policies, and then click DisallowCalling.
- Go to Meetings > Meeting policies, and then click AllOff.
Select Manage users.
In the Manage users pane, search for the user by display name or by user name, select the name, and then click Add. Repeat this step for each user that you want to add.
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.

To learn more about using PowerShell to manage calling policies, see Set-CsTeamsCallingPolicy.

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

To learn more about using PowerShell to manage meeting policies, see Set-CsTeamsMeetingPolicy.

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

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.

Set policies to turn on calling and meeting functionality

You can use the Microsoft 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.

Calling polices: Calling policies in Teams control which calling features are available to users. Teams includes the built-in AllowCalling calling policy, in which all calling features are turned on. To turn 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 control the types of meetings that users can create and the features that are available to meeting participants that are scheduled by users in your organization. Teams includes the built-in AllOn meeting policy, in which all meeting features are turned on. To turn on all meeting features, assign the AllOn policy. Or, create a custom meeting policy to turn on the meeting features that you want and assign it users.

Assign policies using the Microsoft Teams admin center

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

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

To assign a policy to multiple users at a time:

In the left navigation of the Microsoft Teams admin center, go to Users, and then search for the users or filter the view to show the users you want.
In the ✓ (check mark) column, select the users. To select all users, click the ✓ (check mark) at the top of the table.
Click Edit settings, make the changes that you want, and then click Apply.

Or, you can also do the following:

In the left navigation of the Microsoft Teams admin center, go to the policy you want to assign. For example:
- Go to Voice > Calling policies, and then click AllowCalling.
- Go to Meetings > Meeting policies, and then click AllOn.
Select Manage users.
In the Manage users pane, search for the user by display name or by user name, select the name, and then click Add. Repeat this step for each user that you want to add.
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 AllowCalling calling policy to a user.

To learn more about using PowerShell to manage calling policies, see Set-CsTeamsCallingPolicy.

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

To learn more about 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 can disable or enable fallback mode by setting one of the following registry DWORD values:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftTeamsDisableFallback
HKEY_CURRENT_USERSOFTWAREMicrosoftOfficeTeamsDisableFallback

To disable fallback mode, set the value to 1. To enable audio only, set the value to 2. If the value isn't present or is set to 0 (zero), fallback mode is enabled.

This feature is available in Teams version 1.3.00.13565 and later.

Known issues and limitations

Client 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 have 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 before they disconnect from Citrix Virtual Machine to avoid this scenario.
Teams should be deployed either per user or per machine. Deployment of Teams for concurrent per user and per machine is not supported. To migrate from either per machine or per user to one of these modes, follow the uninstall procedure and redeploy to either mode.
Windows Virtual Desktop and VMware don't support MacOS and Linux-based clients at this time.

Calling and meetings

The following calling and meeting features are not supported:

Any multi-window functionality like the new meeting experiences or any functionality that comes with the new meeting experience
Enhanced emergency services
HID buttons and LED controls between the Teams app and devices
Background blur and effects
Broadcast and live event producer and presenter roles
Location-Based Routing (LBR)
Call park
Call queue
Shared system audio/computer sound
Media bypass for Direct Routing
Zoom control

Note

We're working on adding calling and meeting features that are currently only available in non-VDI environments. These might include more admin control over quality, additional screen sharing scenarios, and advanced features recently added to Teams. Contact your Teams representative to learn more about upcoming features.

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

Interoperability with Skype for Business is limited to audio calls; there is no video modality.
Only a single incoming video stream is supported in meetings or group calls. When multiple people send video, only the dominant speaker's video is shown at any given time.
Incoming and outgoing video stream resolution is limited to 720p resolution. This is a WebRTC limitation.
Only 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 dominant speaker.
Teams doesn't switch to use the last audio device that a user selected, if the device is disconnected, and then reconnected.
Outgoing screen sharing:
- Application sharing is not supported.
Give control and take control:
- Not supported during a screen sharing or application sharing session.
- Supported during a PowerPoint sharing session.
Citrix-only limitations
- When screen sharing in a multi-monitor setup, only the main monitor is shared.
- High DPI scaling on CWA is not supported.

For Teams known issues that aren't related to VDI, see Support Teams in your organization.

Troubleshooting

Troubleshoot Citrix components

Teams crashes or the Teams sign in screen is blank

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

HKEY_LOCAL_MACHINESOFTWARECitrixCtxHookAppInit_DllsSfrHookTeams.exe

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

Citrix Workspace Vdi Download

HDX RealTime Webcam Video Compression is not directly dependent on specific models of webcams. Any webcam that is DirectShow compatible (including integrated ones) can be used with HDX RealTime Webcam Video Compression. Most Windows Driver Model (WDM) compatible webcams can be used. However, webcam bandwidth consumption can vary from webcam to webcam. Different webcams offer different frame rates and have different levels of brightness and contrast. Citrix used the following webcams for initial feature validation:

Microsoft LifeCam VX models (2000, 3000, 5000, 7000)
Creative LIVE! CAM Optia Pro
Logitech QuickCam Messenger
Logitech C600, C920
HP Deluxe Webcam

Adjusting the contrast of the webcam can reduce upstream traffic significantly. This can be accomplished if the webcam ships with a system tray utility that runs on the user device. Oppo others driver download for windows 10.

6. Known Issues

Caution! Download olimex usb devices driver. Refer to the Disclaimer at the end of this article before using Registry Editor.

If Citrix GoToMeeting with HDFaces or Skype for Business (either hosted or when in fallback mode with RTOP) does not recognize the webcam of the user, edit the system registry.
For 32-bit devices, access HKEY_CLASSES_ROOTCLSID{860BB310-5D01-11d0-BD3B-00A0C911CE86}InstanceCitrix HDX Web Camera.
For 64-bit devices, access HKEY_CLASSES_ROOTWow6432NodeCLSID{860BB310-5D01-11d0-BD3B-00A0C911CE86}InstanceCitrix HDX Web Camera.
Add a string value named DevicePath.
Set REG_SZ as the data type and Citrix Client as the value [Reference 263277].
HDX RealTime Webcam Video Compression does not automatically reconnect if the session connection is interrupted mid-conference. The user must restart the video conference [Reference 233296].
On XenApp 7.17 or older (Windows Server VDA) with Receiver for Windows 4.11 or older, only one webcam can be used with HDX RealTime Webcam Video Compression at a time; if the client device has multiple webcams configured, only the first one successfully detected is used in the XenApp session.
XenApp 7.18 and Receiver for Windows 4.12 added support for multiple webcams when connecting to Windows Server VDAs. Applications dynamically detect a webcam being plugged in or removed on the client. Users don't have to restart the application to detect these changes.
On XenDesktop (VDI), multiple webcams are supported, along with client-side webcam switching.
Linux Receiver / Workspace app does not support multiple webcam enumeration when the VDA is a Windows Server. Only the default camera is enumerated.
In XenApp 7.18 or higher, actual webcam names are displayed instead of the generic Citrix HDX Camera (which is the way they are still displayed in 7.15 LTSR, for example).

Double Hops:

Xenapp 7.15 LTSR and double hops - [internal ref. LD1143] when installing Citrix Receiver 4.10 or higher, or any version of Citrix Workspace app in the VDA, webcam functionality will break if H264 encoding is used. Only Citrix Receiver for Windows 4.9 LTSR can be installed in a 7.15 VDAs for H264 encoding. This is because both Receiver/Workspace app and the VDA rely on (and are packed with) the same codec library (CtxVideoCodec.dll), and installing Receiver/Workspace app in the VDA will overwrite the dll of the 7.15 VDA with a newer version. As a work-around (if you must install 4.10+ or Workspace app in the VDA), you can try to disable H.264 encoding, and enable Theora using the following registry setting (on the client or on the VDA)

i. HKEY_CURRENT_USERSoftwareCitrixHDXRealTime
DWORD EnableDeepcompress_Client – set it to 0 to disable H.264 encoding (and use Theora instead). By default HDX always prefer H.264. Set it to 1 to go back to H264 default behavior.
ii. If you want to disable H264 on the VDA side instead, it is also possible by setting:
HKLMSoftware Wow6432NodeCitrixHDXRealTime
DWORD EnableDeepcompress_Server – set it to 0 to disable H.264 support.
Please note that when H.264 is disabled, the webcam resolution must be integral multiple of 16. So, 1920*1080 is not supported. User can use other resolution like 1280*720, so apply the defaultwidth and defaultheight regkeys described in 7.1

HDX RealTime Webcam Video Compression supports ICA double-hop for webcams.

7. Advanced Configuration

High Definition
In XenDesktop 7.16 and XenApp 7.18 VDAs (with Receiver for Windows 4.10 or higher) support was added for native resolutions beyond 352x288 (CIF).
This enhancement allows high-def webcam native resolutions for virtual sessions, up to 1080p.
Citrix Receiver now queries the webcams on the client for their list of supported capabilities (media type information and resolutions). Then, the HDX PnP virtual channel is used to send this information to the VDA. Server will then offer this list to the hosted application trying to use the webcam.
Media types that aren’t supported will be filtered out and not offered to the application.
At the moment, HDX supports the RGB formats, YUV420 formats and YUY2 packed formats.
Application running on the VDA picks the desired media type and resolution from the list that was offered.
(If for some reason this media type negotiation fails, HDX falls back to our legacy way of webcam redirection, which is to use hard coded 352x288 CIF resolution).
The selected media type and resolution is then sent to the client and the webcam uses that to start the webcam feed.
The existing registries keys on the client to control the resolution will be honored, and this mechanism can be utilized to enforce a given resolution (see section 7.1 below).
If Bandwidth consumption is a concern, High Definition can be disabled by applying the following registry key (either on the VDA or Client):

On the VDA	Or on the Client/Workspace App
HKLMSoftwareCitrixHDXRealTime Name: Enable_HighDefWebcam Type: REG_DWORD Data: 0 = Disable the high definition webcam streaming	HKCUSoftwareCitrixHDXRealTime Name: Disable_HighDefWebcam Type: REG_DWORD Data: 1 = Disable the high definition webcam streaming

7.1 Resolution

As of XenApp 7.18 and XenDesktop 7.17 (with Receiver for Windows 4.10 or higher), all supported resolutions by the webcam are presented to the hosted app trying to access it, so it can pick the desired resolution.
By default, Citrix Receiver for Windows 4.10 or older and non-Windows Receivers use CIF resolution (352 x 288) to stream webcam video to the XenApp/XenDesktop host.
A scaling function allows applications to request resolutions other than the default. The CIF frames are scaled appropriately on the VDA before delivering them to the application.
To manually adjust (and force) the webcam video resolution, create (on the Client) under HKEY_CURRENT_USERSoftwareCitrixHDXRealTime two DWORD values named

DefaultWidth
DefaultHeight

The resolution directly affects the bandwidth consumed and the overall quality of the video.
Some Webcams (specially integrated) might not support CIF, and Webcam detection might fail on an older VDA (like 7.15 LTSR).
Editing the Registry for a known supported resolution (like 640 x 480 or 1280 x 720) might fix the issue.
Note that the higher the resolution, the higher the bandwidth consumption between Workspace app and the VDA.
Try a lower known supported resolution (e.g. 480p) to avoid high network traffic.
You can find this by launching the Camera app in Windows 10 and clicking on Settings:
Client-side registry:

7.2 Frame Rate

The preferred video frame rate can be adjusted by creating (on the Client) a DWORD (32-bit) value named FramesPerSecond under HKEY_CURRENT_USERSoftwareCitrixHDXRealTime. Because it is possible to input a value that the webcam does not support (e.g 31 FPS), the actual frame rate might be different as seen by the hosted application (e.g. 10 FPS). When this key is not present, a default value of 15 frames per second is selected. The actual frame rate used is dependent upon the Webcam.
For example, an old WebCam device might only support up to 10 fps in 1280*720 resolution for I420, NV12, YV12, YUY2 video format (the formats supported in H.264 encoding, plus RGB with Theora encoding). To confirm this, use a third-party tool (like DumpVCap or GraphStudioNext) to verify.

Citrix Workspace Vdi

--DumpVcap output--

Major Type Sub Type Format Type FixedSamples Temporal Compression Sample Size Max Input Size Min Output Size Max Output Size Min-Max FPS

Video YUY2 VideoInfo Fixed NotTemporal 1843200 1280x720 1280x720 1280x720 5.00-10.00 {none}
Video YUY2 VideoInfo2 Fixed NotTemporal 1843200 1280x720 1280x720 1280x720 5.00-10.00 {none}
Video MJPG VideoInfo Fixed NotTemporal 2764800 1280x720 1280x720 1280x720 5.00-30.00 {none}
Video MJPG VideoInfo2 Fixed NotTemporal 2764800 1280x720 1280x720 1280x720 5.00-30.00 {none}

From the output, it is clear that at 1280*720 resolution, the WebCam device can support 5~10 fps for YUY2 video format and 5~30 fps for MJPG video format (but not supported in HDX). In this case, only up to 10FPS can be used by the hosted app.
Most modern webcams like the integrated ones in a Surface device (e.g. OV5693) support at least 640x480 (480p 4:3) or 640x360 (wide 360p 16:9) and 15-30 FPS (see SETTINGS screenshot above).

7.3 Bandwidth

The bandwidth usage can be tweaked by creating a client-side DWORD (32-bit) value named TargetBitrate under HKCUSoftwareCitrixHDXRealTime. Values are in bits per second, so if 300 kbps is desired, the value should be set to 300000. When this key is not present, the default value is 350000.
During testing, somewhere between 250000 and 300000 was found to be the minimum values for the default CIF (352x288) resolution or 480p that still produced acceptable video quality. If the resolution and frame rate are set to lower values then it might be possible to lower the bit rate and reduce bandwidth consumption. Lastly, setting the bit rate to zero has special meaning – zero indicates that the codec should operate in VBR mode.
However, during production testing, the codec would generate excessive video artifacts so VBR mode is NOT recommended.

7.4 Encoders

Citrix Workspace app for Windows supports H.264 (Default) and Theora (legacy) encoders. If for whatever reason you want to disable H264 (not recommended), the following registry key on either VDA or the client can be used:

On the VDA	Or on the Client
HKLMSoftwareWow6432NodeCitrixHdxRealTime Or HKLMSoftwareCitrixHdxRealTime DWORD EnableDeepcompress_Server – set it to 0 to disable H.264 support.	HKCUSoftwareCitrixHdxRealTime DWORD EnableDeepcompress_Client – set it to 0 to disable H.264 encoding. By default HDX always prefer H.264 decoding. Set it to 1 to go back to default behavior.

8. Troubleshooting
8.1. Device Manager on the Client would list the same webcam names as done by the Citrix Workspace app Desktop Viewer. Although keep in mind that there is no single designated place where they show inside Device Manager. This is device specific. Most common place is under Imaging Devices. Integrated webcams might show in other places (e.g. Device Manager/System devices)
8.2. Citrix Workspace app Desktop Viewer preferences should list all the available webcams on the client. If that drop down does not show webcams at all, that means the Client cannot access the locally attached webcams

In this scenario, redirection will not work. If you run into this problem, try launching apps like Skype for Business, Skype or GoToMeeting LOCALLY to confirm that webcam devices are not available on the endpoint either.
This can happen because of various reasons, most commonly device drivers not installed correctly because of which Windows cannot recognize webcams.
For HDX Realtime webcam video compression, the device drivers are not needed on the VDA, only on the Client.
For Generic USB redirection, drivers are needed at both the VDA and on the Client machine.
Important : in some cases, integrated webcams like in a Surface Book will not show in Desktop Viewer preferences. This does not mean they cannot be redirected.
8.3. Make sure the following Computer policies 'Windows media Redirection' and 'Multimedia Conferencing' are Enabled in Studio.
By default, all multimedia policies explicitly set on the Controller are stored in these registries:

Computer policies:
HKEY_LOCAL_MACHINESoftwarePoliciesCitrixMultimediaPolicies

User policies:
HKEY_LOCAL_MACHINESoftwarePoliciesCitrix{User Session ID}UserMultimediaPolicies
To locate the current user session ID, issue the qwinsta command on the Windows command line.
Keep in mind that these two policies are Enabled by default, and policies that are enabled by default will not show under those regkeys (only policies that are explicitly configured will).

8.4. Once you plug a webcam in your session, or if the webcam was already plugged when the session started,
the following registry entries should be seen on the VDA:
Information on the MediaPropertyData values can be found here.
8.5 If some apps on the VDA can display the webcam, but some other app or self-preview window shows a black or grey screen instead of the video feed, you might need to whitelist the application. This applies to Workstation VDAs only (Windows 10 / Windows 7).
Add a key with the name of your app executable (e.g. myapp.exe) under:

HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrixCtxHookAppInit_DllsCtxMFPlugin
and
HKEY_LOCAL_MACHINESOFTWARECitrixCtxHookAppInit_DllsCtxMFPlugin

DWORD “HookProcess” = 1

After editing this key, a VDA reboot is required.

Disclaimer

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Platform	Version	Comments
Workspace app for Windows	Any	Both 32 and 64-bit apps in the VDA as long as the VDA is 7.17 or higher, otherwise only 32-bit
Receiver for Windows	4.9 (any CU)	Only 32-bit apps in the VDA
Workspace app for MAC	Any	Both 32 and 64-bit apps in the VDA as long as the CWA is 2006 or higher and the VDA is 7.17 or higher, otherwise only 32-bit
Workspace app for Linux	Any	Only for 32-bit apps in the VDA
Workspace app for Chrome	Any	Some ARM Chromebooks don't support H.264 encoding - in that case, only 32-bit apps in the VDA can use the optimized HDX RealTime Webcam Video Compression

What is VDI?

Teams on VDI components

Teams on VDI requirements

Virtualization provider requirements

Platforms certified for Teams

Windows Virtual Desktop

Citrix Virtual Apps and Desktops requirements

VMware Horizon Workspace and Desktop requirements

Install or update the Teams desktop app on VDI

Dedicated persistent setup

Non-persistent setup

Teams cached content exclusion list for non-persistent setup

Microsoft 365 Apps for enterprise considerations

New deployments of Teams through Microsoft 365 Apps for enterprise

Teams deployments through Microsoft 365 Apps for enterprise updates

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

How to exclude Teams deployment through Microsoft 365 Apps for enterprise

Deploy the Teams desktop app to the VM

Teams on VDI performance considerations

Teams on VDI with calling and meetings

Network requirements

Migrate from Skype for Business on VDI to Teams on VDI

Teams on Chrome browser versus Teams desktop app for VDI

Teams on VDI with chat and collaboration

Set policies to turn off calling and meeting functionality

Assign policies using the Microsoft Teams admin center

Assign policies using PowerShell

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

Set policies to turn on calling and meeting functionality

Assign policies using the Microsoft Teams admin center

Assign policies using PowerShell

Control fallback mode in Teams

Known issues and limitations

Client deployment, installation, and setup

Calling and meetings

Troubleshooting

Troubleshoot Citrix components

Teams crashes or the Teams sign in screen is blank

Related topics

1. Background

2. HDX RealTime Webcam Video Compression

3. HDX Generic USB Redirection

4. Default Behavior

4.1 Whether to use Webcam Video Compression or Generic USB Redirection

4.2 Configuring HDX RealTime Webcam Video Compression

4.3 Dependency on Windows Media Redirection

5. Webcam Compatibility

Citrix Workspace Vdi Download

6. Known Issues

7. Advanced Configuration

7.1 Resolution

7.2 Frame Rate

Citrix Workspace Vdi

7.3 Bandwidth

7.4 Encoders

Citrix Workspace Vdi Login

Disclaimer