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
TSplus as an alternative to RDS without paying RDS license fees to microsoft
Hello, We are evaluating whether to use TSplus (https://www.terminalserviceplus.eu/) as an alternative to Microsoft RDS/Terminal Server. According to TSplus we can not install or uninstall the RDS role, so we do not use RDS CALs and use TSplus CALs. This way it would not be necessary to pay for Windows Remote Desktop licenses. Is this correct? I can't find any information from Microsoft about it reading documentation. As I see it is correct that using TSPlus without installing Microsoft RDS it would not be necessary to pay Remote Desktop licenses. Could someone confirm me that it is so?
RDS 2019 limit resources
hello together I've been looking for a solution for months. How can I limit the resource on a RDS 2019 e.g. CPU and Memory? If a user logs in and runs a stress test, he takes all resources from the server, how can I limit this? Windows Server 2008 R2 had a feature "windows system resources manager" there you could limit it. I don't know why the feature was removed from RDS 2019. Is there an alternative? There must be an alternative... I wonder how the current RDS that are in operation will be managed with the new version. Thanks for your support
