Forum Discussion

KrysieJ's avatar
KrysieJ
Copper Contributor
Oct 05, 2021

AVD and various clients.

I logged into AVD today and found it quite interesting that the clients did not have options for permissions for various redirections. I also was quite disappointed to see the difference in feature parity.

My biggest criticism is MSRDC vs URDC.

Really, these two need to have feature parity. It should be common place for at home users to install from the store. This should be a no brainer. Imagine my surprise when I cant use certain basic features in URDC simply because it is from the store. Specifically: Camera and SmartCard redirection. (Pen would be nice too)
But more concerning to me is that I had to dig all the way to this page to see that: https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-app-compare

I should have had a notice on Microsoft Store telling me that if I need those features to use MSRDC and given me a KB number or something to search to get right to it.

 

My second complaint is that both MSRDC and URDC should have a permissions page in settings or a way to define per workspace permissions. I do not want every connection to forward my mic. The added benefit is that I could potentially use this to diagnose if say SmartCard redirection was not working and be able to tell my Admin that, "no, SC is redirected on my end and the client sees it correctly. Please check the Gateway." or maybe even get a notification from MSRDC/URDC saying "The Gateway for this workspace does not support Redirection of [x]"

No RepliesBe the first to reply

Resources