Navigating Installation Challenges with the New Microsoft Teams Client and New Teams for Web

17 Dec Navigating Installation Challenges with the New Microsoft Teams Client and New Teams for Web

Navigating Installation Challenges with the New Microsoft Teams Client

Introducing New Teams for Web

In the dynamic world of unified communications and collaboration, Microsoft Teams stands as an essential tool. However, users and administrators often encounter hurdles during its installation. This blog post explores common issues and solutions for installing the new Microsoft Teams client, ensuring a smoother experience for all involved.

How do I get New Teams?

In order to get a New Teams desktop client, you can visit: https://www.microsoft.com/en-us/microsoft-teams/download-app?rtc=1. Download the appropriate Teams desktop client as shown in the figure below.

Figure 1, Download Teams desktop client.

Understanding Policy Settings and Their Impact

One of the primary obstacles in installing the new Teams client can be traced back to policy settings that restrict downloading and installing applications. These settings are often governed by Group Policy Objects (GPOs) or third-party tools. Key registry keys that might block the installation of the new Teams MSIX package include BlockNonAdminUserInstall, AllowAllTrustedApps, and AllowDevelopmentWithoutDevLicense.

To verify and adjust these settings, administrators can use the Local Group Policy Editor in Windows. Navigating to Computer Configuration > Administrative Templates > Windows Components > App Package Deployment, they should ensure that the settings for preventing non-admin users from installing packaged apps and allowing all trusted apps to install are set to ‘Not Configured’.

Tackling the App Switcher Toggle Issue

Users might face difficulties in accessing the new Teams client due to the absence of the app switcher toggle. This issue can arise from various factors, including sign-in restrictions set by administrators, usage of VDI computers, or being signed into specific Teams accounts. To diagnose the specific cause, users can check the Teams logs located at %appdata%/Microsoft/Teams. Searching for appswitcher_appstateservice_check in the logs can reveal whether the issue is due to OS version compatibility, sign-in restrictions, or other reasons.

Resolving the ‘Update and Restart’ Error for Windows 10 Users

Windows 10 users might encounter an error message stating, “We’ve run into an issue” during the installation process. This can often be resolved by downloading and installing the WebView2 Runtime. Additionally, if the toggle to opt into the new Teams client is not visible, users can try quitting the Teams app, clearing its cache from the %appdata%/Microsoft/Teams directory, and then relaunching the app.

Overcoming Group Policy Restrictions

Even with group policy settings that disable the installation of trusted apps, it’s possible to download and install the new Teams client under certain conditions. For instance, users running Windows 10 or Windows 11 with specific patch versions may bypass these restrictions. However, certain builds of Windows 11 might still remain blocked.

Introducing New Teams for Web

In addition to the challenges and solutions associated with installing the new Microsoft Teams client, there’s an exciting development in the realm of web-based communication: the rollout of the New Teams for Web. This section of the blog post will explore the rollout schedule, availability, and how to access this new frontier in web-based team collaboration.

Rollout Schedule for New Teams for Web

Microsoft has announced the general availability of New Teams for Web for Chrome and Microsoft Edge users. This rollout, which began in November, follows a specific timeline:

• From Nov 15, 2023, to Jan 15, 2024: Chrome and Microsoft Edge users will access the classic Teams for Web by default. A toggle option allows them to switch to the new Teams for Web, unless the tenant’s upgrade policy is set to ‘Not enabled’. Users can revert to Classic Teams anytime during this period.
• Starting Jan 15, 2024: Teams for Web will begin to honor all Teams upgrade policies, impacting both web and desktop clients. Users will have options based on the set policy – “Classic Teams as default”, “New Teams as default”, or “Microsoft Controlled”. The ability to switch back to classic Teams will be available until March 31, 2024.
• After March 31, 2024: Users still on classic Teams for Web will be automatically updated to the new Teams, aligning with the desktop client updates.

Availability Across Different Browsers and Platforms

• For Firefox and Safari Users: The first quarter of 2024 will see the introduction of New Teams for Web for these browsers. Additionally, Progressive Web App (PWA) support on Linux is also anticipated during this period. More specific dates and details will be announced later.

How to Access New Teams for Web

To experience the new Teams for Web, users can navigate to the Teams web client using Microsoft Edge or Chrome browsers. By selecting the ‘Try the new Teams’ toggle on the upper-left corner of the app, users can switch to the new Teams experience.

Prerequisites for the New Teams Web Client

To ensure a smooth transition to the new Teams for Web, certain prerequisites must be met:

• Minimum Browser Versions: The browser must be one of the three most recent versions of Microsoft Edge or Chrome.
• Browser Configuration: It should be configured to allow third-party cookies.
• Device Requirement: The browser should run on a desktop computer.

The new Teams web client aims to offer near feature parity with the new Desktop client, thanks to a new, cross-client infrastructure. This development marks a significant step in making team collaboration more accessible and efficient, regardless of the platform or device.

Navigating the installation of the new Microsoft Teams client can be a complex process, influenced by various policy settings and system configurations. By understanding and addressing these factors, administrators and users can ensure a seamless transition to the new Teams experience, enhancing their communication and collaboration capabilities.