We recently had a server failure in our AD strcture (not a network issue as we have a distributed AD structure) and this has led to a problem with importing subscribers from Exchange into Unity. When unity was installed it has selected a "default domain controller" and this value is set in the registry. In our case this was the controller that suffered the AD failure and whilst the server is offline there are numerous errors on the Unity box -
Skipping synchronization cycle due to error connecting to domain controller. Ensure that the server is accessible and is configured as a domain controller.
Domain Controller: server.aaa.com
Binding String: LDAP://server.aaa.com:389/ROOTDSE
Error Code: ERROR_DS_SERVER_DOWN
Description: The server is not operational.
Changing the registry value to another AD server fixes the problem.
My question is - can Unity be configured to failover btween multiple AD servers to protect against this situation ?? Granted I can edit the registry in the odd case that an AD failure occurs, but as with any other AD client on the network, why will Unity not look to another AD server dynamically ???
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.