Remote Desktop Webcam redirection

%3CLINGO-SUB%20id%3D%22lingo-sub-1277374%22%20slang%3D%22en-US%22%3ERemote%20Desktop%20Webcam%20redirection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1277374%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EIn%20mstsc.exe%2C%20under%26nbsp%3B%3CSTRONG%3ELocal%20Resources%20%26gt%3B%20More..%3C%2FSTRONG%3E%20there%20is%20an%20option%20for%26nbsp%3B%3CSTRONG%3EVideo%20capture%20devices%3C%2FSTRONG%3E.%26nbsp%3B%20Which%20lists%20my%20webcam%20and%20Devices%20that%20I%20plug%20in%20later.%26nbsp%3B%20I%20have%20determined%20that%20this%20option%20the%20an%20RDP%20file%20is%20the%20string%26nbsp%3B%3CSTRONG%3Ecamerastoredirect%3As%3A*%3C%2FSTRONG%3E%26nbsp%3B%20So%20what%20I%20have%20done%20is%20ran%20the%20following%20command%20on%20my%20Connection%20Broker%20so%20that%20this%20line%20will%20be%20added%20to%20rdp%20file%20generated%20by%20the%20feed.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3ESet-RDSessionCollectionConfiguration%20-CollectionName%20%24CollectionName%20-CustomRdpProperty%20%22camerastoredirect%3As%3A*%22%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20run%20Get-RDSessionCollectionConfiguration%20I%20see%20the%20value%20has%20been%20added%20to%20CustomRdpProperty%20along%20with%20%22use%20redirection%20server%20name%3Ai%3A1%22%20which%20seems%20to%20be%20a%20default%20on%20all%20collections.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20strip%20the%20signing%20info%20from%20a%20downloaded%20rdp%20file%20from%20the%20feed%20source%20and%20manually%20add%20camerastoredirect%3As*%20my%20cameras%20are%20redirected.%26nbsp%3B%20Instructing%20my%20users%20to%20do%20this%20in%20order%20to%20use%20their%20cameras%20that%20do%20not%20work%20with%20RemoteFX%20USB%20redirection%20is%20not%20a%20direction%20I%20want%20to%20go.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20am%20trying%20to%20solve%20is%2C%20why%20does%20my%20custom%20RDP%20property%20not%20apply%20to%20the%20RDP%20files%20that%20are%20downloaded.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1277374%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPowerShell%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERemote%20Desktop%20Services%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1345795%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20Webcam%20redirection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1345795%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386796%22%20target%3D%22_blank%22%3E%40Matt_OCC%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20this%20same%20issue.%26nbsp%3B%20Other%20settings%20come%20across%20as%20expected%2C%20but%20not%20the%20camera%20one.%26nbsp%3B%20I%20have%20verified%20on%20two%20farms%20on%20Server%202016.%26nbsp%3B%20They%20show%20up%20in%20the%20registry%20and%20in%20powershell%2C%20but%20don't%20seem%20to%20make%20it%20down%20to%20the%20RDP%20file%20when%20retrieved%20from%20RDWeb.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fremote%2Fremote-desktop-services%2Fclients%2Frdp-files%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fremote%2Fremote-desktop-services%2Fclients%2Frdp-files%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1403739%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20Webcam%20redirection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1403739%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484144%22%20target%3D%22_blank%22%3E%40theguru%3C%2FA%3E%26nbsp%3BI%20accidentally%20made%20a%20double%20post%20on%20this.%20and%20on%20the%20other%20post%20there%20is%20mention%20of%20editing%20the%20registry%20of%20the%20connection%20broker.%26nbsp%3B%20My%20last%20reply%20on%20that%20thread%20has%20a%20powershell%20command%20that%20has%20worked%20for%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eyou%20can%20find%20the%20thread%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-server-for-it-pro%2Fcameras-to-redirect-custom-rdp-property-does-not-work%2Fm-p%2F1361842%22%20target%3D%22_self%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-server-for-it-pro%2Fcameras-to-redirect-custom-rdp-property-does-not-work%2Fm-p%2F1361842%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

In mstsc.exe, under Local Resources > More.. there is an option for Video capture devices.  Which lists my webcam and Devices that I plug in later.  I have determined that this option the an RDP file is the string camerastoredirect:s:*  So what I have done is ran the following command on my Connection Broker so that this line will be added to rdp file generated by the feed.

 

 

 

 

Set-RDSessionCollectionConfiguration -CollectionName $CollectionName -CustomRdpProperty "camerastoredirect:s:*"

 

 

 

 

When I run Get-RDSessionCollectionConfiguration I see the value has been added to CustomRdpProperty along with "use redirection server name:i:1" which seems to be a default on all collections.

 

If I strip the signing info from a downloaded rdp file from the feed source and manually add camerastoredirect:s* my cameras are redirected.  Instructing my users to do this in order to use their cameras that do not work with RemoteFX USB redirection is not a direction I want to go.

 

What I am trying to solve is, why does my custom RDP property not apply to the RDP files that are downloaded.

2 Replies

@Matt_OCC 

 

I have this same issue.  Other settings come across as expected, but not the camera one.  I have verified on two farms on Server 2016.  They show up in the registry and in powershell, but don't seem to make it down to the RDP file when retrieved from RDWeb.

 

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/rdp-files

@theguru I accidentally made a double post on this. and on the other post there is mention of editing the registry of the connection broker.  My last reply on that thread has a powershell command that has worked for me.

 

you can find the thread here https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/cameras-to-redirect-custom-rdp-prop...