New Teams on terminal servers
We have Teams installed on our terminal servers (Windows Server 2022) as well as locally. The video and voice functions aren't usable on the terminal servers, but everything else works (most notably the Outlook addin). I've been letting users decided whether to try the new Teams. I've been using it locally for months and not recently had any issues. It initially seemed OK on the terminal servers too. I decided to set it as the default in the Teams admin centre recently, and in setting up a couple of new user profiles on a terminal server the problems have started to come to light. Specifically: 1) Teams doesn't want to update - it displays a restart and update icon on the menu, but this doesn't actually cause it to update. Even logging in as an admin and using right-click run as administrator doesn't make any difference. The standalone installer uses an msix package, which doesn't work on WIndows Server (I am aware that there are ways to get it to run these packages, but it shouldn't be necessary and I'd rather avoid it for now if I can) 2) The Outlook addin doesn't work (as in doesn't appear in Outlook). I've looked for Microsoft documentation, and all I can find is this: https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy Which doesn't seen to specifically refer to local terminal servers at all! Assuming that much of what applies to AVD will also apply, I've checked the registry settings it lists and they all appear correct. Today I have created a new test VM, Server 2022, terminal server role, and installed Office using the normal XML config file method (using the latest available .exe for this). Office installed, and as expected only included the new Teams, not the old one. Still doesn't work properly - even after a clean install Teams wasn't up to date and the update now button didn't work. Manually closing and opening Teams caused it to update in this case (that doesn't work with the live terminal servers), but it's unclear whether this is going to continue to work reliably, or why it won't update on the live servers. The Oulook addin doesn't appear at all, although the settings and registry entries as listed in the link above all appear correct. Anyone got any ideas? The lack of mention in the documentation suggrsts that - as usual - Microsoft isn't making any effort to accommodate those using on-prem session hosts. Thanks