[German]Microsoft is working hard to push its new Teams 2.0 client into the user community. Even if the old Teams client is still available for a while, IT decision-makers may sooner or later be faced with the problem of how to operate the new Teams 2.0 application in an environment with Vmware Horizon. One user has addressed the issue and outlined the pitfalls.
Advertising
Old Teams client still available
The end-of-life date of July 1, 2024 for the old Teams client (see New Teams 2.0 client will be mandatory later – but some "chaos") has now been postponed. According to my blog post Teams 2.0: Deadline for switch extended by one year to July 1, 2025, there is still more than a year left to switch to the new Teams 2.0 client.
But administrators may sooner or later be faced with the problem of how to run the new Teams 2.0 application in an environment with Vmware Horizon. I am not a specialist, but I had the impression that the use in this environment is a problem due to the Appx packages for the new Teams and users are looking for a way to use the new Teams client.
Teams in Vmware Horizon
The site vdesktop.ninja already addressed this topic in mid-May 2024 in the article New Teams as an application in Vmware Horizon. I came across the topic some time ago via the following tweet, but only got around to posting the information on the blog today.
The author of the blog post writes that companies that use VMware Horizon to share applications on RDSH servers face the challenge of making the new Teams 2.0 client available via Horizon. The author himself has also tried this and has probably found a solution to this problem. However, the analysis took a lot of time.
Advertising
In his blog post, the author describes the procedure for setting up the new client. The first step was to find the path to start the new version of Teams because Horizon could not find it in the list of installed applications. He was able to access the new Teams client via the relevant path in VMware Horizon, but was unable to log in.
After analysis, it was determined that the root cause of this issue was that the client's application mode in the VMware Horizon environment does not have access to the Microsoft.AAD.BrokerPlugin library. This library is critical as it enables applications to use the AAD service for user authentication and logon. The BrokerPlugin acts as an intermediary that integrates the AAD functions into the applications.
In a series of steps, the author of the article describes the steps he had to take to get the new Teams 2.0 client to work in the VMware Horizon environment. I have no idea whether this is of relevance and interest to anyone in the readership – VMware is probably a red rag for many people anyway. But I thought I'd post the topic on the blog.
Similar articles:
New Microsoft Teams 2.0 Client released for macOS and Windows
Teams 2.0: Deadline for switch extended by one year to July 1, 2025
Microsoft Teams 2.0 issues: Outlook add-in missing during installation; crash after installation and more
Microsoft Teams 2: User status is sporadically displayed incorrectly
Microsoft says, Teams 2.0 migration is to slow; 2/3 still on old client
Microsoft Teams 2.0: Fix for missing Outlook add-in
New Teams 2.0 client doesn't ask for password for re-login
New Teams 2.0 client will be mandatory later – but some "chaos"
Microsoft Teams: Microsoft changes storage location for recordings from May 2024
Advertising
