Link to home
Start Free TrialLog in
Avatar of morrisonit

asked on

Adding a Hyper-V RDS 2012 member server to an existing 2012 active directory domain


I have a customer who currently has a Server 2012 Std. active directory domain. They have purchased software that needs to run as a terminal services based application on a server, but they don't want to purchase any more hardware.

Can someone give me an easy step-by-step guide to install a Hyper-V member server on the existing physical machine and then setup RDS. I have tried but I'm having problems with certificates and user access via RDP to the member server.

Thanks in advance.

Avatar of Mohammed Khawaja
Mohammed Khawaja
Flag of Canada image

What you need to do is the following:

1.  Remove RDS role from the server
2.  Join it to the domain
3.  Install RDS role
4.  If you have a certificate server then issue certificates for RDS server (if not then you could use self signed certificates, however, you will be prompted each time that the certificate is from an unreliable CA

If you would like additional help then provide more details.
Avatar of morrisonit


Hi Mohammed

The virtual server was joined to the domain first and then had the RDS components installed. Do I need to install all components on the virtual member server or do I need the Licensing server on the physical AD machine? And there has been talk of having to install SQL Express on the AD server?
I can connect via RDP from users desktops to the virtual RDS server but only administrators are authorized to login. I can't make the RDS server an active directory member server as RDS won't run on a AD server running 2012. So how do I allow the Remote Desktop Users group to access the RDS server?
The term Active Directory Member server is misleading as it would imply that it would be a member server in the domain, however, from you added in your comment, it seems like you want to run RDS on a Domain Controller.  RDS is not recommended, supported or functional if you want Domain Users to logon.

if you have one physical server then my suggestion would be to install Windows Server 2012 with Hyper-V role.  Create two VMs where one would be your DC and one would be your RD server.  If you already have a domain in place, then just add the server to the domain and then  get your users to connect via RDS.
I think we're missing some salient points here.
The active directory domain is in place and live, running on a physical Server 2012 box. This is not going to get touched and will stay as is.
The customer will not spend money on another physical server.
I have installed the Hyper-V role on the physical server and setup a virtual Server 2012 machine and joined it to the domain.
This virtual machine is not a domain controller, it is just a member server, therefore RDS installs OK.
I want domain users, who authenticate on the physical active directory domain controller, to be able to run RDP sessions on the virtual member server.
How do I get them to have the correct permissions on the member server to do this? The domain administrator(s) can login via RDP with no problem, but I don't intend making the RDP users members of the Administrators group!
Avatar of Mohammed Khawaja
Mohammed Khawaja
Flag of Canada image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks, this seems to have worked. AD users can login to the virtual server using RDP. They will be running a desktop app on the server, so all should be fine.