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-14675: Sessions generated by a VNC terminal are not being audited

Auditing and Monitoring Service ,  

5 June,19 at 06:08 PM

Problem:
Sessions generated by a VNC terminal are not being audited. 

Solution:
To enable auditing on sessions generated by a VNC terminal, Instead of using "vncserver :<display>" to start the VNC Server, please use "SHELL=/bin/cdax/bash vncserver :<display>".

This will specify the SHELL as the cdash audited shell manually when vncserver is ran thus ensuring the session is included in the auditing process.

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

Related Articles

 articleKB-7441: List of error codes Adclient and DAD daemons generated for Solaris and Linux clients articleKB-6041: How to show current license type in use by adclient articleKB-10141: Fail to run session data integrity check for nix sessions generated before DB rotation articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-4018: DirectAudit Session logging (scp file stream content) can cause excessive DB usage articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleSIEM Integration - Understanding Centrify's Audit Events