SCCM Log Files | ConfigMgr Log Files | MEMCM Log Files
This post is really helpful for people who are looking for SCCM log files. The ConfigMgr log files can be viewed with a tool called CMTrace tool located in the path: <ConfigMgr_Install_Media>/SMSSETUP/TOOLS.
To figure out what’s wrong with SCCM, you need to know where the ConfigMgr log files are. On clients, servers, and site servers, the SCCM log files are located in different places.
The SCCM log files are identified by .log or .lo_ file extensions. ConfigMgr writes to the file a .log until it reaches its maximum size. Don’t worry, there is an article published to increase SCCM site server log files.
Sometimes a log file may change locations based on the deployment in SCCM. For example, the smsts.log file changes its location depending on the phase of the operating system installation you are in. Learn about the SMSTS.log file location during SCCM OSD.
The SCCM client logs are located in the following path: C:\Windows\CCM\Logs. The SCCM server log files are located in DRIVE-Letter:\Program Files\Microsoft Configuration Manager\Logs.
Table of Contents – Configuration Manager Log Files
SCCM Log File Viewer Options For Admins
There are many SCCM log file viewer options for admins, and you can pick your tool to read the ConfigMgr log files.
These tools help you read and analyze the ConfigMgr log files to identify the errors and warnings. Not only that, there are tools available that can translate SCCM error codes to messages.
When you want to open any SCCM log file, you need a proper tool to read the log files. Although you can open log files with a built-in application such as Notepad, but other tools provide more advantages.
If you are looking for tools to open and view SCCM log files, you can use one of these tools:
SCCM Client Log Files
- CAS – Content Access Service. Maintains the local package cache.
- Ccmexec.log – Records activities of the client and the SMS Agent Host service.
- CertificateMaintenance.log – Maintains certificates for Active Directory service and management points.
- ClientIDManagerStartup.log – Creates and maintains the client GUID.
- ClientLocation.log – Site assignment tasks.
- ContentTransferManager.log – Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
- DataTransferService.log – Records all BITS communication for policy or package access.
- Execmgr.log – Records advertisements that run.
- FileBITS.log – Records all SMB package access tasks.
- Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) – Windows Management Instrumentation (WMI) provider for software inventory and file collection.
- InventoryAgent.log – Creates discovery data records (DDRs) and hardware and software inventory records.
- LocationServices.log – Finds management points and distribution points.
- Mifprovider.log – The WMI provider for .MIF files.
- Mtrmgr.log – Monitors all software metering processes.
- PolicyAgent.log – Requests policies by using the Data Transfer service.
- PolicyAgentProvider.log – Records policy changes.
- PolicyEvaluator.log – Records new policy settings.
- Remctrl.log – Logs when the remote control component (WUSER32) starts.
- Scheduler.log – Records schedule tasks for all client operations.
- Smscliui.log – Records usage of the Systems Management tool in Control Panel.
- StatusAgent.log – Logs status messages that are created by the client components.
- SWMTRReportGen.log – Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)
SCCM Log Files for Mac Client Computers
The Configuration Manager client for Mac computers records information in the following log files on the Mac computer:
| Log Files for Mac Client Computers | Description | Log File Location |
|---|---|---|
| CCMClient-date_time.log | Records activities that are related to the Mac client operations, including application management, inventory, and error logging. | /Library/Application Support/Microsoft/CCM/Logs |
| CCMAgent-date_time.log | Records information that is related to client operations, including user sign in and sign out operations, and Mac computer activity. | ~/Library/Logs |
| CCMNotifications-date_time.log | Records activities that are related to Configuration Manager notifications displayed on the Mac computer. | ~/Library/Logs |
| CCMPrefPane-date_time.log | Records activities related to the Configuration Manager preferences dialog box on the Mac computer, which includes general status and error logging. | ~/Library/Logs |
SCCM Server Log Files
- Ccm.log – Client Configuration Manager tasks.
- Cidm.log – Records changes to the client settings by the Client Install Data Manager (CIDM).
- Colleval.log – Logs when collections are created, changed, and deleted by the Collection Evaluator.
- Compsumm.log – Records Component Status Summarizer tasks.
- Cscnfsvc.log – Records Courier Sender confirmation service tasks.
- Dataldr.log – Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
- Ddm.log – Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
- Despool.log – Records incoming site-to-site communication transfers.
- Distmgr.log – Records package creation, compression, delta replication, and information updates.
- Hman.log – Records site configuration changes, and publishes site information in Active Directory Domain Services.
- Inboxast.log – Records files that are moved from the management point to the corresponding SMSINBOXES folder.
- Inboxmgr.log – Records file maintenance.
- Invproc.log – Records the processing of delta MIF files for the Dataloader component from client inventory files.
- Mpcontrol.log – Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
- Mpfdm.log – Management point component that moves client files to the corresponding SMSINBOXES folder.
- MPMSI.log – Management point .msi installation log.
- MPSetup.log – Records the management point installation wrapper process.
- Ntsvrdis.log – Configuration Manager 2007 server discovery.
- Offermgr.log – Records advertisement updates.
- Offersum.log – Records summarization of advertisement status messages.
- Policypv.log – Records updates to the client policies to reflect changes to client settings or advertisements.
- Replmgr.log – Records the replication of files between the site server components and the Scheduler component.
- Rsetup.log – Reporting point setup log.
- Sched.log – Records site-to-site job and package replication.
- Sender.log – Records files that are sent to other child and parent sites.
- Sinvproc.log – Records client software inventory data processing to the site database in Microsoft SQL Server.
- Sitecomp.log – Records maintenance of the installed site components.
- Sitectrl.log – Records site setting changes to the Sitectrl.ct0 file.
- Sitestat.log – Records the monitoring process of all site systems.
- Smsdbmon.log – Records database changes.
- Smsexec.log – Records processing of all site server component threads.
- Smsprov.log – Records WMI provider access to the site database.
- SMSReportingInstall.log – Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
- SMSSHVSetup.log – Records the success or failure (with failure reason) of installing the System Health Validator point.
- Srvacct.log – Records the maintenance of accounts when the site uses standard security.
- Statmgr.log – Writes all status messages to the database.
- Swmproc.log – Processes metering files and maintains settings.
Site Server Installation Log Files
The following table lists the ConfigMgr log files that contain information related to SCCM site server installation.
| Site Server Log File Name | Description | Site Server Log File Location |
| ConfigMgrPrereq.log | Records prerequisite component evaluation and installation activities | Site server |
| ConfigMgrSetup.log | Records detailed output from the site server setup. | Site server |
| ConfigMgrSetupWizard.log | Records information related to activity in the Setup Wizard. | Site server |
| SMS_BOOTSTRAP.log | Records information about the progress of launching the secondary site installation process. Details of the actual setup process are contained in ConfigMgrSetup.log. | Site server |
| smstsvc.log | Records information about the installation, use, and removal of a Windows service. Windows uses this service to test network connectivity and permissions between servers. It uses the computer account of the server that creates the connection. | Site server and site system server |
Asset Intelligence Log Files
Use the below log files to troubleshoot the Asset Intelligence related issues.
| Asset Intelligence Log File Name | Description | Asset Intelligence File Location |
| AssetAdvisor.log | Records the activities of Asset Intelligence inventory actions. | Client Computer |
| aikbmgr.log | Records details about the processing of XML files from the inbox for updating the Asset Intelligence catalog. | Site server |
| AIUpdateSvc.log | Records the interaction of the Asset Intelligence sync point with the cloud service. | Site system server |
| AIUSMSI.log | Records details about the installation of the Asset Intelligence sync point site system role. | Site system server |
| AIUSSetup.log | Records details about the installation of the Asset Intelligence sync point site system role. | Site system server |
| ManagedProvider.log | Records details about discovering software with an associated software identification tag. Also records activities related to hardware inventory. | Site system server |
| MVLSImport.log | Records details about the processing of imported licensing files. | Site system server |
Configuration Manager Console Log Files
Use the below log files to troubleshoot issues related to Configuration Manager console.
| SCCM Console Log File Name | Description | Console Log File Location |
| ConfigMgrAdminUISetup.log | Records the installation of the Configuration Manager console. | Computer that runs the Configuration Manager console |
| SmsAdminUI.log | Records information about the operation of the Configuration Manager console. | Computer that runs the Configuration Manager console |
| Smsprov.log | Records activities of the SMS Provider. | Site server or site system server |
SCCM Management Point Log Files
Use the below log files to troubleshoot the issues related to your SCCM Management Point Server. These log files are useful when you are setting up Management Point server in SCCM, uninstalling the MP role, etc.
| SCCM Management Point Log File Name | Description | MP Log File Location |
| CcmIsapi.log | Records client messaging activity on the endpoint. Site system server. | Site system server |
| CCM_STS.log | Records activities for authentication tokens, either from Azure Active Directory or site-issued client tokens. Site system server. | Site system server |
| ClientAuth.log | Records signing and authentication activity. Site system server. | Site system server |
| MP_CliReg.log | Records the client registration activity processed by the management point. | Site system server |
| MP_Ddr.log | Records the conversion of XML.ddr records from clients, and copies them to the site server. | Site system server |
| MP_Framework.log | Records the activities of the core management point and client framework components. | Site system server |
| MP_GetAuth.log | Records the status of the site management points. | Site system server |
| MP_GetPolicy.log | Records policy information. | Site system server |
| MP_Hinv.log | Converts XML hardware inventory records from clients and copies the files to the site server. | Site system server |
| MP_Location.log | Records location manager tasks. | Site system server |
| MP_OOBMgr.log | Records the management point activities related to receiving an OTP from a client. | Site system server |
| MP_Policy.log | Records policy communication. | Site system server |
| MP_RegistrationManager.log | Records activities related to client registration, such as validating certificates, CRL, and tokens. | Site system server |
| MP_Relay.log | Copies files that are collected from the client. | Site system server |
| MP_Retry.log | Records the hardware inventory retry processes. | Site system server |
| MP_Sinv.log | Converts XML hardware inventory records from clients and copies them to the site server. | Site system server |
| MP_SinvCollFile.log | Records details about file collection. | Site system server |
| MP_Status.log | Records details about the conversion of XML.svf status message files from clients and the copy of those files to the site server. | Site system server |
| mpcontrol.log | Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes. | Site server |
| mpfdm.log | Records the actions of the management point component that moves client files to the corresponding INBOXES folder on the site server. | Site system server |
| mpMSI.log | Records details about the management point installation. | Site server |
| MPSetup.log | Records the management point installation wrapper process. | Site server |
| UserService.log | Records user requests from Software Center, retrieving/installing user-available applications from the server. | Site system server |
Data Warehouse Service Point Log Files
The below log files contain information related to the data warehouse service point.
| Data Warehouse Service Point Log File Name | Description | DW Log File Location |
| DWSSMSI.log | Records messages generated by the installation of a data warehouse service point. | Site system server |
| DWSSSetup.log | Records messages generated by the installation of a data warehouse service point. | Site system server |
| Microsoft.ConfigMgrDataWarehouse.log | Records information about data synchronization between the site database and the data warehouse database. | Site system server |
Fallback Status Point Log Files
Fallback status point log files are listed below.
| Fallback Status Point Log File Name | Description | Fallback Status Point Log File Location |
| FspIsapi.log | Records details about communications to the fallback status point from mobile device legacy clients and client computers. | Site system server |
| fspMSI.log | Records messages generated by the installation of a fallback status point. | Site system server |
| fspmgr.log | Records activities of the fallback status point site system role. | Site system server |
Mobile Device Management Log Files
- DmClientHealth.log – Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
- DmClientRegistration.log – Records registration requests from and responses to the mobile device client in Native mode.
- DmpDatastore.log – Records all the site database connections and queries made by the Device Management Point.
- DmpDiscovery.log – Records all the discovery data from the mobile device clients on the Device Management Point.
- DmpFileCollection.log – Records mobile device file collection data from mobile device clients on the Device Management Point.
- DmpHardware.log – Records hardware inventory data from mobile device clients on the Device Management Point.
- DmpIsapi.log – Records mobile device communication data from device clients on the Device Management Point.
- dmpMSI.log – Records the MSI data for Device Management Point setup.
- DMPSetup.log – Records the mobile device management setup process.
- DmpSoftware.log – Records mobile device software distribution data from mobile device clients on the Device Management Point.
- DmpStatus.log – Records mobile device status messages data from mobile device clients on the Device Management Point.
- FspIsapi.log – Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.
Mobile Device Client Log Files
- DmCertEnroll.log – Records certificate enrollment data on mobile device clients.
- DMCertResp.htm (in temp) – Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
- DmClientSetup.log – Records client setup data on mobile device clients.
- DmClientXfer.log – Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
- DmCommonInstaller.log – Records client transfer file installation for setting up mobile device client transfer files on client computers.
- DmInstaller.log – Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
- DmInvExtension.log – Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
- DmSvc.log – Records mobile device management service data on mobile device clients.
Operating System Deployment Troubleshooting Log Files
You can refer to the below log files to troubleshoot SCCM operating system deployment issues.
| OS Deployment Log File Name | Description | OSD Log File Location |
|---|---|---|
| CAS.log | Records details when distribution points are found for referenced content. | Client Computer |
| ccmsetup.log | Provides information about client-based operating system actions. Can be used to troubleshoot client installation problems. | Client Computer |
| CreateTSMedia.log | Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager administrator console. | Computer that runs Configuration Manager console. |
| Dism.log | Records driver installation actions or update application actions for offline servicing. | Site system server |
| Distmgr.log | Records details about the configuration of enabling a distribution point for Preboot Execution Environment (PXE). | Site system server |
| DriverCatalog.log | Records details about device drivers that have been imported into the driver catalog. | Site system server |
| mcsisapi.log | Records information for multicast package transfer and client request responses. | Site system server |
| mcsexec.log | Records health check, namespace, session creation, and certificate check actions. | Site system server |
| mcsmgr.log | Records changes to configuration, security mode, and availability. | Site system server |
| mcsprv.log | Records multicast provider interaction with Windows Deployment Services (WDS). | Site system server |
| MCSSetup.log | Records details about multicast server role installation. | Site system server |
| MCSMSI.log | Records details about multicast server role installation. | Site system server |
| Mcsperf.log | Records details about multicast performance counter updates. | Site system server |
| MP_ClientIDManager.log | Records management point responses to client ID requests that task sequences start from PXE or boot media. | Site system server |
| MP_DriverManager.log | Records management point responses to Auto Apply Driver task sequence action requests. | Site system server |
| OfflineServicingMgr.log | Records details of offline servicing schedules and update apply actions on operating system Windows Imaging Format (WIM) files. | Site system server |
| Setupact.log | Records details about Windows Sysprep and setup logs. | Client Computer |
| Setupapi.log | Records details about Windows Sysprep and setup logs. | Client Computer |
| Setuperr.log | Records details about Windows Sysprep and setup logs. | Client Computer |
| smpisapi.log | Records details about the client state capture and restore actions, and threshold information. | Client Computer |
| Smpmgr.log | Records details about the results of state migration point health checks and configuration changes. | Site system server |
| loadstate.log | Records details about the User State Migration Tool (USMT) and restoring user state data. | Client Computer |
| smpperf.log | Logs the state migration point performance counter updates. | Site system server |
| smspxe.log | Records details about the responses to clients that use PXE boot, and details about the expansion of boot images and boot files. | Site system server |
| smssmpsetup.log | Records installation and configuration details about the state migration point. | Site system server |
| SMS_PhasedDeployment.log | Log file for phased deployments. | Top-level site in the Configuration Manager hierarchy. |
| Smsts.log | General location for all operating system deployment and task sequence log events. | Client Computer |
| TSAgent.log | Records the outcome of task sequence dependencies before starting a task sequence. | Client Computer |
| smpmsi.log | Records installation and configuration details about the state migration point. | Site system server |
| TaskSequenceProvider.log | Provides information about task sequences when they are imported, exported, or edited. | Site system server |
| scanstate.log | Records details about the User State Migration Tool (USMT) and capturing user state data. | Client Computer |
Network Access Protection Log Files
- Ccmcca.log – Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
- CIAgent.log – Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log – provides more informative details on installing the software updates required for compliance.
- locationservices.log – Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
- SDMAgent.log – Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
- SMSSha.log – The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.
SCCM Log Files Related to Packages and Programs
Use these SCCM log files when you troubleshoot issues related to packages and programs.
| Package Log File | Description | Log File Location |
|---|---|---|
| colleval.log | Records details about when collections are created, changed, and deleted by the Collection Evaluator. | Site Server |
| execmgr.log | Records details about packages and task sequences that run. | Client Machine |
System Health Validator Point Log Files
- Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
- SmsSHV.log – The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
- SmsSHVADCacheClient.log – Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
- SmsSHVCacheStore.log – Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
- SmsSHVRegistrySettings.log – Records any dynamic changes to the System Health Validator component configuration while the service is running.
- SmsSHVQuarValidator.log – Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLMSOFTWAREMicrosoftSMSSHVLogging@GLOBAL
Desired Configuration Management Log Files
Use these SCCM log files when you troubleshoot issues related to desired configuration manager.
| DCM Log files Name | Desciption | DCM Log File Location |
| ciagent.log | Provides information about downloading, storing, and accessing assigned configuration baselines. | SCCM Site Server |
| dcmagent.log | Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes. | SCCM Site Server |
| discovery.log | Provides detailed information about the Service Modeling Language (SML) processes. | SCCM Site Server |
| sdmagent.log | Provides information about downloading, storing, and accessing configuration item content. | SCCM Site Server |
| sdmdiscagent.log | Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items. | SCCM Site Server |
SCCM Wake On LAN Log Files
Use these SCCM log files when you troubleshoot issues related to wake on LAN.
| WOL Server Log File Name | Description | WOL Log File Location |
|---|---|---|
| Wolmgr.log | Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN | SCCM Site Server |
| WolCmgr.log | Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried. | SCCM Site Server |
Software Updates Site Server Log Files
Following are the software update site server log files.
- ciamgr.log – Provides information about the addition, deletion, and modification of software update configuration items.
- distmgr.log – Provides information about the replication of software update deployment packages.
- objreplmgr.log – Provides information about the replication of software updates notification files from a parent to child sites.
- PatchDownloader.log – Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
- replmgr.log – Provides information about the process for replicating files between sites.
- smsdbmon.log – Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
- SUPSetup – Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
- WCM.log – Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
- WSUSCtrl.log – Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
- wsyncmgr.log -Provides information about the software updates synchronization process.
WSUS Server Log Files
The WSUS server log files are located in the %ProgramFiles%\Update Services\LogFiles folder.
| WSUS Server Log File Name | Description | WSUS Log File Location |
|---|---|---|
| Change.log | Provides information about the WSUS server database information that has changed. | WSUS Server |
| SoftwareDistribution.log | Provides information about the software updates that are synchronized from the configured update source to the WSUS server database. | WSUS Server |
Software Updates Client Computer Log Files
- CAS.log – Provides information about the process of downloading software updates to the local cache and cache management.
- CIAgent.log – Provides information about processing configuration items, including software updates.
- LocationServices.log – Provides information about the location of the WSUS server when a scan is initiated on the client.
- PatchDownloader.log – Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
- PolicyAgent.log – Provides information about the process for downloading, compiling, and deleting policies on client computers.
- PolicyEvaluator – Provides information about the process for evaluating policies on client computers, including policies from software updates.
- RebootCoordinator.log – Provides information about the process for coordinating system restarts on client computers after software update installations.
- ScanAgent.log – Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
- ScanWrapper – Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
- SdmAgent.log – Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
- ServiceWindowManager.log – Provides information about the process for evaluating configured maintenance windows.
- smscliUI.log – Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
- SmsWusHandler – Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
- StateMessage.log – Provides information about when software updates state messages are created and sent to the management point.
- UpdatesDeployment.log – Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
- UpdatesHandler.log – Provides information about software update compliance scanning and about the download and installation of software updates on the client.
- UpdatesStore.log – Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
- WUAHandler.log – Provides information about when the Windows Update Agent on the client searches for software updates.
- WUSSyncXML.log – Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
Windows Update Agent Log File
- WindowsUpdate.log – Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.
Windows Servicing SCCM Log Files
Following are the SCCM log files related to Windows Servicing.
| Windows Servicing Log File Name | Description | Servicing Log File Location |
| CBS.log | Records servicing failures related to changes for Windows Updates or roles and features. | Client Machine |
| DISM.log | Records all actions using DISM | Client Machine |
| setupact.log | Primary log file for most errors that occur during the Windows installation process. The log file is located in the %windir%$Windows.~BT\sources\panther folder. | Client Machine |
Cloud Management Gateway Log Files
The following table lists the SCCM log files that contain information related to the cloud management gateway.
| Cloud Management Gateway Log File Name | Description | CMG Log Files Location |
|---|---|---|
| SMS_Cloud_ProxyConnector.log | Records details about setting up connections between the cloud management gateway service and the cloud management gateway connection point. | This log file is located on site system server – C:\Program Files\Microsoft Configuration Manager\Logs |
| CloudMgr.log | This file logs details related to cloud management gateway service, ongoing service status, and all the data associated with the service. | On site server – C:\Program Files\Microsoft Configuration Manager\Logs |
| CMGContentService.log | This log records the details of the service when you enable a CMG to also serve content from Azure storage. | %approot%\logs on your Azure server |
| CMGService.log | Records details about the cloud management gateway (CMG) service core component in Azure. | %approot%\logs on your Azure server |
| CMGHttpHandler.log | This log has been removed. The component functionality is merged into the CMG service component. Therefore see the CMGService.log instead. | %approot%\logs on your Azure server |
| CMGSetup.log | Records details about the second phase of the cloud management gateway deployment (local deployment in Azure) | %approot%\logs on your Azure server |
Desktop Analytics Log Files
You can use the following log files for Desktop Analytics troubleshooting.
| Desktop Analytics Log File Name | Description | Desktop Analytics Log File Location |
| M365AHandler.log | Logs information about the Desktop Analytics settings policy | Client Machine – C:\Windows\CCM\Logs |
| M365AUploadWorker.log | Information about collection and device upload from Configuration Manager to Microsoft cloud | Service connection point |
| M365ADeploymentPlanWorker.log | Logs information about deployment plan sync from Desktop Analytics cloud service to on-premises SCCM | Service connection point |
| M365ADeviceHealthWorker.log | Information about device health upload from Configuration Manager to Microsoft cloud | Service connection point |
| SmsAdminUI.log | Information about Configuration Manager console activity, like configuring the Azure cloud services | Service connection point |
Endpoint Analytics Log Files
Troubleshooting Endpoint Analytics can be done with the following log files.
| Endpoint Analytics Log File Name | Description | Log File Location |
| UXAnalyticsUploadWorker.log | Records data upload to the service for endpoint analytics. | Site server |
| SensorWmiProvider.log | Records the activity of the WMI provider for the endpoint analytics sensor. | Client |
| SensorEndpoint.log | Records the execution of endpoint analytics policy and upload of client data to the site server. | Client |
| SensorManagedProvider.log | Records the gathering and processing of events and information for endpoint analytics. | Client |
Endpoint Protection Log Files
Listed below are the SCCM Endpoint Protection log files and locations.
| Endpoint Protection Log Files Names | Description | Endpoint Protection Log File Location |
| EndpointProtectionAgent.log | Records details about the installation of the Endpoint Protection client and the application of antimalware policy to that client. | Client |
| EPCtrlMgr.log | Records details about the syncing of malware threat information from the Endpoint Protection role server with the Configuration Manager database. | Site system server |
| EPMgr.log | Monitors the status of the Endpoint Protection site system role. | Site system server |
| EPSetup.log | Provides information about the installation of the Endpoint Protection site system role. | Site system server |
Exchange Connector Log Files
The following logs contain information related to the Exchange Server connector.
| Exchange Connector Log File Name | Description | Log file Location |
| easdisc.log | Records the activities and the status of the Exchange Server connector. | Site Server |
Power Management Log Files
The following SCCM log files contain information related to the Power Management.
| Power Management Log File Name | Description | Log file Location |
|---|---|---|
| pwrmgmt.log | Records details about power management activities on the client computer, including monitoring and the enforcement of settings by the Power Management Client Agent. | Client Computer |
Role-Based Administration Log Files
The following table lists the SCCM log files that contain information related to managing role-based administration.
| Role Based Administration Log File Name | Description | Log file Location |
|---|---|---|
| hman.log | Records information about site configuration changes and the publishing of site information to Active Directory Domain Services. | Site server |
| SMSProv.log | Records WMI provider access to the site database. | Computer with the SMS Provider |
Software Metering Log Files
The following table lists the SCCM log files that contain information related to software metering.
| Software Metering Log File Name | Description | Log file Location |
|---|---|---|
| mtrmgr.log | Monitors all software metering processes. | Site server |
SCCM Software Center Log Files
The following table lists the SCCM log files that contain information related to software center.
| Software Center Log File Name | Description | Log file Location |
|---|---|---|
| SCClient_domain@username_1.log | Records the activity in Software Center for the specified user on the client computer. | Client computer |
| SCClient_domain@username_2.log | Records the historical activity in Software Center for the specified user on the client computer. | Client computer |
| Scheduler.log | Records activities of scheduled tasks for all client operations. | Client computer |
| SCNotify_domain@username_1.log | Records the activity for notifying users about software for the specified user. | Client computer |
| SCNotify_domain@username_1-date_time.log | Records the historical information for notifying users about software for the specified user. | Client computer |
SCCM Distribution Point Log Files
The below table lists the SCCM distribution point log files that help you to troubleshoot issues with remote DP.
| Software Distribution Point Log File Name | Description | Log file Location |
|---|---|---|
| distmgr.log | Records details about package creation, compression, delta replication, and information updates. It can also include other activities from the distribution manager component. | Site Server |
| PkgXferMgr.log | Records the actions of the SMS_Executive component that is responsible for sending content from a primary site to a remote distribution point. | Site Server |
| SMSdpmon.log | Records details about the distribution point health monitoring scheduled task that is configured on a distribution point. | Site Server |
SCCM Reporting Services Point Log Files
The below table lists all the Configuration Manager SSRS log files that are useful for troubleshooting reporting services point issues. Refer to the following step-by-step guide to install reporting services point role for SCCM.
| SSRS Log File Name | Description | Log File Location |
|---|---|---|
| srsrp.log | Records information about the activity and status of the reporting services point. | Site System Server |
| srsrpMSI.log | Records detailed results of the reporting services point installation process from the MSI output. | Site System Server |
| srsrpsetup.log | Records results of the reporting services point installation process. | Site System Server |
| compmon.log | Records the status of component threads monitored for the site server. | Site System Server |
| smsexec.log | Records the processing of all site server component threads. | Site System Server |
SCCM Application Groups Log Files
Use the below ConfigMgr log files to troubleshoot the issues related to the application groups deployment using SCCM.
| Application Groups Log File Name | Description | Log File Location |
|---|---|---|
| AppGroupHandler.log | Records detection and enforcement information for application groups. | Client computer |
| AppEnforce.log | Records details about enforcement actions (install and uninstall) taken for applications on the client. | Client computer |
| SettingsAgent.log | Enforcement of specific applications, records orchestration of application group evaluation, and details of co-management policies. | Client computer |
Where is the SCCM Server Logs Location?
The SCCM server logs are located in DRIVE-Letter:\Program Files\Microsoft Configuration Manager\Logs.
Where is the SCCM Client Logs Location?
The client logs are located in C:\Windows\CCM\Logs folder.
How do I view SCCM logs?
To view the logs, you must use the Configuration Manager log viewer tool CMTrace. The CMTrace tool is located in the /SMSSETUP/TOOLS.
Hello everyone,
Really helpful guide for SCCM related log files.
Which logs files should I look for application installation deployments where it fails in some computers?
For example, installation of a browser (edge, chrome etc.) through configuration manager.
It is really convenient to look on the client side.
Hi Prajwal,
I’m wondering if there is any log for downloading CM Updates and Hotfixes.
In Updates and Servicing, right click on Configurattion Manager Hotfix, and select Download! Is there any log that show the downloading progress?
Thanks in advance
Nizar
Review dmpdownloader.log.
Thanks 🙂
How can I populate smsts.log file during OSD/TS when executing some PowerShell script?
I have a post published that shows how you can get the smsts.log file during TS failure or while the TS is running.
WE have monthly MS security patching activity however client status is not getting updating or taking very long time.
1. If I check client machine manually I can see everything is completed however in console under deployment status server still “Pending System Restart”.
2. Morning 9 AM everything is completed and not its 6 PM but still my 100 servers showing “Pending System Restart”
3. I did client reboot 3 times, run all cycles couple of times..still no change.
4. For few clients I did rename “Software Distribution” and run all cycle..but no change.
I had review my “site status” and “Component Status” but no error or critical. Requesting your guidence..Please help
please guide
Hello Prajwal,
I see that few machines are not getting updated from 1809 to 1909 and when we go to SC, we can see the setup however it does not install and failed. Also in few machines it just shows installing and stuck over there but never succeed.
Could you please suggest what are the steps we can try to resolve this.
I feel probably , since the employees are working remotely and the content is not properly downloading .
thanks alot prajwal desai
Hello
Are you sure this MP_Sinv.log – Converts XML hardware inventory records from clients and copies them to the site server, and not Software inventory?
can you explain MP troubleshooting and DP trouble shooting?
That is going to be a vast topic. What exactly are you looking for ?.
Where are all the log for the SCCM Maintenance jobs that run daily/weekly/monthly?
Anyone ? 🙂 I’m looking for the logging of the task “Delete Aged User Device Affinity Data”.
Like 40% of all the primary user info is gone…
These are SQL maintenance tasks and not SCCM per se. You can see them from the SQL Server Agent jobs
hallo, i tried to push install the ccm setup client, and then i run the log file (ccm setup), and i get 7/0 return code, but from the client side there is no configuration manager, and sometime there is just only 2 components in it. please answer, i need your help.
regard.
Thanks for the useful info. Is there a way to track to progress of an Software Update Group? For an existing rule/SUG, I run the ADR, the software update group is updated with some new updates. There are some updates in the All Updates folder, these ‘should’ be added to the SUG. Is there a way to monitor this progress?
Ji Prajwal,
Thanks for sharing such important information on your blogs. I am currently trying to check the log file CITaskMgr.log on my server for SCCM but can’t really find it. Can you please suggest what path can I use to trace this file? I am currently having issue with one of applications that was working all fine but all of a sudden stopped installing on 90 percent of devices within our organisation while it’s still installing fine on other 10 percent devices. I have checked the boundary ip address range which is set to our organisation’s network range and can’t really find the issue.
Would really appreciate any sort of suggestions from you.
Thanks,
Bharat Sharma
TYTYTYTYTYT!
Hey can you please suggest a Patching log flow at client end?
Thank you
These logs are very useful for me to troubleshoot the issues and getting the sccm information.
Thanks Prajwal.
Thanks Sunil.
Hi Prajwal,
Please can you tell which version of SCCM this article is about as I am using SCCM12 CB update 1706 and I am not able to find many of these logs. One of the logs I was looking for is the DmCertEnroll.log. I have a issue where our Intune/SCCM (Hybrid) enrolled Android 7.0 and Windows 8.1 mobile devices keep getting multiple user certificates issued to them from our NDES server. So I was hoping that this log would help me find out why this was happening.
Thanks
Sarah
Hi Prajwal,
Can you please provide step by step or sequence of logs in order according to flow, to be checked for Software (Application and package), Software update, etc..
Really happy 🙂 to know that your problem is resolved.
The link suggested was really good, but it didn’t resolved my problem. Till now I have followed below steps to resolve my problem.
We have 1 Central and 4 Primary Sites and 4 Primary have their Secondary Sites
Only 1 Primary and Its 1 Secondary site has this Problem.
I am Pushing Patches from Central Site to Primary Site.
1) I have removed the issue site from the Package – Dist. Point and re-added
2) I have removed it from the SCCM Database from Central and Primary Site and again re-distributed the Package but no Luck. Despool.log file was giving Hash Algorithm from Central site is not valid Public Key, and it is Adding and removing Package is kept on goinig
3) I have also tried your Link, and Exchanged the Public Key Manually Between sites, but still no luck.
4) I have also tried disabling the option Requires Exchange of Public Key option from Site Properties.
Can you please help me on this further?????
Thanks
Amol Bhatt
Hi Prajwal,
I tried the link which you provided. I have exchanged Public Keys between sites but still the result is same. Its is giving me the same error on my Primary site
“SMS Despooler received an instruction and package file from site CSS that contains either software distribution data or inter-site replication data, however either the signature on the package or the hash algorithm ID used for the signature is not valid, the despooler will delete the instruction and the package file.”
Request you to please suggest if any log files I need to check apart from dspooler,distmgr,sender…..
Thanks
Amol Bhatt
@Anmol – I check the link which you provided in the last link and saw your comment that “Thank You ….This resolved my Issue. We were struggling since 3 months and those 10 steps resolved my Problem …Many thanks”/ Has the issue been resolved ?
I was about to suggest you to disable the secure key exchange requirements from the primary and all secondary site servers.
Thank You for the Link Prajwal,
This issue is occurring for all the Package on one Primary Site and that Site also have 1 Secondary Site.
So in total there are 2 sites affected and none of the Package is getting distributed on that 2 sites.
Thanks,
Amol
Hi Prajwal,
Thanks for the troubleshooting Library. I have one query, On one of the Primary site, my windows update package is not getting distributed in proper manner. When i see the Log file Sender.log from Central Site from where i am distributing patches , log file says package is distributed to Primary site, but i can not see any of the respective files on the Primary site related to that particular package.
When i checked the log file dspooler.log of Primary site, it is giving me following error
“SMS Despooler received an instruction and package file from site CSS that contains either software distribution data or inter-site replication data, however either the signature on the package or the hash algorithm ID used for the signature is not valid, the despooler will delete the instruction and the package file.”
Request you to help me on this. This is very critical for me.
Thanks
Amol Bhatt
Is this for a single package or for all packages ?
Have you extended the schema correctly ?
Very Informative. Really an Awesome Library for SCCM.
Thank you Prajwal
Thank you Sirisha. Hope this blog helped you.. 🙂
Hello Prajwal,
May be I am wrong but smsdbmon log not only limited for software updates. it will records all database related changes.