Forum Discussion
New Teams on terminal servers
DavidYorkshire - I'm also trying to get New Teams working on RDS environment atleast at the same level as Classic Teams (no video conferencing). As you and others have reported, there often is an "Update" button on the title bar but clicking it does nothing. In my case checking the version of New Teams, it appears that it is actually updated. My New Teams shows the "Update" button but checking its version (Settings -> About Teams), its fully updated. Go here for update history: https://learn.microsoft.com/en-us/officeupdates/teams-app-versioning
Separate of that issue, we're also seeing that New Teams randomly closes, sometimes several times a day. This can be troubling since the Tray icon remains until you mouse over it, then it disappears. Users then need to manually restart Teams.
We are currently having the same issues in our RDS environment.
OS: Windows Server 2022
Issue1: New Teams has the up-to-date version, but the "Update" button still shows up on the title bar. Clicking it will close Teams, and Teams never restarts itself. Manually starting Teams, and the "Update" button will show up again.
Issue2: Occasionally New Teams quits unexpectedly without doing anything.Both issues you note are the same ones we still experience as well in RDS. Its likely a result of how they've re-written Teams into an appX and how those behave (or misbehave) in a multi-user environment of RDS.
I also find that it won't auto-start when a user first logs in even though its fully set to do so. Our users need to manually start after they login each time. At least when running it does seem to work correctly most of the time.
It is sad that MS doesn't seem to provide any new support for RDS session host environment. They want everyone to go the VDI route.
- I suspect it's something to do with Server 2022 not supporting MSIX files fully (hence the need to use the bootstrapper.exe file to install). I have tried Teams on the pre-release of Server 2025 (which does support direct installation of MSIX) and so far as I can tell from initial testing it seems OK. I've also not heard any mention of issues on AVD, which is also multi-user but does of course have the full W10/11 GUI, not the server one, so supports MSIX fully.
Just had a reply this afternoon in the ever-ongoing case with Microsoft. They advise removing and reinstalling it. Well, that'a revolutionary suggestion in a case running since January! It's not like we've done that repeatedly already...
We have both those issues - first one for months (and Teams may or may not actually be up to date), and the second one seems to have appeared more recently. There is also an issue with the Outlook plugin not installing for some users.
Had a case running with Microsoft since January and still got nowhere. procedure seeems to be delay - ask for screenshots / logs - pass to engineering team - try reinstalling it - problem doesn't go away, and back to the beginning to repeat it all again. And again. And again.
I think it's now pretty clear that Microsoft is absolutely not interested in terminal servers and is putting no effort into maintaining software compatibility with them.
DavidYorkshire
The issues stick out a mile. And live for months. Microsoft should really take it seriously.
- While i have stopped Teams constantly closing, further testing shows that all new-Teams users will show the Update button if any one single Teams user with it open doesn't have the latest Outlook plugin installed. In my test profile it says Update but I have confirmed both Teams and the Outlook add-in are up to date. But other users profiles the Outlook plugin has not updated yet so new Teams says Update for everyone. On my test profile I found renaming the outlook plugin folder allowed the latest to install, so i am going to try that on other profiles to confirm. At this point I just need to get every profile up to date and see if the Update button goes away, and then see what happens the next time an update for Teams or the outlook plugin is rolled out.
davidtg I have managed to stop the issue with Teams closing itself multiple times a day on RDS (while it fails to update Teams itself or the Outlook plugin) by adding the earlier suggested GP settings (allow all trusted apps to install, allow deployment operations in special profiles) as well as
Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Installer: Set Enabled and set Disable Windows Installer to never.
Update button is there this morning in Teams and in the next maintenance window i'll manually run that and see what happens, and also probably do the full removal and DISM install method suggested by Jeff.
