How To Unregister An Old or Rogue Controller From PowerShell
book
Article ID: CTX139287
calendar_today
Updated On:
Description
This article demonstrates how to unregister an old or ‘rogue’ XenDesktop delivery controller that has already been taken offline and/or deleted and must be removed from the farm.
Requirements
Administrative access to the PowerShell console (right-click, Run as Admin or start from Citrix Studio, PowerShell tab)
Background
If a controller is deleted outside of Studio, the controller will remain in the farm and must be removed using PowerShell.
Instructions
Complete the following steps to unregister an old or ‘rogue’ XenDesktop delivery controller that has already been taken offline and/or deleted and must be removed from the farm.
-
Back up the database before continuing.
-
Open PowerShell as administrator.
-
Run asnp Citrix* to load the Citrix PowerShell extensions.
-
Run Get-BrokerController to find the rogue controller’s SID, as displayed in the following screen shot:
Note: The SID displayed in your session will vary.

- Highlight and copy the SID (highlight and press Enter).
Tip: Copy the SID to a Notepad window to prevent accidental deletion. -
Run the following two commands to store the SID in a variable and remove the rogue controller from the database:
$brokerSID = "[SID from above]" Get-ConfigRegisteredServiceInstance -ServiceAccountSid $brokerSID | Unregister-ConfigRegisteredServiceInstance

Environment
The above mentioned sample code is provided to you as is with no representations, warranties or conditions of any kind. You may use, modify and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the sample code may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the sample code fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the sample code. In no event should the code be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SAMPLE CODE, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Although the copyright in the code belongs to Citrix, any distribution of the sample code should include only your own standard copyright attribution, and not that of Citrix. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the sample code.
Issue/Introduction
This article demonstrates how to unregister an old or ‘rogue’ XenDesktop delivery controller that has already been taken offline and/or deleted and must be removed from the farm.
Was this article helpful?
thumb_up
Yes
thumb_down
No