Microsoft Teams Citrix Vdi

  
  1. Microsoft Teams In Citrix Vdi
  2. Microsoft Teams For Citrix Vdi Download
  3. Microsoft Teams Citrix Vdi Free
  4. Microsoft Teams For Vdi
  5. Ms Teams On Citrix
  6. Citrix Vdi And Microsoft Teams
  7. Teams And Vdi

Chapter 4: The long-awaited optimization for Microsoft Teams on Windows Virtual Desktop – A/V Redirect. This morning I was wondering, when I saw multiple people post that the A/V Redirect feature will be available from today. They provided with a link from Microsoft, where to download this feature. Microsoft Teams chat and collaboration has been supported in VDI for a long time, and now with the Citrix platform, calling and meeting functionality are also supported. Audio, video and sharing are handled via WebRTC on the Citrix platform. VDA-side HDX services use an API to interface with the Microsoft Teams hosted app to receive commands.

Learn how to use Microsoft Teams Optimization for Citrix. Citrix Virtual Apps and Desktops, along with Citrix SD-WAN, can optimize Microsoft Teams and provide a great user experience.

Now organizations can centrally deploy Microsoft Teams within their virtual environments and deliver a fully-featured Microsoft Teams experience, but also giving IT admins the benefits of centralized management.

Citrix delivers optimization for desktop-based Microsoft Teams using Citrix Virtual Apps and Desktops and Citrix Workspace app. By default, we bundle all the necessary components into Citrix Workspace app and the Virtual Delivery Agent (VDA). ( Microsoft Teams Optimization with Citrix )

Our optimization for Microsoft Teams contains VDA-side HDX services and API to interface with the Microsoft Teams hosted app to receive commands. These components open a control virtual channel (CTXMTOP) to the Citrix Workspace app-side media engine. The endpoint decodes and renders the multimedia locally. Reverse seamless snaps-in the local Citrix Workspace app window back into the hosted Microsoft Teams app.

Authentication and signaling occurs natively on the Microsoft Teams-hosted app, just like the other Microsoft Teams services (for example chat or collaboration). Audio/video redirection doesn’t affect them.

CTXMTOP is a command and control virtual channel. That means that media is not exchanged between the Citrix Workspace app and the VDA.

Only Client-fetch/client-render is available.

Microsoft teams citrix support

Microsoft Teams installation

To start using Microsoft Teams Optimization for Citrix. Citrix recommends you to follow the Microsoft Teams machine-wide installation guidelines and avoid using the .exe installer that installs Teams in Appdata. Instead, install in C:Program Files (x86)MicrosoftTeams by using the ALLUSER=1 flag from the command line. In this mode, the Teams application doesn’t auto-update whenever there is a new version. We recommend this mode for non-persistent environments. For more information, see Install Microsoft Teams using MSI (VDI Installation section).

If you have dedicated persistent VDI environments and you want the Teams application to auto-update and would prefer Teams to install per-user under Appdata/Local, use the .exe installer or the MSI without ALLUSER =1.

If using Citrix App Layering to manage VDA and Microsoft Teams installations in different layers, deploy this registry key on Windows before installing Teams with ALLUSER =1:

HKEY_LOCAL_MACHINESOFTWARECitrix

Or

HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrix

Create an empty registry key named PortICA (leave the default Name, Type, and Data).

Profile Management recommendations

When the ALLUSER =1 flag is passed to the MSI from the command line, the Teams app installs under C:Program Files (~300 MB). The app uses AppDataLocal for logs and AppDataRoamingMicrosoftTeams for user specific configurations, caching of elements in the user interface, and so forth.

System requirements

Minimum version – Delivery Controller (DDCs) 1906.2:

Supported operating systems:

  • Windows Server 2019, 2016, 2012R2 Standard and Datacenter Editions, and with the Server Core option

Minimum version – Virtual Delivery Agents (VDAs) 1906.2:

Supported operating systems:

Teams
  • Windows 10 64-bit, minimum versions 1607 up to 1909.
  • Windows Server 2019, 2016, and 2012 R2 (Standard and Datacenter Editions).

Requirements:

  • BCR_x64.msi – the MSI that contains the Microsoft Teams optimization code and starts automatically from the GUI. If you’re using the command line interface for the VDA installation, don’t exclude it.

Microsoft Teams In Citrix Vdi

Recommended version – Citrix Workspace app 2002 for Windows and Minimum version – Citrix Workspace app 1907 for Windows:

  • Windows 7, 8, and 10 (32-bit and 64-bit editions, including Embedded editions)
  • Windows 10 IoT Enterprise 2016 LTSB (v1607) and 2019 LTSC (v1809)
  • Endpoint requirement: Approximately 2.2–2.4 GHz dual core CPU that can support 720p HD resolution during a peer-to-peer video conference call.
  • Dual or quad-core CPUs with lower base speeds (~1.5 GHz) equipped with Intel Turbo Boost or AMD Turbo Core that can boost up to at least 2.4 GHz.
  • HP Thin Clients verified: t630/t640, t730/t740, mt44/mt45.
  • Dell Thin Clients verified: 5070, 5470 Mobile TC.
  • 10ZiG Thin Clients verified: 4510 and 5810q.
  • For a complete list of verified endpoints, see Thin Clients.
  • Citrix Workspace app requires a minimum of 600 MB free disk space and 1 GB RAM.
  • Microsoft .NET Framework minimum requirement is version 4.6.2. Citrix Workspace app automatically downloads and installs .NET Framework if it is not present in the system.

Enable optimization of Microsoft Teams

Teams vdi download

To enable optimization for Microsoft Teams, use the Studio policy described in Microsoft Teams redirection policy (it is ON by default). In addition to this policy being enabled, HDX checks to verify that the version of Citrix Workspace app is equal to or greater than the minimum required version. If you enabled the policy and the Citrix Workspace app version is supported, the HKEY_CURRENT_USERSoftwareCitrixHDXMediaStreamMSTeamsRedirSupport registry key is set to 1 automatically on the VDA. The Microsoft Teams application reads the key to load in VDI mode.

If you click About > Version, the Optimized for Citrix legend displays

Premium crossover rental car. If you don’t see Optimized for Citrix, exit Teams by right clicking on the notification area icon and restart.

Citrix HDX Optimization for Microsoft Teams

Microsoft Teams For Citrix Vdi Download

These components are by default, bundled into Citrix Workspace app and the Virtual Delivery Agent (VDA)

Call Flow

  1. Launch Microsoft Teams.
  2. Teams authenticates to O365. Tenant policies are pushed down to the Teams client, and relevant TURN and signaling channel information is relayed to the app.
  3. Teams detects that it is running in a VDA and makes API calls to the Citrix JavaScript API.
  4. Citrix JavaScript in Teams opens a secure WebSocket connection to WebSocketService.exe running on the VDA (127.0.0.1:9002). WebSocketService.exe runs as a Local System account on session 0. WebSocketService.exe performs TLS termination and user session mapping, and spawns WebSocketAgent.exe, which now runs inside the user session.
  5. WebSocketAgent.exe instantiates a generic virtual channel by calling into the Citrix HDX Browser Redirection Service (CtxSvcHost.exe).
  6. Citrix Workspace app’s wfica32.exe (HDX engine) spawns a new process called HdxTeams.exe, which is the new WebRTC engine used for Teams optimization.
  7. HdxTeams.exe and Teams.exe have a 2-way virtual channel path and can start processing multimedia requests.—–User calls——
  8. Peer A clicks the call button. Teams.exe communicates with the Teams services in Azure establishing an end-to-end signaling path with Peer B. Teams asks HdxTeams for a series of supported call parameters (codecs, resolutions, and so forth, which is known as a Session Description Protocol (SDP) offer). These call parameters are then relayed using the signaling path to the Teams services in Azure and from there to the other peer.
  9. The SDP offer/answer (single-pass negotiation) and the Interactive Connectivity Establishment (ICE) connectivity checks (NAT and Firewall traversal using Session Traversal Utilities for NAT (STUN) bind requests) complete. Then, Secure Real-time Transport Protocol (SRTP) media flows directly between HdxTeams.exe and the other peer (or O365 conference servers if it is a Meeting).

Nowadays security and compliance are at the forefront of many companies concerns. For organizations with these issues they typically look to virtualize some of their environment. To cater to those needs, Microsoft has recently made VDI available for Microsoft Teams. In this article I will be discussing some of the key features, limitations, and offerings for this up and coming solution for Microsoft Teams if your organization chooses to go this route. One important thing to consider that as of the time of this writing Teams has not been optimized to access or use the audio or video devices on the user’s local devices (without additional software).

Note: Working in a VDI environment will usually have challenges related to multimedia scenarios such as calling, video calling, screen sharing, app sharing, co-authoring, and more.

Your organization can choose to run Teams fully in VDI (using either the Web App or Desktop Client) but it is recommended that the following policies be turned off, so users don’t have a poor experience in a virtualized environment.

  • Policies recommended to be disabled:
    • Calling – Controls whether the Calling app is available in the left rail on the Teams client or not. Also control whether users see Calling and Video Call options in private chat.
      • It is recommended to set this to FALSE to remove the Calling app from the left rail and to remove Calling and Video Call options in private chat.
    • Meetings – The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users.
      • For the specific policy names and recommended values, please check out the list here.

Known Limitations

Other than the audio and video limitations that we mentioned earlier, there are some additional limitations your organization may face:

  • Joining meetings created by others. Even though the above policies restrict users from creating meetings, they will still be able to join meetings sent out by other users. Within these meetings, their ability to share video, use WhiteBoard and other features will depend on whether the admin disabled them or not.
  • Issues related to cached content. If the virtual environment that Teams is running in is not persisted (data is cleaned up at the end of each user session), users might notice performance degradation due to the client having to re-download all content again, regardless of whether the given user accessed the same content in a previous session. This performance impact can be mitigated by using roaming cache solutions, such as those provided by FSLogix.

Microsoft Teams Citrix Vdi Free

The Essential Guide to Microsoft Teams End-User Engagement

Microsoft Teams For Vdi

We take you through 10 best practices, considerations, and suggestions that can enrich your Microsoft Teams deployment and ensure both end-user adoption and engagement.

Ms Teams On Citrix

Once Teams has been optimized for use within Virtual Desktop environments, admins can revert these policies and allow users to use Teams as they normally would.

Similar to the HDX RealTime Optimization Pack offered for Skype for Business Server 2015, Citrix is currently working on a similar plugin for Teams desktop app. As Citrix mentions, this virtualization plugin will be very similar to the one offered for Skype for Business Server 2015. The currently layout for the Citirix HDX RealTime Optimization pack is as follows:

Citrix Vdi And Microsoft Teams

  1. A VDA-side HDX component will interface with the Teams hosted app and receive commands,
  2. Then it will open a control virtual channel to a Citrix Workspace app-side media engine and let the multimedia be rendered locally by the endpoint
  3. Reverse seamless will snap-in the local Citrix Workspace App window back into the hosted Teams app
  4. Authentication and signalling will happen natively on the Teams-hosted app, just like the other Teams services (e.g. chat or collaboration). They will not be affected by the audio/video redirection.
  5. As always, client-fetch/client-render and server-fetch/client-render (in case your endpoints don’t have internet access, thanks to a media relay virtual channel) are going to be available. And of course, there will be support for HID Devices and any endpoint (Windows, Mac and Linux).

Teams And Vdi

In terms of the Teams Web App on VDI, you can expect it to support audio, video, and desktop sharing using WebRTC for multimedia (so that means no browser plugins required!). Citrix has stated they also intend on supporting BCR (Browser Content Redirection). This will allow you to redirect an entire website to the endpoint for local rendering. This feature is intended to be released sometime this quarter (Q3 2018) for XenApp and XenDesktop by enhancing BCR to support WebRTC redirection. For the full blog post on this check it out here. I hope you have found this quick overview of what Microsoft VDI brings to the table useful. Stay tuned, as I have more exciting news on Teams and Skype for Business coming out shortly!