AVD with HP ThinPro (linux) no webcam in MS Teams

[tbendernak]

Hello everyone,

we will use our thinclients (HP) with ThinPro(Linux) to connect to Microsoft AVD.

All works fine, but when i try to use a local USB-Webcam for MS Teams, it will not run.

Does anyone have information to make this going?

Many thanks for your help

Best regards,
Thomas

[#2]

@tbendernak 

What is the model?

[#3]

@Kidd_Ip 

Hi, HP t640 with ThinPro 8.1 SP 2.5 and the newes AVD-Client from January

[#4]

Hi

i did this week the same setup 👌, but had to switch to Windows 10 IoT. But our testing didn't show an issue. Is it working when you test it in Edge?

[#5]

Hello,

i found out, that, i need webRTC-Application for old and new! Teams, when i use Microsoft AVD.

Thank you for all.

[#6]

Yes the problem is solved

[#7]

@tbendernak Would be really interested if you could expand on how you got this working.  We have the same problem.

[#8]

@ElmerMax 

Hi,

a important fact was, that i did'nt install "Remotedesktop-WebRTC-Redirectorservice" and all things for this. 

This App has to be installed before the installation of MS Teams (classic or new).

If all things are right, you'll find after opening Teams at the setup-page the point "Information to Teams". After pulling, you'll find lines with teams-version and the phrase "AVD Media optimized".

At my installation then, all runs.

For me this helps: 

Verwenden von Microsoft Teams in Azure Virtual Desktop: Azure | Microsoft Learn

[#9]

Hey guys
we are back on Thinpro 8.1 as well and started to discover issues with camera and audio redirection this week. even with a new win11 multiuser image with just FSLogix and WebRTC we are not able to have the webcam redirected. Neither in Teams nor in the Browser or Camera app.

when i try it with a notebook or a igelos on the same hardware everything is working just fine.

does anybody have a good advise how to troubleshoot?

thnx & best regards
marc

[#10]

probably something changed here?

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/microsoft-teams-in-windows-365-and-azure-...

[#11]

@marc_kuhn We identified an issue with the settings for the connection.  If you disable the bottom option on the settings page which I think is something like 'use hardware acceleration' then this fixes some of the issues.

[#12]

@ElmerMax Thanks for that Hint, i will go and check that tomorrow and let you know if that helps

[#13]

@ElmerMax I tried to disable or enable the last option. The webcam isn't working reliable as well as the whole performance feels laggy compaired to IgelOS on the same hardware. Luckily we have someone from HP who will have a look on it on Monday

[#14]

Hi, last week i had a talk to a microsoft-engineer. He told me, that micrsoft gives the companies which deliver thinclient-software AVD-sdk's with the newest software. Igel and DELL(wise) integrated this in a relative short timeline. For HP-ThinPro, the newest avd-client is from january with an old AVD-sdk. I know this problematic things about teams. If you have meetings with more than one member, you get no stream and other things don't run. It is important, that HP includes the newest SDK 1.2.5454 from Microsoft, that has a lot of problems eliminated.

[#15]

Hey @tbendernak
many thanks for that feedback. That's great inside 👍. Actually, we had an intensive testing yesterday also with HP and currently this isn't performing compared to IgelOS, so we probably switch in the last minute to Igel to avoid big trouble. Thanks a lot!!

[#16]

We received yesterday a new avd app, which isn't published currently. That really fixed a lot of topics, we had to switch off the hardware option as well.

that helps in that case thanks to the HP support

[#17]

@marc_kuhn wow, that's great. You have a better connection to HP-support. Where can i get the AVD app to test? At the HP Update Center there is no new app for AVD.

[#18]

@tbendernak i think it's not really official yet, but give me you e-mail address, i will provide you a linke where you can download it

[#19]

email address removed for privacy reasons

[#20]

--