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.
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.
Mark Gereau commented
Has this work been completed?
VDI install is not in a good enough state. This just adds an installer to Program Files. Application still installs into users local profile. For Non Persistent VDIs it would be better to install the program in a machine context, not profile (Program Files or similar).
Any update @Warren?
VDI install with MSI is out
Kevin Wheeler commented
Any update on this topic? I'm wondering using any of the VHD redirection techs like FSLogics or Ivanti EM will work.
Marcelo Melo commented
Any update about non-persistent VDIs and Microsoft Teams
This is now implemented:
- Download the latest teams msi
- msiexec /i Teams_windows_x64.msi /l*v %temp%\teamsinstall.log ALLUSER=1
- run C:\Program Files (x86)\Microsoft\Teams\current\Teams.exe
This only works on a machine that is evaluated as VDI by the installer, a normal desktop the installer errors notifying you the machine is not a VDI.
We are currently setting up a test track. This is a solution to our issues.
Thanks Warren, can you give us a status update because it's been over a year now and we are still waiting for a solution. Thanks
Fix for this issue is due for release early Q3 2019.
JAL Stap commented
Please implement this feature soon, we need it in our corporate environment.
Definitely hoping to have a solution for Teams in RDS environment. Hope it will be available soon.
It has been 200 days since the last update.
Rob Quickenden commented
Looks like lots of people are after updates to this - any news to share please MSFT
Are we pass planning stage yet?