master volume control on VDA has no affect in Microsoft Teams

[Don Joly]

We are having issues since deploying Microsoft Teams where the master volume control doesn't change the volume in Microsoft Teams calls or meetings. The volume seems to be at 100% with no way to change it. The master volume works for everything else. Has anyone seen this issue? We have MCS non-persistent random pool of Win 10 1903 VDA's at version 1912.0.1000 LTSR. When connecting to the VDA using RDP we are able to adjust the volume in Teams no problem.

[Patrick Bader]

Any updates on this issue?
We experience different behaviours. When using HDX Optimized Mode sometimes the VDA/Teams is able to set volume control on the local endpoint to 100%, but in some constellations not.

Since we do not have desktop viewer the user always has to exit Shift+F2 and setting the volume locally when having a teams call. Not practicable at all.

[Fernando Klurfan1709153904]

On 8/27/2020 at 4:27 PM, Don Joly said:

We are having issues since deploying Microsoft Teams where the master volume control doesn't change the volume in Microsoft Teams calls or meetings. The volume seems to be at 100% with no way to change it. The master volume works for everything else. Has anyone seen this issue? We have MCS non-persistent random pool of Win 10 1903 VDA's at version 1912.0.1000 LTSR. When connecting to the VDA using RDP we are able to adjust the volume in Teams no problem.

That is because Teams is redirected. 

In that case, it is HdxTeams.exe on the endpoint who handles the audio processing, hence the volume bar on the endpoint is the only one that can control the sound level.

 

[Don Joly]

Our users don't have access to the local endpoint to adjust the volume because either the Citrix session goes full screen without the viewer toolbar or Citrix Desktop Lock is installed which prevents any kind of local access to the endpoint. How is it that nobody has reported/complained about this yet? I guess our only option is to disable the Teams optimization so that HDXteams.exe is not used? Thank you for your response!

 

Anyone else come up with any other options? I've got a ticket open with support and will post any solutions they may provide.

[Mohammad Chaaban]

we have the same issue in our environment... we are using desktop lock... did u manage to solve the issue?

[Fernando Klurfan1709153904]

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.

[Gerhard Gerstenberger]

Anything new to this issue? We encounter the same problem using desktop lock and MS Teams. 

[Marc Dell]

Having the same issue. We use thin clients and users cannot easily drop down to the desktop. 

[Fernando Klurfan1709153904]

There is no solution at the moment to this problem. 

It is something we want to fix but no ETA.

There are two possible solutions:

1- we make code changes to VDA and CWA, so you would need to upgrade to a Current Release

2-we create a custom virtual channel pack so you can install a VDA-side executable in your golden image and a client-side dll. This would allow you to keep your VDA and CWA at the same versions you have right now

 

Any preferences?

[T.Massop]

On 12/7/2021 at 3:27 PM, Fernando Klurfan1709153904 said:

There is no solution at the moment to this problem. 

It is something we want to fix but no ETA.

There are two possible solutions:

1- we make code changes to VDA and CWA, so you would need to upgrade to a Current Release

2-we create a custom virtual channel pack so you can install a VDA-side executable in your golden image and a client-side dll. This would allow you to keep your VDA and CWA at the same versions you have right now

 

Any preferences?

 

Any news? 

We are experiencing the same issue, thinclient user cannot switch to endpoint to access volumecontrol.

 

Prefered method for solving this: 

 

1- we make code changes to VDA and CWA, so you would need to upgrade to a Current Release

 

Please provide us with an update. 

 

Thanks!

 

[Frederik de Groot]

Is there any news on this topic? 

thanks! 

 

[Fernando Klurfan1709153904]

On 6/2/2022 at 9:52 AM, Frederik de Groot said:

Is there any news on this topic? 

thanks! 

 

It is still on the backlog.

[Colt Boyd]

This is by no means a fix, but more of an acceptable workaround.
 

When using a windows end-point (with or without Desktop Lock), have the user press Ctrl+Alt+Del and from that SAS screen they can use the media keys on the keyboard to control the end-points volume. If you have them do this while someone is talking in teams all the better.

[Jeroen Wijsman]

 

this solution could also be considered 

 

 

with this solution you can adjust your local sound setting working from a Citrix VDI desktop and a Thinclient and HDX.  The computer must be equipped with a keyboard on which you can adjust the sound level. Or your speaker is equipped with a volume switch

 

https://msendpointmgr.com/2019/04/06/building-lock-down-device-part-2-shell-launcher/

 

https://learn.microsoft.com/en-us/windows-hardware/customize/enterprise/shell-launcher

 

 

[Tim Roumlser]

Hi Guys,

 

we managed to build a workaround for our enviroment ( CVAD2203CU3, with Igel Thin Clients & Imprivata for Appliance Mode) we had to build a Igel Profile which allows the Multimedia keys on our keyboard in Appliance Mode this allows us to control the local volume via keyboard while using a desktop session. 

 

With current release the issue seems still listed as  a known limitation.