Hi,

If you use SCCM server then its very important that you know about SCCM Logs because
Logs have all information about the product configuration.

SCCM 2007 Logs:-

Client Log Files

The Configuration Manager 2007 client logs are located in one of the following locations: · On computers that serve as management points, the client logs are located in the SMS_CCM\Logs folder. · On all other computers, the client log files are located in the %Windir%\System32\CCM\Logs folder or the %Windir%\SysWOW64\CCM\Logs.The following table lists and describes the client log files.

Log File Name

Description

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 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.)

Site Server Log Files

Most Configuration Manager 2007 site server log files are located in the <InstallationPath>\LOGS folder. Because Configuration Manager 2007 relies heavily on Microsoft Internet Information Services (IIS), you can review the IIS log file for additional errors that relate to client access to the IIS server. The IIS log file is located in the %Windir%\System32\logfiles\W3SVC1 folder on the IIS server. The following table lists and describes the site server log files.

Log File Name

Description

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 SMS\INBOXES 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 SMS\INBOXES 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.

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.

Management Point Log Files

If management points are installed in the site hierarchy, management point log files are stored in the SMS_CCM\LOGS folder on the management point computer. The following table lists and describes the management point log files.

Log File Name

Description

MP_Ddr.log

Records the conversion of XML.ddr records from clients, and copies them to the site server.

MP_GetAuth.log

Records the status of the site management points.

MP_GetPolicy.log

Records policy information.

MP_Hinv.log

Converts XML hardware inventory records from clients and copies the files to the site server.

MP_Location.log

Records location manager tasks.

MP_Policy.log

Records policy communication.

MP_Relay.log

Copies files that are collected from the client.

MP_Retry.log

Records the hardware inventory retry processes.

MP_Sinv.log

Converts XML hardware inventory records from clients and copies them to the site server.

MP_Status.log

Converts XML.svf status message files from clients and copies them to the site server.

Operating System Deployment Log Files

The following table lists and describes the operating system deployment log files.

Log File Name

Description

CCMSetup.log

Provides information about client-based operating system actions.

CreateTSMedia.log

Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.

DriverCatalog.log

Provides information about device drivers that have been imported into the driver catalog.

MP_ClientIDManager.log

Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.

MP_DriverManager.log

Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.

MP_Location.log

Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.

Pxecontrol.log

Provides information about the PXE Control Manager.

PXEMsi.log

Provides information about the PXE service point and is generated when the PXE service point site server has been created.

PXESetup.log

Provides information about the PXE service point and is generated when the PXE service point site server has been created.

Setupact.log Setupapi.log Setuperr.log

Provide information about Windows Sysprep and setup logs.

SmpIsapi.log

Provides information about the state migration point Configuration Manager 2007 client request responses.

Smpmgr.log

Provides information about the results of state migration point health checks and configuration changes.

SmpMSI.log

Provides information about the state migration point and is generated when the state migration point site server has been created.

Smsprov.log

Provides information about the SMS provider.

Smspxe.log

Provides information about the Configuration Manager 2007 PXE service point.

SMSSMPSetup.log

Provides information about the state migration point and is generated when the state migration point site server has been created.

Smsts.log

General location for all operating system deployment and task sequence log events.Log file location:· If task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: \logs· If task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG· If task sequence completes when running in WindowsPE: \SMSTSLOG

Note

is %windir%\system32\ccm\logs for most Configuration Manager 2007 clients and is \SMS_CCM for the Configuration Manager 2007 site server. For 64-bit operating systems, it is %windir%\SysWOW64\ccm\logs.

TaskSequenceProvider.log

Provides information about task sequences when they are imported, exported, or edited.

USMT Log loadstate.log

Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.

USMT Log scanstate.log

Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

By default, client log files related to Network Access Protection are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs.The following table lists and describes the Network Access Protection log files.

Log File Name

Description

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.


Posted by,

Vinesh Rathi