Is there an option to have adnisd update NIS maps after a systems reboot or by extension a daemon restart with no external signal(commands)?
Applies to: All versions of Centrify DirectControl on all platforms
Question: Is there an option to have adnisd update NIS maps after a systems reboot or by extension a daemon restart with no external signal(commands)?
Answer: There is no setting in centrifydc.conf file by which adclient with no external signal can update itself on daemon restart or server reboot .This is because adnisd uses adclient to connect to Active Directory and update the maps, it doesn't connect to AD directly.
Although you cannot force an update immediately after service start you can control the frequency of updates afterwards via the parameter nisd.update.interval which by default is every 30 minutes (1800 seconds), This value is our recommendation for most environments. In environments for example that have a more volatile or stable NIS map environment the time between updates can be changed by modifying the nisd.update.interval parameter in in /etc/centrifydc/centrifydc.conf to specify a different number of seconds between updates,for example: nisd.update.interval: 900.
After the parameter is modified please follow the below steps to take into effect parameter's changed value, Please login into Unix machine Open the terminal Run adreload as root which will force the Centrify agent process (adclient) to reload the configuration properties in the /etc/centrifydc.conf file and in other files in the /etc/centrifydc directory.