Which RDP roles should I install on the domain controller vs the actual application server where users will login

rdpremote desktopremote-desktop-serviceswindows-server-2012

We have a Windows 2012 server that will need to allow 10 users to access it via RDP. The server is setup in our domain. When I go to add the server role for RDP, it gives me the option to install several role services:

  • RD Connection broker
  • RD Gateway
  • RD Licensing
  • RD Session host
  • RD Virtualizatino host
  • RD web access

I am wondering if any of these should be installed on the DC instead of the local machine and also which ones I actually need to install to support plain vanilla RDP access?

Best Answer

Well honestly you shouldn't install any of them on a DC. A DC should be a DC and nothing else. But I know, I'm a purist. So if you must install RDS on a DC, then all you need is the RD Session Host, and RD Licensing. You can install them both together. The session host is what you need to allow 10 simultaneous connections. The RD Licensing role service will store your CALs.

Oh no, I think I misread your question at first. No, none of them need to be installed on a DC. If you don't care about redundancy/broker service, etc., just install both RDS role services on the same member server.