RDS 2012 Connection Broker Role not supported on DC

Anyone who wishes to deploy RDS on the Domain Controller needs to be aware that the Connection Broker role cannot be installed on the DC.

Microsoft does not recommend installing RDS Roles on the DC and advises to deploy separate VM’s/Servers.

http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/f2d16f40-ae75-426b-ba00-0d05c5d48dd7/

http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/593251c4-c8d3-44a6-b71b-c7ad9f919eea

9 thoughts on “RDS 2012 Connection Broker Role not supported on DC”

Add yours

xuanyinwen says:

April 17, 2013 at 4:09 am

Hi Ryan, could you give me a hand on the Microsoft forum again please:
http://social.technet.microsoft.com/Forums/en-us/winserverTS/thread/7293234f-e1ad-4e57-a52b-b06cc1d94ea3

Reply
1. xuanyinwen says:
  
  April 23, 2013 at 4:49 am
  
  HI Ryan,
  
  I have done most step you show,
  now I still can’t install the RDS, just stuck on this step:
  
  What should I do Please? I don’t know why I can’t reply on my question any more.
  
  cheers
  Wayne
  
  Reply
  1. Ryan.Mangan says:
    
    April 23, 2013 at 8:46 pm
    
    You need to add the server to the server pool.
mojodk says:

May 14, 2014 at 6:39 pm

“RDS 2012 Connection Broker Role not supported on DC” … what about on RDS 2012 R2?

Reply
1. Ryan.Mangan says:
  
  May 14, 2014 at 9:49 pm
  
  It is supported in 2012 after a hotfix release and 2012 R2 supports this.
  
  Reply
  1. Tomaž says:
    
    September 9, 2014 at 10:09 am
    
    Hi,
    
    I was wondering if you could help me out with a an issue I have in deploying RODC – RDCB roles combined on a single server, a fully updated (patched) Win2012R2 machine.
    
    First, I tested the desired set-up in a lab on AWS and get it to work as planned. Now, when I tried to do so on a (intended) production VPS, the Remote Desktop Management service (RDMS) won’t start at all, making the whole session-based RDS role non-functional. Is there something I am missing? I do not know if this is relevant, but also the BalloonService is unable to start …
    
    There were two attempts that resulted in the same issue mentioned above.
    
    1. RODC successfully installed and promoted, adding the Session-based RDS role by a Quick Start:
    a) Remote Desktop role Services role service – SUCCEEDED
    b) Session Collection – FAILED
    c) RemoteApp programs – CANCELLED
    
    2. RODC successfully installed and promoted, adding the Session-based RDS role by Standard Deployment:
    a) Remote Desktop role Services role service – SUCCEEDED
    b) RD Web Access role service – FAILED
    c) RD Session Host role service – CANCELLED
    
    Thank you,
    Tomaz
  2. Michael Corney says:
    
    September 23, 2014 at 10:37 am
    
    Hi Ryan,
    We have gone through a few PoC deployments and we have been unable to install the RDCB role onto a machine that has already been promoted to a DC. Systems all running 2012 R2 so this is supported from all things I’ve read. Are there any caveats or specific steps required to make this work that you are aware of?
  3. Ryan.Mangan says:
    
    September 30, 2014 at 8:19 pm
    
    Its worked for me many times. Let me look into this and I will get back to you.
Tom says:

September 16, 2014 at 4:48 pm

If this is allegedly supported on 2012 R2, why can I still not install it. I am really confused with all of the conflicting info out there. If anyone can help straighten me out, that would be great.
System:
Server 2012 R2
AD
FS
PS

Thanks in advance.

Reply