Citrix Studio displays following messages when trying to connect the site.

"The Delivery Controller Address has been changed..."
"Reenter Controller Address or enter a new address"
"Controller has not been configured as a member of a site"

Error Details:


Broker Service logs error events as below


Log Name:   Application
Source:    Citrix Broker Service
Date:     <>
Event ID:   1007
Task Category: None
Level:    Error
Keywords:  
User:     NETWORK SERVICE
Computer:   <>
Description:
The Citrix Broker Service encountered a problem with Active Directory. The site Organizational Unit (OU) identifier might be incorrect or communication with the Active Directory Domain Controller might be experiencing problems.

Please run the Set-ADControllerDiscovery PowerShell script to reconfigure the OU identifier in Active Directory.

Error details:
Exception 'Failed to bind to AD object: <GUID= guid string for OU >' of type 'Citrix.Fma.Sdk.ActiveDirectory.ADBindFailureException'.

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.

The issue can be resolved in two ways.

• Restore the missing OU in AD which is configured as BaseOU for the site, and continue to use the OU based DDC Discovery
• Switch to new mechanism which has no dependency on OU as explained below

1. Powershell command to verify if there is an OU configured for DDC Discovery (old configuration):

• Get-BrokerSite | Select BaseOU
  • For newly deployed sites for new versions, this value is blank (NULL). For old configuration, there must be a GUID string to represent the OU path.
  • Same configuration can be verified from Citrix site database as below:
  • SELECT BaseOU FROM [<enter your site db name>].[chb_Config].[Site]

To change this configuration:

1. On SQL server, you can set the value to NULL as below:

• Update [<enter your site db name>].[chb_Config].[Site] set BaseOU = NULL

OR

2. On Powershell, it can be set to null as below (this will work only if the DDC is already connected to the site. If not, you’ll have to use the SQL option)

• Set-BrokerSite -BaseOU $Null

Note:
Restart the DDC services to ensure the changes are effective.
After this change, AD OU is not required anymore for DDCs, but the VDAs must be configured with ListOfDDCs using a GPO or registry


 

---

Problem Cause

The site was originally deployed with The site Organizational Unit (OU) identifier for DDC discovery. With his configuration, if the configured OU (BaseOU) is deleted, the specified error occurs.