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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Correct.
ASKER
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?
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.
ASKER
Worked straight away. Thanks for the answer, and the insight.
ASKER