"The paramter is incorrent" error in new Teams client (VDI)
Hello We have a serious issue with the new Teams client in our VDI (Horizon) environment. After running fine for a while (can be multiple hours up to days) Teams crashes / vanishes with the following error. We suspect it might happen during an automatic update. The same error is displayed when trying to launch ms-teams.exe from that path manually. This never happened with classic Teams. We have no idea what causes this and how to fix it, any help is appreciated.New Teams Desktop Not Consistently Opening for Meeting Links (VDI)
I have a user where clicking to join scheduled meetings in Outlook doesn't consistently open Teams desktop. The times that it fails to open (basically nothing happens), they have to click "Continue in Browser", which is a worse experience. We can't seem to find a pattern, other than if they click to join from the little pop-up window after a meeting as started, Teams desktop opens every time. I understand that Teams for VDI is its own animal and maybe we just need to wait to see if whatever is going on is fixed in a newer version, but I thought I'd check to see if this is a common issue.
VM optimized version doesn't display Analytics across Teams
Multiple users reporting (and validated) that when using VM Optimized New Teams, they're unable to see Analytics when clicking the "..." in the center-column. These features all appear to work fine in the desktop versions and on the web-app. Analytics ARE available by clicking "... > Manage Channel > Analytics", and even the "Across channels"-button. But clicking the "Analytics across teams" also results in a blank page. Currently running:MS Teams does not retain device settings in VDI
Hi All, We implemented MS Teams a while ago to be available in our VDI environment. Several users noticed that their device settings are not retained. We have implemented MS Teams by Microsoft best practice; Teams for Virtualized Desktop Infrastructure - Microsoft Teams | Microsoft Docs Anyone else also faced this issue?New Teams and AVD
Hi all we have deploy new teams on our VDI test infrastructure. Yes its working great but how the hell we publish it as app without desktop? It not show in start menu add application, and path can't be used cause after update it change. like: C:\Program Files\WindowsApps\MSTeams_23306.3306.2510.9721_x64__8wekyb3d8bbwe C:\Program Files\WindowsApps\MSTeams_23285.3604.2469.4152_x86__8wekyb3d8bbwe thnx
MS Teams blocking screen lock / idle timeout occurring
Currently running Teams version 1.5.00.31168 on Citrix VDI , Citrix VDA 19.12 LTSR CU5 In the past few weeks a few users have reported that the VDI screen saver / lock is not occurring as expected. It normally occurs after 15 minutes of idle time. The BYOD is locked, but un-unlocking the BYOD session still has the VDI desktop unlocked Why do i think its teams ? Well, I exited teams and the problem seems to have gone away. Large environment and need an explanation what might have caused this. I know media player has a setting "Allow Screen saver during playback" Is there an equivalent setting in teams ? ( i can see anything obvious in the teams interface ) Is there a setting that the organizer can put on a meeting that may hang around afterwards (seen posts suggesting people are complaining the opposite, the meeting continues after a lock is enabled ) Don't have access to the Teams admin center, so can't see if there are any settings there.Non-optimized VDI Policy Teams
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? ThanksTeams Meeting Limitations for VDI Users
We have a large group of Teams users who are using Teams through a VDI session (our frontline workers). It seems like there are a couple things that should be able to be controlled through the Teams admin center or with a setting of some sort but I can't figure it out. Any ideas? When Teams detects that a user is running inside a VDI, they are not able to give control of their screen. The screensharing control is turned on inside the Teams admin center in the policy assigned to our frontline workers, but it still doesn't work inside the VDI. Is there a work around for this? When in a Teams meeting, inside "show device settings," there is no option for VDI users to mute the meeting (the speaker icon disappears). Is there a workaround for this? (situation: they could be in a meeting but able to mute it in order to take other calls, etc - all while inside the VDI). A screenshot is attached of where the referenced speaker icon is typically present inside a meeting. Sincerely appreciative of any help anyone can provide!
