Applies to:
Centrify Direct Control for Unix/Linux on all platforms

Question:
Is there any record other than addebug logs that shows adclient switching between domain controllers?

Answer:
There is no record other than addebug logs that shows switching between domain controllers. Addebug is the only way which describes switching of domain controllers by adlclient, but they have to be turned on while switching of domain controllers.

Below on the Centrify Unix server, as root or sudo, please run the following commands:

a) /usr/share/centrifydc/bin/addebug on (will turn debug ON).

b) /usr/share/centrifydc/bin/addebug clear.

c) Run the following command as "root" or "sudo"
adinfo –t “Your_AD_domain_name”

d) /usr/share/centrifydc/bin/addebug off (turn OFF debug log)

This file adinfo_support.txt file will be generated under /tmp/adinfo_support.tar.tgz (or) /var/centrify/tmp/adinfo_support.tar.gz (for 5.1 and above releases)
Look by bg:bindingRefresh(background DC binding Refresh) in the file and it will show information related to switching of domain controllers.

Also if the computer is currently bound to a local domain controller, bindings are refreshed only if adclient.binding.refresh.force is set to true.If the computer is currently bound to a domain controller in another site, bindings are refreshed regardless the adclient.binding.refresh.force setting.

The parameter adclient.binding.refresh.interval value specifies the number of minutes between refresh attempts. It must be an integer greater than zero. The following example sets the interval time to 60 minutes: adclient.binding.refresh.interval: 60