• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2066
  • Last Modified:

Can't install RDS on Server 2012 R2

I'm trying to setup a proof of concept RDS deployment in Server 2012 R2. For this purpose, I'm trying to create a personal virtual desktop pool with RDS on a single server, which means AD/DC, remote desktop broker, remote desktop virtualization host, and remoted desktop gateway all on one physical box. I'm aware of the potential reasons for not doing this, but like I said, this is a proof of concept. In server 2012, this was not possible on a DC, but now with R2, it is supported. At the end of the day, I'm running into issues with the virtualization host. I've finally gotten the role to install, which in my case had to be done before promoting to a DC, but now I get error 4119 "could not add to RDS management servers group". I can setup a template in hyperV, but server manager shows no virtualizations hosts, even though the role reports as installed. I have no available templates when I go to deploy because of this. Anyone have any ideas? I've been through the guides and I feel like I've reached the end of the internet. I've started from scratch multiple times. I've done it with all updates completed, and with none. I've changed the order of installation, I've installed via powershell, I've done everything I can think of, and I end up back in the same spot, without a recognized virtualization host.
0
sdholden28
Asked:
sdholden28
  • 3
  • 3
1 Solution
 
Cliff GaliherCommented:
The reason an RDS deployment couldn't happen on a single box in 2012 is because the RDCB and ADDS roles could not coexist. This impacted RDSH as well as RDVH.

So while you are indeed correct that the RDCB block was removed in 2012 R2 and that role is now supported on a DC, this was done primarily for RDSH. RDVH still relies on Hyper-V and that'll never play well with a DC.

What you *can* do, and did work the last time I test labbed (which was admittedly pre-RC) is fresh install. Add Hyper-V. Create two VMs. One as a DC and one for the other RDS roles. Once you have a DC, join the management to the domain. Then deploy RDS.,RDVH on your management OS and the other RDS roles in the other VM (or the DC if you are a masochist.) That should keep the odd hyper-v/ADDS interaction that occurs from mangling the RDS environment.
0
 
sdholden28Author Commented:
Ahh. Thanks for the info, so the key is having hyper-v and the DC separated, via physical means, virtually, whatever. Correct?
0
 
Cliff GaliherCommented:
Correct.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
sdholden28Author Commented:
Is it acceptable to run the DC in a VM, and then HyperV plus all the other roles on the physical machine or would this be ill-advised? Recommendation?
0
 
Cliff GaliherCommented:
I am a *firm* believer that the only role on a hyper-v server is Hyper-v. Further, with 2012's licensing, there is no reason to colocate other roles on the host. There is zero licensing cost savings in doing so, and the hardware costs difference is pennies.
0
 
sdholden28Author Commented:
Worked straight away. Thanks for the answer, and the insight.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now