📎 AI Summary:
The thread discusses issues with redirecting the camera for a published app in Windows Server 2019. The original poster experiences success with local RDP connections but cannot enable camera access when using the published app, despite RemoteFX USB device redirection being enabled. Contributors suggest verifying RDS settings and RDP properties, with one sharing a workaround involving configuring custom RDP properties via PowerShell, but the original poster notes difficulties editing these settings in downloaded app links. Overall, the conversation highlights challenges in camera redirection for published applications in Windows Server environments.
The thread discusses issues with redirecting the camera for a published app in Windows Server 2019. The original poster experiences success with local RDP connections but cannot enable camera access when using the published app, despite RemoteFX USB device redirection being enabled. Contributors suggest verifying RDS settings and RDP properties, with one sharing a workaround involving configuring custom RDP properties via PowerShell, but the original poster notes difficulties editing these settings in downloaded app links. Overall, the conversation highlights challenges in camera redirection for published applications in Windows Server environments.
Solution
williamkj
New Member
It works for my friend.
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.
What I am trying to solve is, why does my custom RDP property not apply to the RDP files that are downloaded.
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.
What I am trying to solve is, why does my custom RDP property not apply to the RDP files that are downloaded.
Solution
hey, RemoteFX usb devices is allowed.
when i try to use mstsc.exe with usb + video cupture redirect, it works,
but when i download the link for my published app, i can't really edit the properties...
