To gather additional information on various Defender components, you can enable diagnostic logging for each component.
To enable the logging for some Defender components, you need to edit the Registry.
|
Caution: The following sections instruct you to modify the Registry. Note that incorrectly modifying the Registry may severely damage the system. Therefore, you should make the changes carefully. It is highly advisable to create a backup of the Registry before making changes to Registry data. |
To enable diagnostic logging for Administration Console
- On a computer where Administration Console is installed, use Registry Editor to create the following value in the HKLM\SOFTWARE\PassGo Technologies\Defender\Defender AD MMC registry key:
The path to the log file is %ProgramData%\One Identity\Defender\Diagnostics\defender_ade_mmc.txt.
To disable diagnostic logging for Administration Console, delete the Diagnostics value from the Defender AD MMC registry key, or set the value data to 0.
To troubleshoot issues that may occur with token operations, you need to enable diagnostic logging for the DTSDK component which is installed as a part of various Defender components.
To enable diagnostic logging for DTSDK
- On a computer where DTSDK is installed, use Registry Editor to create the following value in the HKLM\SOFTWARE\PassGo Technologies\Defender registry key:
Value name: DTSDK Diagnostics
The path to the log file is %ProgramData%\One Identity\Defender\Diagnostics\dtsdk.txt.
To disable diagnostic logging for DTSDK, delete the DTSDK Diagnostics value from the Defender registry key, or set the value data to 0.