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-7687: How to enable on-premises CPS logging

Privileged Access Service ,  

4 January,17 at 12:42 PM

Applies to:

All version of on-premises Centrify Privilege Service

Question:

How to enable logging for on-premises Centrify Privilege Service and send the necessary log files for Centrify support team to further investigate?


Answer:

Centrify has a built-in Powershell script comes with the package that record the information that needs for troubleshooting. A PowerShell script (capture_diagnostics.ps1) is provided with Centrify Privilege Service to record information about the following areas:

  • The product registry hive from HKLM\Software\Centrify.

  • The cisdb database.

  • Centrify log files for the cloud connector, lrnode, web, and installation log4net.

To save Centrify Privilege Service diagnostic information using the capture_diagnostics.ps1 script, please perform the following:

  1. Open a PowerShell console window as Administrator.

  2. In the PowerShell console, change to the Centrify Privilege Service scripts folder. The Scripts folder is located in the installation folder that was specified during Centrify Privilege Service installation. Or, if the default installation location was selected, the Scripts folder is in:

C:\Program Files\Centrify\Centrify Identity Service\scripts

C:\Program Files\Centrify\Centrify Identity Platform\scripts (For version 16.12 or higher)
  1. Run the capture_diagnostics.ps1 script:

.\capture_diagnostics.ps1

When the script finishes, output is saved in a file named diag-gid-date.zip and send it back to Centrify support to further investigate the issue.
 

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

Related Articles

 article[How To] Setup Centrify PIM for Google Compute Engine Linux VM Instances article[Labs] Securing Windows Servers with Centrify Infrastructure Service - Local Password Management articleKB-7928: How to create an installation log file with CPS on-premise article[Howto] Set up Centrify Identity Service or Privilege Service for MFA using Smart Card articleCentrify 16.11 & 16.11 Hotfix 1 Release Notes articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? article[Labs] Securing Windows Servers with Centrify Infrastructure Service - Enrollment, Settings and Sets article[Labs] Installing Centrify Privilege Service + High-Availability with Windows Failover Clustering article[Labs] Using Identity Platform as a RADIUS Client to support MFA with OTP tokens (e.g. SecurID, etc)