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-2020: Why does session.starttime in DirectAudit database not match with the local system time?

Centrify DirectControl ,  

12 April,16 at 11:11 AM

Apples to:

All version of Centrify DirectAudit.

 
Question:
 
Why does session.starttime in DirectAudit Database not match with the local system time (current_timestamp)?

 
Answer:
 
This is because the date time stored in the Centrify database is in UTC (Universal Time) format. 
It was designed to be time zone invariant so that DirectAudit Console can report properly at different clients' ends.
 
This is one of DirectAudit's design requirements so that it can report the datetime using the local time setting on the machine with the installed console.
 
This feature helps the auditor to figure out when the session actually occurs. 
It is also consistent with all other desktop applications as recommended by Microsoft and should always show the local time.
  
The difference can be shown by the following query:
 
To show the session in Pacific Standard Time in SQL, you can try the following SQL statement:
 
 SELECT 
 zone, 
 machinename, 
 DATEADD(hh, -8, starttime) as pstStartTime 
 
 FROM Session 
 
 WHERE DATEDIFF(hh, CONVERT(DATETIME, '17530101'), starttime) > 0 
 
 ORDER BY pstStartTime

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

Related Articles

 articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-2727: How to migrate SQL databases associated with a Centrify_DirectManage Audit 3.x installation from one database server to another 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-3925: How to add Centrify parameter to a group policy articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-1311: Collector unable to connect to SQL database