Non Persistent VDI
Support for Non-Persistent VDI. Currently Teams desktop App installs in the user App folder this means it can't be placed on the base image of non persistent VDI environments.
Are there any plans to provide an alternative install for VDI. Currently we are installing Teams at login for VDI users as a work around.
Good news, this feature has moved into the planning stages. I’ll keep you posted as we continue to move ahead in development.
Warren - any progress with this?
Exactly when i have been looking for
Bruce S commented
The Uninstall steps here don't work! https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi#install-teams-on-vdi
Ramy Harb commented
Hello folks, looking for a recommendation: I am looking for a Teams Meeting add-in for Outlook without installing the teams as it will be part of a VDI and I don't need to keep the teams application running on the VMs. any advise?
I don't see their workaround as a solution. All the install does is put a pointer in so all users install on first run to their profile just like before.
Will Smith commented
It is finally supported on non-persistent VDI! I installed this on one of our Server 2016 images for Citrix and it works great.
Christian LeBourgeois commented
Oh excellent! You started to plan this 1 1/2 years ago. Not even working.
I think Teams would have to be rebuilt to be able to use in RDS
This is so simple Microsoft, do not install to the users appdata!
There is no point putting an installer into prog data for it to just install per user on logon to the same directories.
SRS/AppLocker do not like this either.
Jason Holdenfeild commented
This is ridiculous. The alluser=1 command that allow teams installer fo to program files breaks the Json file. The setup json and the one in Appdara are ignored. You can even save your settings via the GUI. Please fix
Joshua Holcomb commented
So teams worked a bit in Non-Persistent VDI but then it was broke at some later version. It seems to be related to either the SID of the computer or the computer name its self. If these don't match then the encryption on the user's credentials is "invalid". The encryption part may not be as accurate but I'm fairly confident it's related to the fact that it's a "new computer". It seems that roaming profiles were not an idea when adding support for Non-Persistent VDI which roaming prfile support is basically a requirement for non-persistent desktops.
We have a customer that has an Office 365 tenancy – this customer is part of our “Managed Private Cloud” service that provides a virtual desktop and application server environment.
This customers tenancy had a change done by Microsoft that locked it to “Teams Only” which we require to be enabled to allow Skype to operate as Microsoft Teams performs very badly in a Terminal Services environment and bloats the users profiles also making extremely excessive disk consumption across the Terminal server farm.
This particular customer has less than 500 users and Microsoft have indicated customers should be above 500 users to have Skype enabled. Can you please assist with getting this setting enabled in the customer tenant as using Teams is not practically possible in the environment given the technical issue mentioned, and the customer is unable to use the integrated Skype functionality they are paying for.
Taylor M commented
Any update regarding this?
矢崎 達也 commented
Can you give us update for this ?
Any further update on this ? Same boat as everyone else - VDI users are in a ridiculous situation.
Any news here?
We really cant use Teams in a RDSH environment due to this. Now the web option on the RDSH host wants to use Microsoft Edge... which we dont have on Server 2016.
We have this same issue as most of our environment is Non-Persistent and after communicating efforts through an open MS ticket they have acknowledged that this is a known issue and that they are currently working on addressing it before SFB deadline of July 31st 2021.
Any updates on Teams Support for non persistent VDI scenarios
It has been 325 since the last update.
There is a VDI version now which doesn't write the program files into the userprofile.
But still no support for Shared session host type deployments.
The second start of the application if failing on terminalservers (you need to exclude settings.json from the profile to work). It work's but still not supported.