Collecting Log Files to Send to Support for SCCM and Intune

enable verbose logging for third-party updates in microsoft sccmTo help us diagnose specific issues, you may need to send us log files from SCCM or Intune.

This article reviews the logs files required to allow our support team to analyze and troubleshoot different scenarios. Please review the different scenarios below.

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

Server-Side Logs

Software Updates - Failing to Publish Updates Using Patch My PC's Publisher

When using the Patch My PC Publisher to published third-party updates to WSUS, we will need the following log files from the SUP/WSUS server where the service is installed.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\PatchMyPC*.lo_
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
  • %PatchMyPCInstallDirectory%\PatchMyPC-PublishingHistory.csv
  • %SiteServerLogsFolder%\wsyncmgr*.log
  • %SiteServerLogsFolder%\WCM*.log

The following log file may be needed upon request only due to large file size

  • %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log
Software Updates - Failing to Publish Updates Using SCCM In-Console Publishing
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
  • %SiteServerLogsFolder%\wsyncmgr*.log
  • %SiteServerLogsFolder%\WCM*.log

The following log file may be needed upon request only due to large file size

  • %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log
SCCM Applications - Failing to Create/Update SCCM Applications Using Patch My PC's Publisher

When using the Patch My PC Publisher for SCCM application creation, we will need the following log files to troubleshoot applications failing to create.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\PatchMyPC*.lo_
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
  • %PatchMyPCInstallDirectory%\PatchMyPC-PublishingHistory.csv
  • %SCCMInstallFolder%\Logs\SMSProv*.log
Intune Applications - Fails to Create/Update Applications Using Patch My PC's Publisher

When using the Patch My PC Publisher for Intune application creation, we will need the following log files to troubleshoot applications failing to create.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\PatchMyPC*.lo_
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
  • %PatchMyPCInstallDirectory%\PatchMyPC-PublishingHistory.csv

Client-Side Logs

Intune Applications/Updates Failing to Install on Client Devices

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

  • %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
  • %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
  • %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
  • %ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
  • %ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
  • %ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log

 

    Note: Some Patch My PC log files listed above may be found in %WinDir%\CCM folder if that folder exists.

    SCCM Applications Failing to Install on Client Devices

    When troubleshooting SCCM 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\CAS*.log
    • %WinDir%\CCM\Logs\CIAgent.*log
    • %WinDir%\CCM\Logs\DataTransferService*.log
    • %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
    • %WinDir%\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log
      • This may be found in the %temp% of the user who clicked ‘Install’ in Software Center if it was an ‘Available’ deployment.
    • %WinDir%\CCM\Logs\StateMessage.log
    • %ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
    Third-Party Software Updates Failing to Install on Client Devices

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

    • %WinDir%\CCM\Logs\CAS*.log
    • %WinDir%\CCM\Logs\DeltaDownload*.log
    • %WinDir%\CCM\Logs\DataTransferService*.log
    • %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
    • %WinDir%\CCM\Logs\ScanAgent*.log
    • %WinDir%\CCM\Logs\StateMessage.log
    • %WinDir%\CCM\Logs\UpdatesDeployment*.log
    • %WinDir%\CCM\Logs\UpdatesHandler*.log
    • %WinDir%\CCM\Logs\UpdatesStore*.log
    • %WinDir%\CCM\Logs\WUAHandler*.log
    • %WinDir%\WindowsUpdate.log
    • %ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
    Download Stuck at 0% / Waiting to install / Preparing to download

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

    • %WinDir%\CCM\Logs\CAS*.log
    • %WinDir%\CCM\Logs\CIAgent.*log
    • %WinDir%\CCM\Logs\ClientLocation*.log
    • %WinDir%\CCM\Logs\CMBITSManager*.log
    • %WinDir%\CCM\Logs\ContentTransferManager*.log
    • %WinDir%\CCM\Logs\DataTransferService*.log
    • %WinDir%\CCM\Logs\StateMessage.log
    • %WinDir%\CCM\Logs\LocationServices.log*.log
    • %WinDir%\CCM\Logs\UpdatesDeployment*.log
    • %WinDir%\CCM\Logs\UpdatesHandler*.log
    • %WinDir%\CCM\Logs\UpdatesStore*.log
    • %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)

    Configuration Manager Specific  Logs

    Automatic Deployment Rule Failing for Third-Party Updates

    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
    • The PatchDownloader.log (Location may vary)
      • C:\Program Files\SMS_CCM\Logs\PatchDownloader*.log (Most common location)
      • C:\Program Files\Microsoft Configuration Manager\Logs\PatchDownloader*.log (Possible location)
      • %WinDir%\CCM\Logs (Possible location)
      • If unable to locate a current PatchDownloader.log, check HKLM\SOFTWARE\Microsoft\CCM\Logging\@Global:LogDirectory on the site server
        • how to locate the patchdownloader.log file
    Updates Failing to Download to Deployment Package using SCCM Console
    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 numbered sub-folder in your users %temp% folder.
    Patch My PC Publisher - How to Enable Debug Logging

    Enabling Debug logging is often helpful for troubleshooting unique issues with publishing. Follow the steps below to enable Debug logging:

    1. Open the Publisher
    2. Click on the General tab
    3. In the dropdown under Logging Options select Debug
      Enable Debug Logging in Publisher
    4. Close the Publisher
    5. Open Services.msc and locate the PatchMyPCService
    6. Right-click and Restart the PatchMyPCService
    7. Debug Logging is now enabled