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-9042: Which version of Centrify Audit Analyzer should be used in a mixed environment?

Centrify DirectAudit ,  

11 August,17 at 08:31 AM

Applies to:
All versions of Centrify DirectAudit

Question:

Which version of Centrify Audit Analyzer should be used in a mixed environment?
For example if the administrator would like to review the auditing sessions from 2012 installation as well as 2015 installation on the same Auditor console. 


Answer:

The 2012 console should be used in above case if you want to connect to both 2012 and 2015 installations.

The newer console cannot talk to older installation and it is by design. 

If the newer console is used with old version of database attached to the installation, then following warning message will be prompted. 


User-added image

Why is new database supported by old console?
Centrify almost never remove any columns or tables from the old schema; the changes are always additive in nature. Because of this, the old console almost always finds the schema/SPs (stored procedures) that it can understand (which of course won't be true if console is newer and schema is older). This was designed based on the assumption that after DB upgrade, customer may not always be able to upgrade all the collectors and consoles in one go and hence we'll have to take care of cases wherein some consoles/collectors are on older version compared to the version of the database. It's perfectly fine to use an older console to review sessions from the newer database since session review process has been part of the product since day#1.

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

Related Articles

 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? 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-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-2727: How to migrate SQL databases associated with a Centrify_DirectManage Audit 3.x installation from one database server to another articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6055: Audit trail events and associated eventID information articleKB-5929: Does Centrify provide documentation for Administrators who wants to monitor Centrify Server Suite events?