Server 2012 R2 RDS redirection issue
Hi all -
I'm working with a new domain based upon Server 2012 R2 Datacenter Edition. All servers are VMs running on robust Hyper-V hosts. Among my VMs I have two DCs, a file server and 4 other servers that are setup as RDS Session Hosts - I want to use them to host various apps and databases. Users will connect to the various app and database servers from thin-clients via RDP. Each of these servers has a unique purpose - i.e. they are not meant to be a load balancing farm or any such thing. I would like users to be able to login to a particular session host by specifying its hostname or IP in the connection profile at the thin-client.
Unfortunately, it seems like I have inadvertently created a situation where the thin-clients connect randomly to any RDS Session host (rather than to the specific one whose hostname or IP is supplied at connection time). I am not quite sure how to get around this. In order to get the RDS licensing to work properly, I had to setup a server "collection". Could this be the source of the problem? Obviously, I need the Session Hosts to be able to communicate with the license server but I can't have them randomly accepting connections that weren't intended for them.
Can anyone shed some light?
I really appreciate any help you can provide.
Thanks much.
I'm working with a new domain based upon Server 2012 R2 Datacenter Edition. All servers are VMs running on robust Hyper-V hosts. Among my VMs I have two DCs, a file server and 4 other servers that are setup as RDS Session Hosts - I want to use them to host various apps and databases. Users will connect to the various app and database servers from thin-clients via RDP. Each of these servers has a unique purpose - i.e. they are not meant to be a load balancing farm or any such thing. I would like users to be able to login to a particular session host by specifying its hostname or IP in the connection profile at the thin-client.
Unfortunately, it seems like I have inadvertently created a situation where the thin-clients connect randomly to any RDS Session host (rather than to the specific one whose hostname or IP is supplied at connection time). I am not quite sure how to get around this. In order to get the RDS licensing to work properly, I had to setup a server "collection". Could this be the source of the problem? Obviously, I need the Session Hosts to be able to communicate with the license server but I can't have them randomly accepting connections that weren't intended for them.
Can anyone shed some light?
I really appreciate any help you can provide.
Thanks much.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cliff 0 that seems to have done the trick. Thank you!
How are you initiating the RDP connections?
Are you dealing with a Broker and a pool of guest workstations?
Have you setup ADUC > User > Personal Virtual Desktop.
https://technet.microsoft.com/en-us/library/ee216751(v=ws.11).aspx
https://technet.microsoft.com/en-us/library/dd883277(v=ws.10).aspx