I am having trouble deploying an RDS environment. My deployment plan was this:
1. Install RD Connection Broker, RD Licensing, RD Web Access and RD Gateway role on my domain controller (dc01)
2. RD Session Host on my other virtual server (rds01 - fresh install, only joined to domain)
Step-by-step of how I installed this:
(on dc01)
1. Manage > Add Roles and Features > Next
2. Select "Remote Desktop Services installation" > Next
3. Select "Standard deployment" > Next
4. Select "Session-based desktop deployment" > Next > Next
5. Add "dc01.corp.contoso.com" as RD Connection Broker server > Next
6. Add "dc01.corp.contoso.com" as RD Web Access server > Next
7. Add "rds01.corp.contoso.com" as RD Session Host server > Next
8. Select "Restart the destination server automatically if required"
9. Confirm rds01 is online and reachable
10. Hit "Deploy"
* at this point it takes about 5 minutes before the first error shows up
RD Connection Broker role service: dc01.corp.contoso.com - Failed
Error message: "Failed: Unable to set the RD Session Host server running in redirection mode because the RD Connection Broker server is unreachable."
Event viewer error: "RD Connection Broker Configuration Failed on DC01.CORP.CONTOSO.COM With Error: Unable to save the RD Session Host server redirection settings."
RD Web Access role service: dc01.corp.contoso.com - Succeeded
RD Session Host role service: rds01.corp.contoso.com - Succeeded
Continuing, I try to install RD Gateway role on dc01:
Step-by-step of how I installed this:
(on dc01)
1. Server Manager > Remote Desktop Services > Overview
2. Click "RD Gateway" (big green plus + sign)
3. Add "dc01.corp.contoso.com" as RD Gateway server > Next
4. Set SSL certificate name to "rdgw.contoso.com" > Next
5. Configm selections > Add
* at this point it takes about 2 minutes before the first error shows up
Remote Desktop Gateway role service: dc01.corp.contoso.com - Failed
Error message: "Failed: Unable to create a Remote Desktop resource authorization policy on dc01.corp.contoso.com. The error is Object reference not set to an instance of an object.. Please check the eventlog on RD Gateway server for more info."
Event viewer errors(e) and information(i) (order old to newest)
Error: RD Gateway Configuration Failed on dc01.corp.contoso.com With Error: Failed to create RAP for Domain Computers group. Error = 0
Information: The resource group "RDG_RDCBComputers" was created.
Error: RD Gateway Configuration Failed on dc01.corp.contoso.com With Error: Failed to create new RD Connection Broker Computers group. Error = 0
Information: The resource authorization policy "RDG_RDConnectionBrokers" was created.
Error: RD Gateway Configuration Failed on dc01.corp.contoso.com With Error: Failed to create RAP for RD Connection Broker Computers group. Error = 0
Error: RD Gateway Configuration Failed on dc01.corp.contoso.com With Error: Unable to create a Remote Desktop resource authorization policy on dc01.corp.contoso.com. The error is Object reference not set to an instance of an object.. Please check the eventlog on RD Gateway server for more info.
Now you see the informations doesn't really add up with the errors. If I go to RD Gateway Manager application all RAP and CAP are created as well. However,
Additional information:
* The environment consists of one domain controller (dc01.corp.contoso.com) and one remote desktop session host (rds01.corp.contoso.com)
* The environment is totally fresh, have only installed AD DS beforehand (was going to use this deployment internally for techs)
* The servers are volume licensed
* Both servers have internet connection
* DNS is working
What I have tried:
* Rebooting
* Re-installing all remote desktop services roles
* Re-installing OS on both servers
* Re-installing domain
* Windows Update
* Disable any GPO that hit the domain controller
* Checked to see if any local group policies exist on the target server
* Installing from PowerShell
* Installing with another domain administrator account
* Installing the role on the rds01 server
* Using DISM to repair from original image
* Quick start deployment
* Standard deployment
* This exact deployment procedure was used at a customer last week, where everything is working just fine.
Does anyone have a clue what is going on? What am I doing wrong...
Thanks in advance.