Wednesday, February 12, 2014

KB: Cannot remove a RD Session Host from an RDS deployment

Microsoft released a new Kb article related to being unable to remove a RD Session Host or RD Virtualization Host from a RDS 2012 deployment.

“…Assume that you try to remove a Remote Desktop Session Host (RD Session Host) or Remote Desktop Virtualization Host (RD Virtualization Host) server from your Remote Desktop Services (RDS) deployment. If the target server was already deleted from Active Directory, you may receive the following error message:

Could not remove the configuration. Object reference not set to an instance of an object.

This issue occurs because the removal operation tries to contact the server in order to remove the Connection Broker from the RDS Management Servers internal group. The operation fails because the computer object cannot be resolved in Active Directory…”

The advice:

“…To safely remove the server from your RDS deployment, contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:  Contact Us (

Important We do not recommend that you manually edit the database that is used by the RDS deployment…”



  1. Absolutely mind boggling MS wants to charge for this!!! Never having worked with RDS in Server 2012 R2, I deleted a session host (crashed actually) from AD, came back to RDS management to learn I could now not remove it. It crashed with bad HDD and needed to be rebuilt, now with new SID of course so I couldn't have removed it anyway!! UNBELIEVABLE............

    1. You must add the server to the existing collection in which was the server.
      Use the this cmdlet:
      Add-RDSessionHost -SessionHost "Servername" -ConnectionBroker "Servername" -CollectionName "CollectionName" -Verbose

  2. I have reinstalled a server 2012R2 with the same name and IP than the one removed from AD, no role installed. You can now add it in the server manager and then manage the server collection.
    It just give you the ability to manage the collection again
    We are going to add the RD session host role outside of production hours.
    Keep you posted