This tip came to me from a question someone posed internally that we had to find an answer for by hunting someone down.This property isn’t exposed in Server Managers’ UI, so you can set it by calling this powershell command:Set-RDVirtualDesktopCollectionConfiguration –CollectionName –CustomRdpProperty “redirectcomports:i:1”Now the Remote Desktop Client will redirect its COM1 port to the Server. Why is this needed? Think Serially connected devices such as say, Smart Card readers, for instance.Hope this helps!The Dude.
JeffHope you get thisI am having some difficulties getting this to work in my Win Srv 2012 RDS environment.Can you elaborate what input is required here to make it runI get:PS C:Usersasalm Set-RDVirtualDesktopCollectionConfiguration -CollectionName -CustomRdpProperty 'redirectcomports:i:1'At line:1 char:61+ Set-RDVirtualDesktopCollectionConfiguration -CollectionName – + The '.
URL/ protocol redirection from server to client devices. When multiple links are clicked, multiple websites are opened in multiple browsers that use different platforms. When the application contains multiple email links, the user clicks them and opens multiple email clients that run on different platforms.
I want to modify my Virtual Desktop deployment RDP file that is generated via the RDWEB website of my RDS server. I need to add these Custom RDP settings:drivestoredirect:s:DynamicDrives displayconnectionbar:i:0 devicestoredirect:s:.I need the WE8 thin client to redirect any flash drives that are plugged into the unit after initial logon. Also I want to get rid of the connection bar so users cannot accidentally disconnect, but in getting rid of the bar, I need the thin client to automaticallyredirect every USB device that can be to the VDI session like webcams and medical equipment that would normally require using the redirect button in the connection bar. This includes all the items listed under 'Other supported RemoteFX USB devices'.I tried using the following PowerShell command but it throws an error:Set-RDVirtualDesktopCollectionConfiguration -CollectionName GeneralUsers -CustomRdpProperty 'drivestoredirect:s:DynamicDrives `n displayconnectionbar:i:0 `n devicestoredirect:s:.' This creates this error:Set-RDVirtualDesktopCollectionConfiguration: A Remote Desktop Services deployment does not exist on (Server name removed).
This operation can be performed after creating a deployment. For information about creating a deployment, run 'Get-Help New-RDVirtualDesktopDeployment'or 'Get-Help New-RDSessionDeployment'.At line:1 char:1+ Set-RDVirtualDesktopCollectionConfiguration -CollectionName GeneralUserDes -Cu.+ + CategoryInfo: NotSpecified: (:) Write-Error, WriteErrorException+ FullyQualifiedErrorId: Microsoft.PowerShell.Commands.WriteErrorException,Set-RDVirtualDesktopCollectionConfigurationPlease help.-Brian. The easiest solution by far is to just put the switches into the RDP file after the signature. If I tried to put it into the signed portion at the top, it would give me an error that the RDP file was no longer valid. I figured out that the Remote Desktopprogram in Win 8.1 doesn't care if the switches are in the signed or unsigned portions of the file, they all get applied anyway. The solution is to manually edit the RDP file and put the switches that are desired at the very end, after the signature.Thank you to everyone who tried to help with this issue.
Ok, I was able to get the error to go away by updating my SSL certs for the Connection Broker. Apparently something caused them to lose their association.Now when I try to run that command it works; however, only the last item in the chain actually gets implemented. So for instance, if I put ' Set-RDVirtualDesktopCollectionConfiguration-CollectionName GeneralUsers -CustomRdpProperty 'drivestoredirect:s:DynamicDrives `n displayconnectionbar:i:0', (to clarify, both properties are put in the RDP file, but only the last works) the only part that works is the displayconnectionbarproperty. The dynamic drives do not get implemented.
If I remove the displayconnectionbar piece and just leave the drivestoredirect, that property works as it should.Also I cannot figure out what setting in the RDP file will force all USB devices to be passed into theVM, automatically checking the boxes for the devices listed in the 'Other supported RemoteFX USB devices'.Edited for clarification. Hi,Thanks for your comment.Do you have RemoteFX feature is enabled on your server?Sorry to inform but there are some limitation, when we redirect the drives. Hmmm, that is unusual. If both settings are showing up in the RDP file correctly but only the last one of the two is being correctly applied, then my first instinct would be to assume that somehow an unrecognized character is sneaking in there somewhere.If you're copy-pasting the settings into the PowerShell command line, try typing them directly. If that's not the problem, then try removing some of the spaces around the powershell newline character (I don't think they should matter, but it's worth a shot).Hope that helps,Travis Howe RDS Blog: http://blogs.msdn.com/rds/default.aspx. The easiest solution by far is to just put the switches into the RDP file after the signature.
If I tried to put it into the signed portion at the top, it would give me an error that the RDP file was no longer valid. I figured out that the Remote Desktopprogram in Win 8.1 doesn't care if the switches are in the signed or unsigned portions of the file, they all get applied anyway. The solution is to manually edit the RDP file and put the switches that are desired at the very end, after the signature.Thank you to everyone who tried to help with this issue.