I've got an odd RDS 2012r2 issue here. All of the RDS roles are installed on one server and the local Server Manager keeps on saying a RDS deployment doesn't exist. All of the services are up and running. I keep on getting these two errors in even log.
Remote Desktop Services has taken too long to load the user configuration from server \\havoc.gridowa.local for user administrator
Microsoft-Windows-TerminalService-RemoteConnectionManger is generating the above error. It generated this error for both of AD controllers. That makes me suspect that some of the configuration is stored in AD. See below...
and
Remote Desktop Connection Broker Client failed to redirect the user GRIDOWA\Administrator.
Error: NULL
I had a 2012r2 server setup with all of the RDS roles. Then I had to promote it to a DC controller for a different project and removed all of the RDS Roles. I'm now trying to setup all of the RDS roles on a new server. The problem is that the new server Broker role keeps on trying to read the configuration from somewhere. Does anybody know were the broker role reads a configuration to figure out what server it should use? I've been scouring DNS and the AD configuration tree and not finding anything.
Server Purpose
HAVOC - 2012r2 DC (Old RDS 2012 Server)
Beta - 2008r2 DC
Gladiator - RDS 2012r2 Server