The Director shows the Controller as Offline, where as in Studio it is noticed that the Controller is Active and Virtual Delivery Agents are getting registered with it.

To resolve this issue, complete the following steps:

1. Run the PowerShell command Get- BrokerController to get the following output:

   

   From the preceding screen shot, in the DB see that the name of both the Controllers are correct and nslookup is also displaying the correct IP of the Controller and the wrong name output states Non-existent domain.

   Same issue appears even after uninstalling and re-installing the Director on the Controller.
   
   2. While installing, the Director enquires for the address of the Controllers. Ensure to add the FQDN of both the Controllers and run a test connection.

   After completing the installation, when starting the director for the first time, the same issue appears.

   Note: You can see that the name on the Controller is incorrect.
   
   3. Run the PowerShell commands to set the Config Registered Service Instances pointing to the correct name of the Controller
   
   4. Run Get-ConfigRegisteredServiceInstance in PowerShell to get all the service instances registered to the Controllers.
   Note: The Service instances registered had the name of the Controller as example.net (which is incorrect).
   
   5. Run the following commands to set the correct name:
   
   Set-ConfigRegisteredServiceInstance -Address http://example.net/xxxxx  -ServiceInstanceUid xxxxxxxx
   
   Note the address and the service instance selected from the Get-ConfigRegisteredServiceInstance command.
   
   Setting the parameter correctly resolves the issue.

Problem Cause

The Configuration Services Instances were registered with the wrong name.