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-51205: Audit Trail event log shows incorrect installation name after joining system to a new domain

Auditing and Monitoring Service ,  

31 March,21 at 01:51 PM

Problem:
The Audit Trail event log shows incorrect installation name  in the 'DAInst' field after joining a linux system to a new domain.

Resolution:
If the DA installation is setup manually instead of using Group Policy, It will be required to re-run 'dacontrol -i' again to set up the DA installation after the system has been joined to a different domain/forests; otherwise the field 'DAInst' of audit trail events might still show the old DA installation name.

 

Related Articles

 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? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-6056: How to report the group policy settings that are in effect for the local computer? article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-2727: How to migrate SQL databases associated with a Centrify_DirectManage Audit installation from one database server to another