How to enable debug logging in the CMN Directory Connector [version 3.7 onwards] (4343649)

1. On the CMN Directory Connector Server, navigate to the following location:
   C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Directory Connector\Tools
2. Locate the "log42net.config" file.
3. Rename the "log42net.config" file to "log42net.config.NORMAL".
4. Download the attached "log42net.config.DEBUG" file from the bottom of this KB article.
5. Copy the "log42net.config.DEBUG" file to the same location as above on the CMN Directory Connector server.
6. Rename the "log42net.config.DEBUG" file to "log42net.config" file.
7. Run the connector that you are having issues with in order to capture debug log files.

NOTE: Debug logging mode may impact the performance of the CMN Directory Connector. We would recommend returning the CMN Directory Connector to normal logging mode after troubleshooting has concluded or the necessary debug logs have been captured.

The following steps will return the CMN Directory Connector to normal logging:

1. On the CMN Directory Connector Server, navigate to the following location: 
   C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Directory Connector\Tools
2. Locate the "log42net.config" file.
3. Rename the "log42net.config" file to "log42net.config.DEBUG".
4. Locate the "log42net.config.NORMAL" file.
5. Rename the "log42net.config.NORMAL" file to "log42net.config".

If you have a customized PowerShell script in a field value to populate a field that you want to troubleshoot, you can add PowerShell logging to the top of the script to output the log to a directory of your choosing.

for example;

An Enhancement Request, TFS 763193, has been logged to remove the "userCertificate" mapping from the default configuration of new connectors.