Aug 15 2022 06:38 AM
Aug 15 2022 06:38 AM
We are having a bit of a problem with VDI policy application in Teams.
We are running Server 2016 terminal services (no Citrix) in the full desktop experience and don't currently run Teams in this setup. We run Teams separately on individual local PCs. Teams is an important LoB application for us as we use it as our complete telephone system.
We want to run Teams in our RDS environment as well as on local PCs to get the benefit of integrated chat, Outlook, colloaboration features, etc. Essentially we want the entire Teams experience in RDS, except for audio and video features. This seems entirely possible, but doesn't seem to be working.
We have used the IsWVDEnvironment registry key to allow us to install Teams as a machine-wide per machine instance using the current msi with the ALLUSER=1 switch. Teams installs and runs completely in RDS in this way.
We have also created a Teams VDI policy in powershell and assigned it to our users. The policy disables audio and video in calls and meetings using the CsTeamsVdiPolicy cmdlets. The policy applies to the required users and we can see that when we query the user via powershell. However, the two things do not join up. When a user signs in to the terminal server via RDS Teams loads in the normal experience. Video is disabled because there is no redirected camera, but since audio is redirected through the rds session the calling option is there. It is as if the Teams VDI policy has not applied to this instance of Teams.
Just to confirm, our VDI policy disables all calling features in the non-optimized environment:
Identity : Tag:DisableCallsAndMeetingsTrue
DisableCallsAndMeetings : True
DisableAudioVideoInCallsAndMeetings : True
MS does clearly state that the policy will only apply to non-optimized VDI environments. RDS is barely supported for Teams and we have no optimization features in place for it. I'm not sure how to tell if it is technically a VDI optimized environemnt or how we can specifically set it to be non-optimized so that our policy applies to the Teams instance?
I hope that all makes sense. Does anyone have any experience of the Teams VDI policies and how we can make sure they apply in the right instances?
Aug 20 2022 08:42 AM
Since the community has not yet responded to your post, you might want to seek assistance with other resources that are focused on tech support: