Fernando Klurfan1709153904
-
Posts
218 -
Joined
-
Last visited
-
Days Won
12
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Fernando Klurfan1709153904
-
-
If the Teams session is not optimized, for example the user has a CWA version that does not support Teams optimization (anything prior to CWA 1905 for Windows), then Teams in the VDA behaves 'natively' and all functionalities are supported. BUT .... audio/video/screenshare is rendered by/on the VDA and that will tax the VDA's CPU and network.
The moment the session is optimized (e.g. users with CWA for Windows 1912) then Teams switches to WebRTC and some elements in the UI are not available anymore.
E.g, Live captions.
-
1
-
-
On 7/5/2021 at 10:07 AM, sup kaur said:
So, we are not getting noise suppression feature inside citrix using hdx teams optimization.
This feature is not available for Teams running on browsers - hence it wont work on VDI either (since both rely on WebRTC).
Please raise this request to Microsoft through their Uservoice forums or your Microsoft account manager.
-
1
-
-
On 2/25/2021 at 10:25 AM, Ken Zygmunt said:
Hi Everyone
according to https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html only Client Fetch/Client Render is available in Teams Optimization.
Has anyone heard any news about Citrix extending this to support Server Fetch/Client Render?
Regards
Ken Z
Not planned.
The Branch office should allow breakout to the internet for the 3 well defined IP blocks in Office 365.
-
1
-
-
This is a known issue in Teams when running in VDI.
I added the reference ID in CTX253754 - it is getting fixed in the next few weeks by Microsoft. Updates will be posted there.
"5/23/2021: Hidden chat channels are not visible in Teams when running in a virtual desktop - Microsoft issue (incident reference 241949910) ; currently working on the fix)"
-
2
-
-
11 hours ago, Godwin Odongo said:
Hi,
Most of the users are having issues with Teams in Citrix.
I have attached an image of what comes up on the user's screen.
When this happens users report calls getting dropped and call transfer also fails at this point.Would someone be able to fill me in if they have encountered this before?
Kind regards,
Godwin
We have seen this in the past. I can't think of anything (nor did we find anything) on the Citrix side. Citrix code does not control the UI elements. I would suggest you open a case with Microsoft.
-
On 6/3/2021 at 9:45 AM, Sam Journagan said:
Hello is anyone out there? Its now June, no update...
HI all, we will post updates in CTX253754.
The fix for DTMF is included in a new Teams API version that will auto-update once Microsoft enables it in Ring 4.
This is currently progressing through the Rings. Unfortunately we don't have an exact ETA since it is outside our control.The CWA versions that will support DTMF are:
CWA for Windows 2102 or higher
CWA for Linux 2101 or higher
CWA for MAC 2101 or higher
-
On 5/17/2021 at 9:14 AM, Jesper Lundgren said:
Hi!
We are experiencing the same issue with a Conexant SmartAudio HD sound in Citrix. There is no sound at all.
Will the private build solve that aswell? In that case, can you share it?
The correct drivers are installed but still no sound.
HI Jesper
this was rolled into 2009.6 already and posterior versions - can you try with the latest one 2105 and report back?
-
13 hours ago, Chad Taggart said:
All,
Currently working through a POC of having Teams run within a XENApp shared desktop environment.
Host: Server 2019
VDA: 1912.0.1000.24525
Client Workspace: 21.5.0.48
Headset: YealinkUH36
Handset: Yealink MP50
Teams is installed and is HDX Optimised, the audio devices (mic and headset are all connecting through without issue). I'm using the machine-wide installer and utilising FSLogix to keep profile/cache etc in check (Teams certainly is a bloated bit of kit)
The issue i'm experiencing,
-
The Teams call control buttons on the headset/handset do nothing (eg: answering and hanging up a call). I've found conflicting articles to suggest this is a limitation,
-
Using the USB MP50 handset - If you receive a call, picking up the handset does not answer the call. You hear dial-tone and the call continues to ring. If I answer the call by clicking on the call within teams and then pickup the handset I can hear the person talking but also hear 'dial-tone' for 15s. After 15s the handset then hangs-up and the audio comes out of the speaker on the handset.
- Using the UH36, per above the call answer/hang-up buttons don't work although audio is fine.
From a deployment perspective we were thinking of pairing a HP Thin Client with the USB based Yealink MP50 handset for our general user base.
Appreciate any feedback as to whether what i am experiencing is a true limitation and/or whether i should engage Citrix to troubleshoot the issue.
Known limitations
Citrix limitations
Limitations on Citrix Workspace app:
HID buttons - Answer and end call are not supported. Volume up and down are supported.
-
1
-
The Teams call control buttons on the headset/handset do nothing (eg: answering and hanging up a call). I've found conflicting articles to suggest this is a limitation,
-
There is no workaround AFAIK.
I acknowledge this is a problem - we need to fix it.
I dont have an ETA at the moment. In mid-august 2021 i can give you a better update.
-
On 5/3/2021 at 12:14 PM, Akshay Kotalwar said:
Is this ever going to change?
It's painful for the people from tech support not able to capture screens when troubleshooting. I come across few users already at Citrix complaining about this.
unlikely (although theoretically possible) - this is the nature of optimization / redirection. The window with the video/screenshare is not running on the VDA anymore.
This overlay window is instantiated by the client Workspace app, hence it runs on the endpoint itself.
You can't expect to be able to capture client-side screenshots from the VDA.
-
On 12/1/2020 at 12:50 PM, blue_ken said:
Hi fernando, I have just tested this with CWA 20.10.0.12 with a Teams dial-in number and the conference ID will not be accepted at all. Has this been broken in CWA 20.10.0.12?
unfortunately, yes, its broken but not on CWA side. See ctx253754
-
On 12/1/2020 at 10:54 AM, Michael Burnstead1709159565 said:
I have an issue with Linux-based thin clients, in that when in a Teams meeting and with HDX Optimization in place, the audio quality goes very choppy when sharing the desktop.
It's been happening a while, across all versions of Wyse ThinOS 9.0 (since the version supporting HDX Optimization was released) and also includes the beta release of 9.1 that I have. It's happening with Workspace for Linux 2006 and 2010, and after testing earlier I've found that it's also happening to a different terminal I have from a manufacturer called 10Zig.
If I make a peer-to-peer call, then audio with screensharing is fine. As soon as I join a multi-person meeting, and then share the screen, then a few seconds later everyone else on the call says my audio has gone very chop py and 'robot-voice'.
Anyone else seen anything like this and have any tips to fix? I'm working with Dell engineering now and they are mystified at the moment, but agree that the issue is definitely present as I've demoed it to them.
I've seen some strange scenarios like this - when you join a meeting, we are using a Teams transport relay or conference server. The connection to that server might be using TCP and not UDP (preferred), and even with TCP there are some TLS fragmentation problems that would make your audio robotic.
Can you repro with a Windows machine?
-
7 hours ago, Michael Burnstead1709159565 said:
I have a similar setup, with 5070s running the same software versions. My headset shows up as 'Citrix HDX Audio' in Windows (ie the volume control in the system tray), but in Optimized mode, Teams makes it own connection back to the thin client and should show the proper device names. These terminals run Workspace for Linux 2006 which doesn't provide the option to view multiple audio devices within Windows taskbar, only the default one will work, and will shows up as HDX audio.
Teams now has the ability to make a Test Call, even when running in Optimized mode. Does this work for you?
Dell should have access to CWA linux 2010 - please check with them.
-
On 11/25/2020 at 12:17 PM, Daniel Dunn1709158952 said:
Thats great thank you for that.
Ah I cant wait, we have struggled all year with just the one video!
Thank you
Make sure you monitor CTX253754 - we will post the update there.
-
16 hours ago, Gary Chan1709160142 said:
We started encountering an issue with Teams recently.
We are running Windows 1803 and Teams 1.3.00.30866, the Teams interface will freeze after a user tries to add a speed dial or group with the buttons in the top right corner.
I originally thought it might be a VDA issue so I attempted to upgrade to 1912 LTSR CU2 and 2009t, the issue persists. No change with HDX optimization on or off.
Anyone else encountering this?
If there is no change with HDX opt on or off, I suggest you contact Microsoft - UI freeze requires a level of troubleshooting they are better positioned to execute.
-
On 11/25/2020 at 11:29 AM, Daniel Dunn1709158952 said:
Hi I believe DTMF in Teams was broken with Citrix rolled back the shim recently.
Does anyone know when this will be working again?
Its causing us a big pain!
Thanks
We are targeting this for Q1 - send me a direct message for more details
-
On 11/18/2020 at 10:30 AM, Kris Castelow1709159165 said:
Hi,
Whilst not Linux based Endpoints, I've been seeing some strange behaviour with my Windows devices and HDX. On the contrary, my devices started to work with HDX correctly (they were "HDX not connected" after disconnect / reconnect) around the time period yours stopped, and strangely they've stopped working again in the past week or so.Was your info on versions / shims supplied by Ms / Citrix support or other? I ask as it is my current theory that the backend changes are causing this carnage in my env. It would be most useful to get to the bottom of this.
Thanks,Let me follow up with you on this
-
On 10/30/2020 at 7:47 AM, Mike Broom said:
Anybody else not seeing this after adding the reg keys? Mine doesn't show disabled, it isn't an option in HDX Monitor at all.
Thanks
This is probably related to you using the wrong HDX Monitor version.
You need to get the hdxmonitor.msi that matches the VDA version. This is packaged with the CVAD .iso layout (somewhere in one of those folders)
-
this was fixed in VDA 2009 - for anyone reading this
-
1
-
-
On 10/21/2020 at 9:07 AM, Mark Clayton1709155289 said:
Has anyone noticed when a Citrix users starts video or screen sharing that a hissing type noise is heard on the other end? I use a Laptop with Teams direct but if I phone a citrix users and they start video I can hear a hissing noise through my headset. This only seems to happen from Citrix users.
Running XenApp version 1912 LTSR CU1
Teams Version 1.3.0.21759 (32bit)
Thanks
Mark
what Workspace app version and OS are you using?
Does the hissing go away if the Citrix users mute/unmute their mic?
-
On 10/1/2020 at 12:12 PM, jfarlow669 said:
Any update here? We are needing to get this working asap, and Citrix support keeps telling me its a Microsoft thing, but if its a Citrix thing, please let us know. I am happy to implement a private hotfix if necessary, as we need this working asap.
Thanks!
Please try again today. Sign out/Sign back in required. CWA 2006 for Windows or higher.
-
1
-
-
On 10/2/2020 at 8:33 AM, isaachMF said:
Roughly what date in October might that be Daniel? We've been waiting a while...
Try now, it was enabled today. Sign out / sign back into Teams required.
-
The objective of this post is to allow the community to share powershell scripts for Teams that can benefit other Admins.
Feel free to share yours!
.\Teams_enable_gpu.ps1 -disable
[CmdletBinding()]
Param(
[switch] $disable
)
$DebugPreference = 'SilentlyContinue';
if ($PSCmdlet.MyInvocation.BoundParameters["Debug"].IsPresent) { $DebugPreference = 'Continue' }
$jsonfile = "{0}\Microsoft\Teams\desktop-config.json" -f $env:AppData
Write-Debug ("disable={0}" -f [bool]$disable)
Write-Debug ("jsonfile={0}" -f $jsonfile)
if (Test-Path $jsonfile) {
Write-Debug ("File exists.")
$json = Get-Content $jsonfile | ConvertFrom-Json
Write-Debug ("disableGpu={0}" -f [bool]$json.appPreferenceSettings.disableGpu)
if ([bool]$json.appPreferenceSettings.disableGpu -ne [bool]$disable) {
$json.appPreferenceSettings.disableGpu = [bool]$disable
$json | ConvertTo-Json | Out-File $jsonfile -Encoding ASCII
Write-Debug ("File modified.")
}
}
-
23 hours ago, Daniel Dunn1709158952 said:
We did try it but users were reporting black screens in Teams video calls so rolled back.
The not optimizing after reconnects was fixed by Microsoft a couple of months ago.
There is a new version of 2009.6 though which we havent tested yet.
Disabling GPU in Teams Settings should alleviate the CPU on the VDA , I doubt it makes a dent on RAM.
Otherwise the Teams UI (not video, but the UI itself and all the animations/transitions) are trying to be rendered with GPU emulation and taxing the CPU (because there is no GPU in your host).
As for your RDS Servers - how many concurrent users are logging in to the Windows Server and trying to optimize Teams?
Cutting off non-optimized Microsoft Teams
in HDX Microsoft Teams Optimization Pack
Posted
Although drastic, you could disconnect the session if the CWA does not meet the minimum required version ... you can easily do this by creating a logon script.
CWA version is logged in the VDA, so read that regkey value and take the proper action (you could even display a warning message asking to update)