Adding Remote Desktop Services role may fail when Firewall Service is stopped in Windows Server 2012

Article ID: 2802436 - View products that this article applies to.
Expand all | Collapse all


On a computer that is running Windows Server 2012, when you try to install the Remote Desktop Services Role, using the "Add Roles and Features" Wizard, the installation may fail. Additionally, during the installation process you may receive one of the following error messages:

Unable to open remote connections on the RD Connection Broker server

The post installation configuration did not complete.

Note: After a reboot the RDS Server may work. If it does not, the following powershell commands will complete the failed action:

    $tss = Get-WmiObject -namespace root\cimv2\terminalservices -class Win32_TerminalServiceSetting


During the post installation configuration, the wizard attempts to enable necessary firewall exceptions for the RDS Role. When the firewall service is stopped, this operation fails and is reported with the above error.


It is not recommended to run without a Firewall. If you have certain requirements to do so, enable the Firewall Service at least during installation of this Role.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.


Article ID: 2802436 - Last Review: July 8, 2013 - Revision: 2.0
Applies to
  • Windows Server 2012 Foundation
  • Windows Server 2012 Standard
  • Windows Server 2012 Datacenter

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from