Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-4874: DirectAudit ADM templates shipped with Centrify Suite 2013.3 or before is not compatible with agent 5.1.3

Auditing and Monitoring Service ,  

12 April,16 at 11:11 AM

Applies to:  Centrify DirectAudit 3.x release

Problem:

When using Centrify Suite 2013 ADM group policy template to apply DirectAudit Installation GUID group policy setting on all Unix/Linux systems with Centrify DirectAudit 3.2.0 release or above.
The /var/centrifydc/reg/machine/gp.report showed that the group policy has been applied.
However, the DirectAudit agent installation settings remains not configured (verified by dainfo -d):

Dad's current installation: not configured

Cause:

The location of registry policy file for the "Installation Guid" group policy setting has changed since Centrify Suite 2014.
The mismatch of path causes the DirectAudit agent unable to retrieve the group policy settings.

Below screenshots showing the view difference between the 2 versions of ADM files – upper one is shipped with Suite 2013 and lower is shipped with Suite 2014. 

User-added image
 
User-added image

Resolution:

Please re-import the ADM file shipped with Centrify Suite 2014 or later by

1. Right click on Computer Configuration > Policies > Administrative templates

2. Choose Add/ Remove Templates

3. Browse to C:\Program Files\Centrify\DirectManage Audit\AuditManager and import centrifyda_settings.adm

User-added image

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleIntegration of legacy platforms with Centrify Server Suite articleKB-5889:enQuesta application authentication issue after upgrading Centrify agent to 5.2.3 articleKB-4565: Centrify disconnects from AD after a period of time articleKB-5875: How to Disable DA Logging articleIdentity and Access Management for Hortonworks Data Platform articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD?