Controlling agent operations
The Centrify configuration file for access control and privilege management is /etc/centrifydc/centrifydc.conf. The Centrify configuration file for auditing is /etc/centrifyda/centrifyda.conf. Depending on the deployment options selected when you install the agent, one or both of these files might be available on each Centrify-managed computer. The configuration files contain parameters that specify how Centrify components and subsystems operate on the local computer. They can be used to tune operations to suit your environment, for example to address bandwidth or latency constraints or address specific requirements, for example, to prevent the storage of a password hash. Many of the operations controlled locally by configuration parameters can also be controlled remotely using group policies. For information about customizing operations using group policies, see the Group Policies Guide.
You only have to edit the /etc/centrifydc/centrifydc.conf or /etc/centrifyda/centrifyda.conf file if you want to set custom values for one or more configuration parameters. For most organizations, the default values are appropriate. However, if you decide that you want to use a custom value for any parameter, you can uncomment the parameter name in the appropriate configuration file, then set an appropriate parameter value in place of the default value.
Note: In most cases, you only modify settings in the configuration files if you want to customize specific behavior locally on an individual computer. For most parameters, you can make changes, then run the adreload command to have the changes take effect immediately. Some parameters, however, require you to restart the agent (adclient). Similarly, if you make changes to the configuration parameters used by the Centrify Network Information Service (adnisd), you may need to run the adreload command or restart that service.