Automated Application Management for SCCM

Simplify third-party application creation and patching in SCCM

Knowledge Base ArticlesDownload Trial

Collecting Log Files for Patch My PC Support

enable verbose logging for third-party updates in microsoft sccmIn this article, we will review the logs files required to allow our support team to analyze and troubleshoot different scenario’s. Please review the different scenarios below.

When sending the logs files, please attach the logs as a ZIP file using our technical support form.

Logs Files For Troubleshooting Update Publishing (Using Publishing Service)

When using the Patch My PC Publishing Service, we will need the following log files from the SUP/WSUS server where the service is installed.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log
  • %SiteServerLogsFolder%\wsyncmgr*.log
  • %SiteServerLogsFolder%\WCM*.log
Logs Files For Troubleshooting Application Creation (Using Publishing Service)

When using the Patch My PC Publishing Service, we will need the following log files to troubleshoot applications failing to create.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %SCCMInstallFolder%\Logs\SMSProv*.log
Logs Files For Troubleshooting Update Publishing (Using SCCM In-Console)

When using the SCCM in-console publishing, we will need the following log files from the SUP/WSUS server where the service is installed.

  • %SiteSystemLogsFolder%\SMS_ISVUPDATES_SYNCAGENT*.log
  • %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log
  • %SiteServerLogsFolder%\wsyncmgr*.log
  • %SiteServerLogsFolder%\WCM*.log
Log Files for Troubleshooting Update Downloads to Deployment Package

When troubleshooting updates failing to download into a deployment package from the SCCM console, we will need the following log from the machine running the SCCM console:

  • %temp%\PatchDownloader*.log
    • Note: if you are using an RDP session the patchdownloader.log may be in a random folder in your users %temp% folder.
Log Files for Troubleshooting Automatic Deployment Rule Failures

When troubleshooting automatic deployment rules failing for third-party updates, we will need the following server-side logs. In this example, we will assume the main SCCM installation directory is: C:\Program Files\Microsoft Configuration Manager

  • C:\Program Files\Microsoft Configuration Manager\Logs\ruleengine*.log
  • C:\Program Files\Microsoft Configuration Manager\Logs\PatchDownloader*.log (If exist)
  • C:\Program Files\SMS_CCM\Logs\PatchDownloader*.log (If exist)
Log Files for Troubleshooting Application Installation (Client-Side)

When troubleshooting application installation errors on a client, we will need multiple client logs. Please include the following logs:

  • %WinDir%\CCM\Logs\AppDiscovery*.log
  • %WinDir%\CCM\Logs\AppEnforce*.log
  • %WinDir%\CCM\Logs\AppIntentEval*.log
  • %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
  • %WinDir%\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log
Logs Files for Troubleshooting Update Installations (Client-Side)

When troubleshooting update installation errors on a client, we will need the following client logs:

  • %WinDir%\CCM\Logs\ScanAgent*.log
  • %WinDir%\CCM\Logs\UpdatesDeployment*.log
  • %WinDir%\CCM\Logs\WUAHandler*.log
  • %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
  • %WinDir%\WindowsUpdate.log