Logging Options

Applies to: Patch My PC Publisher

Overview

Logging options control the level of detail written to Publisher log files and provide tools to assist with troubleshooting and support.

Logging Level

The logging level determines how much information is written to the log files.

• Information This is the default setting and is recommended for normal operation. It records high level operational events and status messages.

• Debug This setting records detailed diagnostic information and is intended for troubleshooting. Debug logging can significantly increase log volume and should typically be enabled only when investigating an issue.

When troubleshooting, it is recommended to temporarily enable Debug logging and revert to Information once the issue has been resolved.

Logs to Retain

Specifies the number of log files to keep before older logs are overwritten.

Note

It is recommended to set Logs to Retain to 10. Publisher log files are relatively small, and retaining additional history is extremely valuable when troubleshooting issues or providing support, as it preserves publishing context that may otherwise be lost.

Max Size in MB

Specifies the maximum size of each individual log file before a new log is created.

Note

It is recommended to set Max Size in MB to 10. Publisher log files are relatively small, and retaining additional history is extremely valuable when troubleshooting issues or providing support, as it preserves publishing context that may otherwise be lost.

Open PatchMyPC.log

Opens the primary Publisher log file. This log contains the main operational and publishing activity for the Publisher.

Note

It is recommended to view this log using CMTrace to improve readability and highlight warnings and errors.

Open wsyncmgr.log

Opens the wsynccmgr.log file. This option is applicable when the Publisher is installed on a ConfigMgr site server and is useful for troubleshooting software update synchronization behavior.

Collect Logs

Collects relevant Publisher log files and packages them into a compressed archive.

The generated log bundle is intended for troubleshooting and is particularly useful when working with support, as it includes the files needed to diagnose most Publisher related issues.