Centrify DirectControl Administrator Console versions 3.0.0 and 3.0.1Problem:
(1) After installing the DirectControl Administrator Console, and then running the Setup Wizard to configure DirectControl with the Active Directory forest, “The server is not operational” message appears.
(2) When trying to add users to a Zone, or when clicking on the Centrify Profile tab for an AD user in ADUC, you see the message "Server Not Operational"Cause:
This is a problem in versions 3.0.0 and 3.0.1 of the DirectControl Administrator Console because they expect to see an A record in DNS. If not found, “The server not operational” error message is displayed.Resolution:
This will be fixed in DirectControl 3.0.2.
There are two workarounds that can be employed:
1. Create the A record in the DNS. This will be the DNS that the Windows machine with the Administrator Console installed is pointing to. You can create this manually, in the DNS Management MMC, or run “netdiag /fix” on the machine servicing DNS and the A record will be created. Please first read about netdiag in Windows Help and run “netdiag /?” before running “netdiag /fix”.
2. On the Windows machine that has the Administrator Console installed, edit the hosts file, C:\WINDOWS\system32\drivers\etc\hosts.
Add the line:
Note that it is the <domain_name> and not the <DC_machine_name>
If you have this IP already existing, you can append the domain, as in:
184.108.40.206 dc1.centrify.com centrify.com