SCCM 2012 R2 Server Log Files

SCCM 2012 R2 Server Log Files Troubleshooting

Configuration Manager Site Server Log Files

The following sections list log files found on the site server or related to specific site system roles.

Site Server and Site System Server Logs

The following table lists the log files found on the Configuration Manager site server and site system servers.

Log name	Description	Computer with log file
adctrl.log	Records enrollment processing activity.	Site server
ADForestDisc.log	Records Active Directory Forest Discovery actions.	Site server
ADService.log	Records account creation and security group details in Active Directory.	Site server
adsgdis.log	Records Active Directory Group Discovery actions.	Site server
adsysdis.log	Records Active Directory System Discovery actions.	Site server
adusrdis.log	Records Active Directory User Discovery actions.	Site server
ccm.log	Records client push installation activities.	Site server
CertMgr.log	Records the certificate activities for intra-site communications.	Site system server
chmgr.log	Records activities of the client health manager.	Site server
Cidm.log	Records changes to the client settings by the Client Install Data Manager (CIDM).	Site server
colleval.log	Records details about when collections are created, changed, and deleted by the Collection Evaluator.	Site server
compmon.log	Records the status of component threads monitored for the site server.	Site system server
compsumm.log	Records Component Status Summarizer tasks.	Site server
ComRegSetup.log	Records the initial installation of COM registration results for a site server.	Site system server
dataldr.log	Records information about the processing of Management Information Format (MIF) files and hardware inventory in the Configuration Manager database.	Site Server
ddm.log	Records activities of the discovery data manager.	Site server
despool.log	Records incoming site-to-site communication transfers.	Site server
distmgr.log	Records details about package creation, compression, delta replication, and information updates.	Site server
EPCtrlMgr.log	Records information about the synchronization of malware threat information from the Endpoint Protection site system role server into the Configuration Manager database.	Site server
EPMgr.log	Records 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
EnrollSrv.log	Records activities of the enrollment service process.	Site system server
EnrollWeb.log	Records activities of the enrollment website process.	Site system server
fspmgr.log	Records activities of the fallback status point site system role.	Site system server
hman.log	Records information about site configuration changes, and the publishing of site information in Active Directory Domain Services.	Site server
Inboxast.log	Records the files that are moved from the management point to the corresponding INBOXES folder on the site server.	Site server
inboxmgr.log	Records file transfer activities between inbox folders.	Site server
inboxmon.log	Records the processing of inbox files and performance counter updates.	Site server
invproc.log	Records the forwarding of MIF files from a secondary site to its parent site.	Site server
migmctrl.log	Records information for Migration actions involving migration jobs, shared distribution points, and distribution point upgrades.	The top-level site in the System Center 2012 Configuration Manager hierarchy, and each child primary site Note In a multi-primary site hierarchy, use the log file created at the central administration site.
mpcontrol.log	Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.	Site system 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 of about the management point installation.	Site server
MPSetup.log	Records the management point installation wrapper process.	Site server
netdisc.log	Records Network Discovery actions.	Site server
ntsvrdis.log	Records the discovery activity of site system servers.	Site server
Objreplmgr	Records the processing of object change notifications for replication.	Site server
offermgr.log	Records advertisement updates.	Site server
offersum.log	Records the summarization of deployment status messages.	Site server
OfflineServicingMgr.log	Records the activities of applying updates to operating system image files.	Site server
outboxmon.log	Records the processing of outbox files and performance counter updates.	Site server
PerfSetup.log	Records the results of the installation of performance counters.	Site system 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
policypv.log	Records updates to the client policies to reflect changes to client settings or deployments.	Primary site server
rcmctrl.log	Records the activities of database replication between sites in the hierarchy.	Site server
replmgr.log	Records the replication of files between the site server components and the Scheduler component.	Site server
ResourceExplorer.log	Records errors, warnings, and information about running the Resource Explorer.	The computer that runs the Configuration Manager console
ruleengine.log	Records details about automatic deployment rules for the identification, content download, and software update group and deployment creation.	Site server
schedule.log	Records details about site-to-site job and file replication.	Site server
sender.log	Records the files that transfer by file-based replication between sites.	Site server
sinvproc.log	Records information about the processing of software inventory data to the site database.	Site server
sitecomp.log	Records details about the maintenance of the installed site components on all site system servers in the site.	Site server
sitectrl.log	Records site setting changes made to site control objects in the database.	Site server
sitestat.log	Records the availability and disk space monitoring process of all site systems.	Site server
SmsAdminUI.log	Records Configuration Manager console activity.	The computer that runs the Configuration Manager console
SMSAWEBSVCSetup.log	Records the installation activities of the Application Catalog web service.	Site system server
smsbkup.log	Records output from the site backup process.	Site server
smsdbmon.log	Records database changes.	Site server
SMSENROLLSRVSetup.log	Records the installation activities of the enrollment web service.	Site system server
SMSENROLLWEBSetup.log	Records the installation activities of the enrollment website.	Site system server
smsexec.log	Records the processing of all site server component threads.	Site server or site system server
SMSFSPSetup.log	Records messages generated by the installation of a fallback status point.	Site system server
SMSPORTALWEBSetup.log	Records the installation activities of the Application Catalog website.	Site system server
SMSProv.log	Records WMI provider access to the site database.	Computer with the SMS Provider
srsrpMSI.log	Records detailed results of the reporting point installation process from the MSI output.	Site system server
srsrpsetup.log	Records results of the reporting point installation process.	Site system server
statesys.log	Records the processing of state system messages.	Site server
statmgr.log	Records the writing of all status messages to the database.	Site server
swmproc.log	Records the processing of metering files and settings.	Site server

SCCM Log Files for Apple Mac,ipad and iPhone

SCCM Log Files for Apple Mac,ipad and iPhone

Client for Mac Computers

For System Center 2012 Configuration Manager SP1 and later:

The Configuration Manager client for Mac computers records information in the following log files.

Log name	Details
CCMClient-<date_time>.log	Records activities that are related to the Mac client operations, which includes application management, inventory, and error logging. This log file is located in the folder /Library/Application Support/Microsoft/CCM/Logs on the Mac computer.
CCMAgent-<date_time>.log	Records information that is related to client operations, which includes user logon and logoff operations and Mac computer activity. This log file is located in the folder ~/Library/Logs on the Mac computer.
CCMNotifications-<date_time>.log	Records activities that are related to Configuration Manager notifications displayed on the Mac computer. This log file is located in the folder ~/Library/Logs on the Mac computer.
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. This log file is located in the folder ~/Library/Logs on the Mac computer.

Additionally, the log file SMS_DM.log on the site system server records communication between Mac computers and the management point that is enabled for mobile devices and Mac computers.

SCCM 2012 R2 Log files for Linux and Unix Machines - Troubleshooting

SCCM 2012 R2 Log files for Linux and Unix Machines - Troubleshooting

Client for Linux and UNIX

For System Center 2012 Configuration Manager SP1 and later:

The Configuration Manager client for Linux and UNIX records information in the following log files.

Tip
Beginning with client for Linux and UNIX from cumulative update 1, you can use CMTrace to view the log files for the client for Linux and UNIX.

Note
When you use the initial release of the client for Linux and UNIX and reference the documentation in this section, replace the following references for each file or process: Replace omiserver.bin with nwserver.bin Replace omi with nanowbem

Log name	Details
scxcm.log	This is the log file for the core service of the Configuration Manager client for Linux and UNIX (ccmexec.bin). This log file contains information about the installation and ongoing operations of ccmexec.bin. By default, this log file is created in the following location: /var/opt/microsoft/scxcm.log To change the location of the log file, edit /opt/microsoft/configmgr/etc/scxcm.conf and change the PATH field. You do not need to restart the client computer or service for the change to take effect. You can set the log level to one of four different settings: ERROR: Indicates problems that require attention. WARNING: Indicates possible problems for the client operations. INFO: More detailed logging that indicates the status of various events on the client. TRACE: Verbose logging that is typically used to diagnose problems. To change the log level, edit /opt/microsoft/configmgr/etc/scxcm.conf and change each instance of the tag MODULE to the desired log level.
scxcmprovider.log	This is the log file for the CIM service of the Configuration Manager client for Linux and UNIX (omiserver.bin). This log file contains information about the ongoing operations of nwserver.bin. By default, this log is created in the following location: /var/opt/microsoft/configmgr/scxcmprovider.log To change the location of the log file, edit /opt/microsoft/omi/etc/scxcmprovider.conf and change the PATH field. You do not need to restart the client computer or service for the change to take effect. You can set the log level to one of three different settings: ERROR: Indicates problems that require attention. WARNING: Indicates possible problems for the client operations. INFO: More detailed logging that indicates the status of various events on the client. To change the log level, edit /opt/microsoft/omi/etc/scxcmprovider.conf and change each instance of the tag MODULE to the desired log level.

Under normal operating conditions the ERROR log level should be used. The ERROR level of logging creates the smallest log file. As the log level is increased from ERROR to WARNING to INFO to TRACE, each step results in a larger log file as more data is written to the log file.

Manage Log Files for the Client for Linux and UNIX Client

The client for Linux and UNIX does not limit the maximum size of the client log files, nor does the client automatically copy the contents of its .LOGfiles to another file such as a .LO_ file. If you want to control the maximum size of log files, implement a process to manage the log files independent from the Configuration Manager client for Linux and UNIX.

For example, you can use the standard Linux and UNIX command logrotate to manage the size and rotation of the clients log files. The Configuration Manager client for Linux and UNIX provides an interface that enables logrotate to signal the client as to when the log rotation completes, allowing the client to resume logging to the log file.

For information about logrotate, see the documentation for the Linux and UNIX distributions that you use.

SCCM 2012 R2 Log Files for Troubleshooting -Client Troubleshooting

SCCM 2012 R2 Log Files for Troubleshooting

Client Operations

The following table lists the log files found on the Configuration Manager client.

Log name	Description
CAS.log	Content Access service. Maintains the local package cache on the client.
Ccm32BitLauncher.log	Records actions for starting applications on the client marked as "run as 32bit".
CcmEval.log	Records Configuration Manager client status evaluation activities and details for components that are required by the Configuration Manager client.
CcmEvalTask.log	Records the Configuration Manager client status evaluation activities that are initiated by the evaluation scheduled task.
CcmExec.log	Records activities of the client and the SMS Agent Host service. This log file also includes information about enabling and disabling wake-up proxy.
CcmMessaging.log	Records activities related to communications between the client and management points.
CCMNotificationAgent.log	Records activities related to client notification operations.
Ccmperf.log	Records activities related to the maintenance and capture of data related to client performance counters.
CcmRestart.log	Records client service restart activity.
CCMSDKProvider.log	Records activities for the client SDK interfaces.
CertificateMaintenance.log	Maintains certificates for Active Directory Domain Services and management points.
CIDownloader.log	Records details about configuration item definition downloads.
CITaskMgr.log	Records tasks that are initiated for each application and deployment type, such as content download or install or uninstall actions.
ClientAuth.log	Records the signing and authentication activity for the client.
ClientIDManagerStartup.log	Creates and maintains the client GUID and identifies tasks performed during client registration and assignment.
ClientLocation.log	Records tasks that are related to client site assignment.
CMHttpsReadiness.log	Records the results of running the Configuration Manager HTTPS Readiness Assessment Tool. This tool checks whether computers have a PKI client authentication certificate that can be used for Configuration Manager.
CmRcService.log	Records information for the remote control service.
ContentTransferManager.log	Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access packages.
DataTransferService.log	Records all BITS communication for policy or package access.
EndpointProtectionAgent	Records information about the installation of the Endpoint Protection client and the application of antimalware policy to that client.
execmgr.log	Records details about packages and task sequences that run on the client.
ExpressionSolver.log	Records details about enhanced detection methods that are used when verbose or debug logging is enabled.
ExternalEventAgent.log	Records the history of Endpoint Protection malware detection and events related to client status.
FileBITS.log	Records all SMB package access tasks.
FileSystemFile.log	Records the activity of the Windows Management Instrumentation (WMI) provider for software inventory and file collection.
FSPStateMessage.log	Records the activity for state messages that are sent to the fallback status point by the client.
InternetProxy.log	Records the network proxy configuration and usage activity for the client.
InventoryAgent.log	Records activities of hardware inventory, software inventory, and heartbeat discovery actions on the client.
LocationCache.log	Records the activity for location cache usage and maintenance for the client.
LocationServices.log	Records the client activity for locating management points, software update points, and distribution points.
MaintenanceCoordinator.log	Records the activity for general maintenance task activity for the client.
Mifprovider.log	Records the activity of the WMI provider for .MIF files.
mtrmgr.log	Monitors all software metering processes.
PolicyAgent.log	Records requests for policies made by using the Data Transfer service.
PolicyAgentProvider.log	Records policy changes.
PolicyEvaluator.log	Records details about the evaluation of policies on client computers, including policies from software updates.
PolicyPlatformClient.log	Records the process of remediation and compliance for all providers located in %Program Files%\Microsoft Policy Platform, except the file provider.
PolicySdk.log	Records activities for policy system SDK interfaces.
Pwrmgmt.log	Records information about enabling or disabling and configuring the wake-up proxy client settings.
PwrProvider.log	Records the activities of the power management provider (PWRInvProvider) hosted in the Windows Management Instrumentation (WMI) service. On all supported versions of Windows, the provider enumerates the current settings on computers during hardware inventory and applies power plan settings.
SCClient_<domain>@<username>_1.log	Records the activity in Software Center for the specified user on the client computer.
SCClient_<domain>@<username>_2.log	Records the historical activity in Software Center for the specified user on the client computer.
Scheduler.log	Records activities of scheduled tasks for all client operations.
SCNotify_<domain>@<username>_1.log	Records the activity for notifying users about software for the specified user.
SCNotify_<domain>@<username>_1-<date_time>.log	Records the historical information for notifying users about software for the specified user.
setuppolicyevaluator.log	Records configuration and inventory policy creation in WMI.
SleepAgent_<domain>@<@SYSTEM_0.log	Main log file for wake-up proxy.
smscliui.log	Records usage of the Configuration Manager client in Control Panel.
SrcUpdateMgr.log	Records activity for installed Windows Installer applications that are updated with current distribution point source locations.
StatusAgent.log	Records 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.
UserAffinity.log	Records details about user device affinity.
VirtualApp.log	Records information specific to the evaluation of App-V deployment types.
Wedmtrace.log	Records operations related to write filters on Windows Embedded clients.
wakeprxy-install.log	Records installation information when clients receive the client setting option to enable wake-up proxy.
wakeprxy-uninstall.log	Records information about uninstalling wake-up proxy when clients receive the client setting option to disable wake-up proxy, if wake-up proxy was previously enabled.

How SCCM 2012 R2 Client Communication Process Works

How SCCM 2012 R2 Client Communication Process Works

Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process:

1. Client location services identify the site code and the MP it is supposed to connect to.
2. The client connects to the Management Point and downloads the policies.
3. Once the policies are downloaded it sends the heartbeat record to the server.
4.  Once the server receives this heartbeat record these are converted in to DDR and processed.  This will set the client flag to 1 which will make the client status display as Active in the console.
5.  On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to Inactive.
6.  So only if this process is completed and it continues to happen will the client remain reporting to the server.