Today all my Windows 11 22h2 Enterprise imaged desktops had Teams auto install itself.
But the 2 know workarounds are the "change user" commands else use VDI instead of TS (or RDS). Most people just blame on the O365 installation or MS Server 2016/2019 OS etc. You can go do your own research as there are easily 3000 over cases on MS technet or other MS forums that the issues are some random and have no solutions (some worked but issues came back again). Please let me know what are the issues you spoke of that are associated with 365 apps on TS, so i can prepare to avoid them or fix them. I installed 365 apps and they are working for all users.
Thats where you may get weird O365 issues which are not as properly documented as MS Office 2016/2019. MS Office, Gogole Chrome etc are some of the applications that need it as they often create like multiple cheime.exe, excel.exe, outlook.exe etc in the background process.in the past (server 2012, we call them Terminal Server shadow registry settings) and these applications sometimes do not go to the correct "home profiles" as well (modern day "users\appdata"). However, I've never installed O365 on an RDS server, so maybe it's one of the apps that needs it. I have seen a few people post about apps that had issues, but personally I've not done this on Server 2012 and up. While this used to be required it's very rarely needed with modern servers. Did you use the commands "change user /install" and "change user /execute" when installing applications to TS servers ?
0 kommentar(er)
