Forum Discussion

Matt_OCC's avatar
Matt_OCC
Copper Contributor
Apr 02, 2020

Cameras To Redirect Custom RDP Property Does not Work

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...
Remote Desktop Services
windows server
Matt_OCC's avatar
Matt_OCC
Copper Contributor
May 19, 2020
Like I thought, editing the collection overwrites this value and it has to be updated again. The fact that the property does not get to the file property is a bug I believe. How can we escalate this with Microsoft's rdp team?
RoanPaes's avatar
RoanPaes
Copper Contributor
May 29, 2020

Matt_OCC  I was unable to upload the VB because of clients info within the file.  But I feel your solution works way better. 


The one I used roughly looks like the below (it is missing lots of bits and pieces, but the idea is, once you have your registry exported, you create the VBS file with all you need plus the camera support).

 

 & "promptcredentialonce:i:1" & VbCrLf _
& "videoplaybackmode:i:1" & VbCrLf _
& "audiocapturemode:i:1" & VbCrLf _
& "gatewayusagemethod:i:2" & VbCrLf _
& "gatewayprofileusagemethod:i:1" & VbCrLf _
& "gatewaycredentialssource:i:0" & VbCrLf _
& "full address:s:REMOTE.yourdomain.com" & VbCrLf _
& "gatewayhostname:s:remote.yourdomain.com" & VbCrLf _
& "workspace id:s:REMOTE.yourdomain.com" & VbCrLf _
& "use redirection server name:i:1" & VbCrLf _
& "loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.RDS-Desktop" & VbCrLf _

Dim WSHShell
set WSHShell = CreateObject("WScript.Shell")
WSHShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\BCB-Desktop\RemoteDesktops\BCB-Desktop\RDPFileContent", myval, "REG_SZ"

  • Matt_OCC's avatar
    Matt_OCC
    Copper Contributor
    Jul 13, 2020

    RoanPaes I found editing the registry directly through powershell the easies.  I've run into the issue with a HA collection continually gets written over any time any collection in the deployment changed.  It seems to be part of the sync process between the collection brokers.  I've written a small script to cycle through all of the collections and append the registry to deal with it, just haven't decided on when I should trigger this.