The only component that I can get to install successfully I have tried both the "Remote Desktop Services installation" option, and manually (selecting individual RDS roles) through the "Role-based or feature-based installation", as a session based deployment. On a Hyper-V host that is running Windows Server 2008 R2 (which is patched with the semi-recent hotfix that resolves the issue with a Server 2012 guest on a Server 2008 R2 host). Trying to install Remote Desktop Services on a Windows 2012 server that I am running as a virtual machine (which from various accounts that I have read, should be entirely possible) this Server 2012 VM is a guest I would greatly appreciate any help anyone could offer. Is there a powershell command for just installing the Connection Broker that might provide some additional error information, or any Has anyone encountered this before? Any suggestions would be greatly appreciated.
I've also tried applying the one update available in Microsoft Update, and tried it without applying that update (reinstalling between attempts of course). I've run an SFC scan, which found no issues. Get the session host and every other component to install using role-based deployment, except the Connection Broker. That particular item does provide some error messages, but they seem to complain about the Session Host not being able to install due to not being able to find the connection string key in the registry for the Windows Internal Database. I've also tried to deploy this using Powershell using this command: I've tried enabling RDMSUI_TRACING, but didn't get any information at all as to why it's failing. Using the role-based deployment, I can get every 'Remote Desktop Services' component to install except the Remote Desktop Connection Broker. including powershell, Remote Desktop Services Deployment, standard role-based deployment, etc. I've wiped out the OS and reinstalled from scratch at leat 15 times, trying various combinations, fixes, approaches, etc. The installation fails, but I can't find any explanation as to why.
Then I go to add the Remote Desktop Virtualization Services (the VM virtualization role). Installation, I added the AD and DNS roles and promoted the server to the PDC. This is my one and only server (just my personal one for home), so I'm using this single server to run all of the services that I need. I have a brand new installation of the Windows Server 2012 Datacenter 64-Bit RTM from MSDN.
Thanks in advance for trying to help me out. I have been searching for and trying fixes for this for 3 days, and I've gotten no where.