This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 60%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
An USB camera is well redirected to the Windows side (2019 RDSH). But there is an error in de the Device manager “The device could not start. (code 10)”. It works well on Windows 10.
The client is a Dell Wyse thin client . On that client other USB cameras are working well (logitech, MCAD)
Hey @Lolix2
Before we go further, I would like to confirm the following questions:
Best regards
Karlie
Hello @Lolix2
Good day!
I'm just following up to make sure you received my last reply.
You can enable email notifications for a variety of different events in Microsoft Q&A:
https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html
If you have any further questions or suggestions about this case, please let me know.
----------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Best Regards
Karlie
Hello @Lolix2
Have the problem resolved?If any problem, welcome to feedback!
---Please Accept answer if the reply is helpful---
Thanks
Karlie
No it is not. This is probably a problem on the client side (Wyse ThinClient running ThinOS)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 41%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
The problem has not been solved.
I just tried to add the EnableFrameServerMode registry key w/o improvement.
As far as I understand The ThinCLient does a low level RemoteFX redirection. The camera appear as local on the rdsh server side, not as "remote camera".
As I said some other cameras are working well.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 84%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBA%3C/text%3E%3C/svg%3E)
Hello
I have a question; Am i reading that you got logitech webcams to work on Server 2019 RDSH with Wyse ThinOS thin clients? Can every user have his/hers own video conference separately (zoom....etc)?
If so, what Wyse thin clients are you using and a logitech camera that works model you tested?
This will be much appreciated. Sorry to go off topic, but this is intriguing and will be very useful.
Hi;
Yes Zoom is multi-user aware. (I'm installed the msi package for all users).
We're on D101D, and 5070. ThinOS 8, RDP.
Logitech C270 works. Other brands / models "may" work.
I'd prefer camera with lower resolution (1080*720) which are less cpu intensive. Hence this thread...
Yet, I advise my users to use video sparingly for two reasons :
My hosts have a max of 15 users. I never checked how many concurrent Zoom session are occuring, but I's say that 4 to 5 would a maximum before the overall performance would drop. I had to increase the number of vCPUs to cop with that. (14 at the moment)
Also we're using analog headset. (there is a recurrent bug in ThinOS where USB headsets are not set as default or not recognized at all)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Make sure install the latest driver for the device.
In case you have access to a Windows 10 device, open start and search for feedback and open the Feedback Hub app and in the list select Windows Server and report this issue.