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-2283: How to upgrade Centrify DA from version 2.0.x to 3.0

Auditing and Monitoring Service ,  

12 April,16 at 11:08 AM

Applies to: Centrify DirectAudit 2.x/3.x 

Question:
What is the correct sequence in upgrading Centrify DirectAudit 2.0.x to 3.0.x? Can the versions be mixed and matched together?

Answer:
The steps below are provided at a high level. For more details, please check the online documentation.

1) DirectManage Audit Manager/console and the database has to be at the highest version among Audit Manager, collector and DA agent - meaning it should be upgraded to version 3.0 first.

2) Collector can be at version 2.0 and it can be upgraded to 3.0 later.

3) DirectAudit agent can be at version 2.0.x and can be upgraded to version 3.0 later.

Note: DA 3.0 is not a separate download but is part of Centrify Enterprise Suite 2013/5.x. 

The versions can be mixed and matched between Audit Manager/console, collector and agent as long as the DA database itself is at the highest version. 

There is no downtime except that auditors on Direct Audit Analyzer will not be able to view audited sessions until the upgrade is completed. 

 

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

Related Articles

 articleKB-4547: Is it possible to connect from DA 2.0.x console to a DA 3.0.x installation? articleKB-7120: Suite 2016.1 Deployment Manager is reporting unsupported CentOS 6.8 articleKB-2480: lslpp Reports 2 Versions of DirectAudit Co-existing After Upgrade. articleKB-6041: How to show current license type in use by adclient articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-4046: Why /da/cdashmod appears in /etc/shells after upgrading from 3.1.0 to 3.1.1 articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin?