Transitioning from Microsoft Classic Teams to Teams 2.1 is a significant milestone for many organizations. Whether it’s an on-premises CVAD installment or Citrix DaaS installment, the shift is inevitable. On October 5th, 2023, Microsoft released a blog outlining the details for both client-based Teams and Teams for VDI. Their aim was to reduce the footprint of the classic Teams, enabling Teams 2.1 to operate two times faster while using 50% less memory. As of June 30th, 2024, Microsoft Classic Teams for VDI will no longer be available, marking a crucial turning point. We recognize the challenges this change can pose as customers navigate various platforms. At this pivotal juncture, our commitment to providing robust onboarding for Teams 2.1 becomes paramount. We understand the importance of ensuring a smooth migration process for our customers and acknowledging the complexities they may encounter.

The compatibility of Microsoft Teams 2.1 with Citrix Microsoft Teams Optimization using WebRTC (VDI 1.0) virtual channel is a testament to the collaborative efforts between Microsoft and Citrix. This optimization channel is set to receive an updated channel to use in the near future, underscoring the dedication to providing ongoing support and compatibility for profile solutions. The new Teams is currently operating on WebRTC (VDI 1.0) and provides a great user experience. Here at Choice Solutions, we have spent many hours working with Citrix to fine-tune Teams 2.1 with Citrix Profile management solutions, as well as FSLogix profile solutions.

This blog post aims to provide a comprehensive understanding of Teams 2.1 for Citrix, Virtual Apps, and Desktops/Citrix DaaS. Offering insights and guidance for those embarking on their Teams 2.1 journey. While it won’t serve as a step-by-step deployment guide, it will provide valuable details to help navigate the next steps effectively and explain key data elements and what to think about when beginning the journey.  

Microsoft Teams 2.1 Requirements

For new Teams to be successfully installed, you need version 23306.3314.2555.9628 or higher. In addition, virtual machines must meet the minimum requirements listed here. Please note that Server 2016 for Multi-Session VDAs is not supported, and with this in mind, we encourage you to start thinking about your next operating system upgrade to incorporate Teams 2.1 as you prepare for this transition. 

Teams 2.1 Install

Teams 2.1 is now considered an MSIX application, and the installation process has changed. Many organizations will need to understand how this change affects their current image and processes. Depending on your operating system, there are 3 installer types. The recommended way is to install Teams 2.1 without Classic Teams. 

• Installing the bootstrapper with a MSIX 
  • .\teamsbootstrapper.exe -p -o “C:\Installs\newTeams\MSTeams-x64.msix”
• Installing the bootstrapper without a MISX location 
  • .\teamsbootstrapper.exe -p
• Server 2019 Dism Side loader 
  • Dism /Online /Add-ProvisionedAppxPackage /PackagePath:<MSIX package path> /SkipLicense 

Classic Teams vs New Teams 2.1

Many organization’s EUC teams are familiar with the classic Teams and profile locations. Teams 2.1 changes everything from how it was installed to the package requirements. This is a quick comparison from Microsoft outlining the key differences.

HDX Optimization

To achieve HDX Optimization with Teams 2.1, you need to enable the requirements for Team 2.1 and Citrix to utilize WebRTC (VDI 1.0); you can accomplish this by updating your golden image or defining it with GPO. It’s also worth mentioning you will need to review your M365 updates and deployments. There are specific use cases where you want the Teams 2.1 VDI optimized accordingly, and using M365 as a package to allow Teams 2.1 from the source installer will need to be reviewed and understood. You will want to optimize certain aspects to prevent the disabled Teams 2.1 options from an M365 packaged installer. Citrix and Microsoft are working on a new 2.0 channel, and if you look closely at the docs, you will discover some elements here.

• Base Citrix HDX: You can define this in the golden image or apply it via GPO.
  • Add WebSocketService for Teams 2.1

Outlook Plugins (TMA)

Just as before, Microsoft Teams 2.1 integrates with Outlook.  Due to the underlying application platform change, there are some considerations you need to be mindful of. When you install Teams 2.1, the Teams Meeting add-in (or TMA) will try to run as the user context. Depending on how you define security, this can lead to the Teams Meeting add-in being blocked. This doesn’t always occur, but there are tactics to ensure the Outlook plugin is operational, and there is a need to change how this is handled to ensure the users can successfully have the Outlook integrations they are accustomed to.  It’s important to know that other actions need to be taken to ensure that the IM providers are successfully loaded for the users. 

JSON Files

In Classic Teams, modifying JSON files controlled many settings for the user experience. Teams 2.1 has some settings in this JSON file in each user’s profile.  The JSON file is only created after Teams 2.1 is launched for the first time. After it’s created, I found that you can update settings within “app_settings.json”  for specific things only at this time.  You can also change the Teams 2.1 user settings in app_settings.json with WEM and JSON actions, but there are only certain things you can do, and there are timing aspects you need to consider, which will define how you roll Teams 2.1 out to your organization. Ideally, as of now, it’s best to fully understand that the classic Team’s settings aren’t like the new Teams in these aspects. It’s best to get Teams 2.1 working as a whole before modifying JSON configurations to avoid uncertainty.

Desktop Shortcuts

When you install Teams 2.1, it will not create a Desktop Shortcut for the user. Instead, you will need to define this for your users if they are accustomed to it. There are many ways to achieve this, but we typically use Citrix Workspace Environment Manager to help define this. Teams 2.1 is installed and registered in the Windows App folder. The Windows Apps folder is a hidden folder on Windows containing the files that make up all the default applications. It stores every application you download from the Microsoft Store or any UWP-related application. Defining shortcuts to this location for users will only cause you more work down the road, and you will need to understand the operations of these applications and how they store the data for the users.

• Define a WEM Application pointing to the user data for the ms-teams.exe shortcut as an example

Disable or Enable AutoStart

Teams 2.1 will be enabled at startup, just like the classic Teams. You can enable or disable this for your users depending on your environmental needs. But there is some information you will need to understand by defining this. Configurations for Teams 2.1 are possible, but you will need to understand the functions of Teams 2.1 to help you determine whether you like Teams 2.1 to start up. By understanding this, you will also understand the need to know the difference between resource consumption and classic teams. Your outcome may change based on resource consumption.

• Teams 2.1, like Classic Teams, does run at startup. To stop that, implement this registry key in the user hive for the location of Teams 2.1
• This changed dramatically with Teams 2.1 compared to the location of classic teams.
• You can achieve this with Citrix Workspace Environment Management, GPP, or custom scripts that fit your needs.

Profiles

Providing users with any virtual desktop, you always need a solid profile solution with the change in how Teams 2.1 interacts with the user profile and the MSIX foundation. It’s essential you know how to successfully determine your profile needs to fully support Teams 2.1. The outline here is to help you understand the different aspects of what is necessary for Teams 2.1.

FSLogix Profile containers or Office Data File containers

• FSLogix 2210 hotfix 3 (2.9.8784.63912) – FSLogix Release Notes – FSLogix | Microsoft Learn
  • Customers who are deploying or using new Teams, this version is the minimum version needed on the following operating systems:
  • Windows 10 enterprise and professional (multi-session or single session)
  • Windows 11 enterprise and professional (multi-session or single session)
  • Windows Server 2022
  • Sever 2016 is NOT supported
• Server 2019 is still under development, and FSLogix 2210 hotfix 3 (2.9.8784.63912 will NOT work 
  • For organizations running Server 2019, challenges will arise with this operating system. Microsoft is working hard to address these limitations with FSLogix.
• FSLogix offers a feature set called “enable the installation of Appx Packages”
  • It’s vital to understand if you need this feature or not. When enabled (1), this setting reads the AppxPackages.xml manifest file from the user’s profile and installs / re-registers the list of applications. The AppxPackages.xml file can be found at %LocalAppData%\FSLogix\AppxPackages.xml. This setting does control the global behavior in Windows for all AppX applications. This only improves functionality when used with FSLogix.
• Recommendation is to review and understand AppX, MSIX
  • Issues with AppX, MSIX or Microsoft store applications – FSLogix | Microsoft Learn

Citrix Profile Management

• Just like FSLogix, Citrix has adopted Teams 2.1 into the current CPM stack. We have been working closely with the Citrix development team to ensure that CPM profile solutions are ready for Teams 2.1. 
• If you are using OFDC with FSLogix and CPM files as profiles, it’s recommended that you store Teams 2.1 in OFDC. 
• Citrix offers Roam UWP apps availability now. Still, it’s vital to understand if you need this before enabling it within your environment, as there are some changes and elements you will need to understand that could impact you if the elements are not discussed here.
• Recommendation is to review and understand AppX, MSIX 
  • Microsoft Teams 2.1 supported for VDI/DaaS (citrix.com)

Profile Data

As always, Teams can take up space. I highly recommend you take the time and read this (New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) – Microsoft Teams | Microsoft Learn).  Implementing correct profile management will ensure that the user experience is positive.  Teams 2.1 requires slightly different configuration of profile management solutions to maintain that positive experience.

Anti-Virus Exclusions

One of the most common issues affecting software is not having proper anti-virus exclusion before rolling out systems. As we all know, Team’s 2.1 is no different, and Microsoft even describes this in the new Teams VDI documentation.  Ensure you put in the proper AV exclusions for Teams 2.1, significantly reducing Teams 2.1 from starting up or even delaying starting for the user. The name of the folder where the new Teams app is installed is dynamic, and it changes when the app’s version is updated. The folder name begins with MSTeams_, ends with _8wekyb3d8bbwe

Feature parity and VDI

Teams in a VDI scenario inevitably has growing pains.  Initially not all native Teams features are supported in VDI.  As Microsoft works with VDI vendors, this list will be updated, but please refer to Microsoft documentation on a particular feature if it is not working to ensure it is supported.  You can find that list here https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy at the bottom of the page.

Summary

Migrating to Teams 2.1 from Classic Teams can be daunting, especially navigating all the changes introduced with the updated platform. This includes checking compatibility, user experience, and profile management, optimizing integration with HDX Optimization and Outlook Plugins, and, most importantly, ensuring that end users are satisfied compared to Classic Teams. With everything that goes into the deployment of Teams 2.1, we understand the complexity that Team 2.1 may bring to our customers. Choice Solutions team is now offering a New Teams JumpStart program. The Teams 2.1 JumpStart program will do a planning and environment check around your use case for Classic teams. JumpStart includes items such as build, configure, and functionality testing geared with Teams 2.1. This program will enable you to reduce the daunting next steps ahead and empower you confidently when you transition. The Solutions team has already spent significant hours understanding the changes and is ready to assist your organization.  Please contact us, reach to your sales representative, or email sales@choicesolutions.com so we can begin partnering with your organization to make sure you leverage Microsoft Teams to its fullest extent in your organization.

References

These two links will provide you with some comparison of what we started with for Classic Teams and where we are going with Teams 2.1 in the near future.

• Classic Teams – CVAD Guide to Microsoft Teams – Citrix Community Articles – Citrix Community 
• New Teams – Testing the New Teams in Citrix VDI – Citrix Community Articles – Citrix Community 
• Exclude antivirus and DLP applications from blocking Teams – Microsoft Teams | Microsoft Learn 
• New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) – Microsoft Teams | Microsoft Learn 
• Announcing general availability of FSLogix 2210 hotfix 3! – Microsoft Community Hub