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  >

KB-4665: How to Collect Debug Logs for a Centrify PowerShell Cmdlet

Centrify DirectControl ,  

5 October,16 at 05:55 PM

Applies to:
All versions of the Centrify PowerShell Modules

How does one collect debug for Centrify PowerShell Commandlet issues?

The following steps can be performed as administrator on the machine running Centrify PowerShell Cmdlet to turn on logging:
1) Close any existing PowerShell sessions or consoles.
2) Open the registry (regedit) and navigate to the key HKEY_CURRENT_USER->Software->Centrify->CIMS:
Note: The CIMS key may not exist.  It is required to manually add CIMS key under HKEY_CURRENT_USER->Software->Centrify.
3) Add string value "LogPath" and specify the path to the log file (e.g. C:\Log).
4) Add a DWORD (32-bits) value "TraceLevel", this is the trace level which can be one of several values:

0 - OFF, 1 - ERROR, 2 - WARNING, 3 - INFO, 4 - VERBOSE
Suggested level should be set to 4 (verbose)

Registry Example

5) Reproduce the issue.  

6) After reproducing the issue and the data has been captured send the file(s) specified in the log path (step 3) to support.  If the file is too big (> 18 megs), the same can be sent over FTP or HTTP to to (user: customer0, passwd: custzero).  


Note:  The above registry settings apply to Access Manager as well so if it is installed on the same machine these values may already be populated.

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