Original works, allow reprint, please be sure to use hyperlinks in the form of the original source of the article, author information and this statement. Otherwise, the legal liability will be investigated. http://ycrsjxy.blog.51cto.com/618627/203174 all client and Site server components in Microsoft System Center Configuration Manager 2007 will process The information is recorded in a single log file. You can use the information in the client and site server log files to help you diagnose problems that may occur in the configuration Manager 2007 hierarchy. By default, the client and server component logging is enabled in Configuration Manager 2007.
Client log Files
The Configuration Manager 2007 client log files are located in one of the following locations: On the computer that is the management point, 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%windir%\syswow64\ccm\logs.
Cas
Content access Services. Maintain local packet caching.
CcmExec.log
Records the activity of the client and the SMS Agent Host service.
CertificateMaintenance.log
Certificate maintenance for Active Directory services and management points.
ClientIDManagerStartup.log
Create and maintain a client GUID.
ClientLocation.log
Site assignment tasks.
ContentTransferManager.log
Schedule Background Intelligent Transfer Service (BITS) or Server Message Block (SMB) to download or access the SMS package.
DataTransferService.log
Log all BITS traffic for a policy or package access
Execmgr.log
Records all advertisements that are running.
FileBITS.log
Log all SMB package access tasks
Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service packs)
The Windows Management Instrumentation (WMI) provider for software inventory and file collections.
InventoryAgent.log
Create Discovery Data Records (DDR) and hardware and software inventory records.
LocationServices.log
Find management points and distribution points.
Mifprovider.log
. MIF file for the WMI provider.
Mtrmgr.log
Monitor all software metering processes.
PolicyAgent.log
Request policy using the data transfer service.
PolicyAgentProvider.log
Records policy changes.
Policyuator.log
Records the new policy settings.
Remctrl.log
Records the start time of the remote control component (WUSER32).
Scheduler.log
Records the scheduled tasks for all client operations.
Smscliui.log
Records the use of the System Administration tool in Control Panel.
StatusAgent.log
Records the status messages created by the client component.
SWMTRReportGen.log
Generates a usage data report that is collected by the Count agent. (This data is recorded in Mtrmgr.log.) ）
Site Server log files
Most Configuration Manager 2007 site Server log files are located in the < Installation path >\logs folder. Because Configuration Manager 2007 is highly dependent on Microsoft Internet information Services (IIS), you can view the IIS log files for the presence of client access to the IIS server He was wrong. The IIS log files are located in the%windir%\system32\logfiles\w3svc1 folder on the IIS server.
Ccm.log
The Client Configuration Manager task.
Cidm.log
Use client Installation Data Manager (CIDM) to record changes to client settings.
Coll.log
Records are recorded when the collection calculator creates, changes, and deletes collections.
Compsumm.log
Records the Component Status Summarizer task.
Cscnfsvc.log
Records the Media Sender Acknowledgement service task.
Dataldr.log
Handles management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
Ddm.log
Use the Discovery Data Manager to save the DDR information to the Configuration Manager 2007 database.
Despool.log
Record incoming site-to-site communication transmissions
Distmgr.log
Record package creation, compression, incremental replication, and information updates.
Hman.log
Records site configuration changes and publishes site information in Active Directory Domain Services.
Inboxast.log
Records the files that are moved from the management point to the appropriate Sms\inboxes folder.
Inboxmgr.log
Record file maintenance.
Invproc.log
Records the processing of incremental MIF files from the Dataloader component of the client manifest file.
Mpcontrol.log
Records the registration of management points in WINS. The availability of the management point is logged every 10 minutes.
Mpfdm.log
Move the client files to the management point component of the appropriate Sms\inboxes folder.
MPMSI.log
Management point. msi installation log.
MPSetup.log
Record Management point installation wrapper process
Ntsvrdis.log
Configuration Manager 2007 Server discovery.
Offermgr.log
Record advertisement updates.
Offersum.log
Records the summary of the advertisement status message.
Policypv.log
Records updates to client policies to reflect changes to client settings or advertisements.
Replmgr.log
Records file replication between the site server component and the Scheduler component.
Rsetup.log
The report point installation log.
Sched.log
Records site-to-site jobs and package replication.
Sender.log
Records files that are sent to other subwebs and to the parent site.
Sinvproc.log
Log client software inventory data processing to the site database of Microsoft SQL Server.
Sitecomp.log
Records the maintenance of installed site components.
Sitectrl.log
Records Site settings changes to the Sitectrl.ct0 file.
Sitestat.log
Records the monitoring process for all site systems.
Smsdbmon.log
Record database changes.
Smsexec.log
Records the processing of all site server component threads.
Smsprov.log
Logs access to the site database by the WMI provider.
SMSReportingInstall.log
Record reporting points install the component to start the installation task and to process the configuration changes.
Srvacct.log
Records account maintenance When the site uses standard security.
Statmgr.log
Writes all status messages to the database.
Swmproc.log
Processes the count file and maintains the settings.
Administrative user interface log files are located in <installationpath>\adminui\ RepairWizard.log
Records errors, warnings, and information about the process of running the Repair Wizard.
ResourceExplorer.log
Logs errors, warnings, and information about running the resource manager.
SMSAdminUI.log
Log the ground Configuration Manager 2007 Console task when you connect to the Configuration Manager 2007 site.
Management point log Files
If a management point is installed in the site hierarchy, the management point log files are stored in the Sms_ccm\logs folder on the management point computer. Mp_ddr.log
Records the conversion of XML.DDR records from the client and copies them to the site server.
Mp_getauth.log
Records the status of the site management point.
Mp_getpolicy.log
Records policy information.
Mp_hinv.log
Converts the XML hardware inventory records from the client and copies the files to the site server.
Mp_location.log
Records the Location Manager task.
Mp_policy.log
Records policy communication.
Mp_relay.log
Copy the files collected from the client.
Mp_retry.log
Records the hardware inventory retry process.
Mp_sinv.log
Converts the XML hardware inventory records from the client and copies them to the site server.
MP_Status.log
Convert the XML.SVF status message files from the client and copy them to the site server.
mobile Device Management log files
If mobile device management is enabled in the site hierarchy, the mobile device management point log files are typically stored in the <configmgr installation path >\logs folder on the mobile device management point computer. DmClientHealth.log
Records the GUID of all mobile device clients that communicate with the device management point.
DmClientRegistration.log
Records registration requests and responses to requests from mobile device clients in native mode.
DmpDatastore.log
Records all site database connections and queries made by the device management point.
DmpDiscovery.log
Records all discovery data for the mobile device client on the device management point.
DmpFileCollection.log
Records data collected by mobile device files from mobile device clients on the device management point.
DmpHardware.log
Records hardware inventory data for the mobile device client 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 installed by the device management point.
DMPSetup.log
Records the mobile device management installation process.
DmpSoftware.log
Records mobile device software distribution data from mobile device clients on the device management point.
DmpStatus.log
Records the mobile device status message data from the mobile device client on the device management point.
FspIsapi.log
Records the fallback status point communication data from the mobile device client and client computer on the fallback status point.
mobile Device Management client logs
For information about the location of the log files on managed mobile devices and computers that are used to deploy mobile device clients, see How to configure logging for Windows Mobile and Windows CE devices. DmCertEnroll.log
Records the certificate enrollment data on the mobile device client.
Dmcertresp.htm (in \temp)
When the mobile device enrollment program requests a client authentication certificate on the mobile device client, the HTML response from the Certificate Server is logged.
DmClientSetup.log
Records client installation data on the mobile device client.
DmClientXfer.log
Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
DmCommonInstaller.log
Records client transfer file installation on a client computer that sets up a mobile device client transfer file.
DmInstaller.log
Records whether Dminstaller calls Dmclientsetup correctly, and if dmclientsetup on the mobile device client is successful or failed.
DmInvExtension.log
Log the manifest extension file installation that sets up the manifest extension file on the client computer.
DmSvc.log
Records mobile device Management Service data on the mobile device client.
operating System deployment log filesCCMSetup.log
Provides information about client-based operating system operations.
CreateTSMedia.log
Provides information about the 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
When the Configuration Manager 2007 Management point responds to a Configuration Manager 2007 client ID request from the boot media or PXE, the log provides information about the management point. This log is generated on the Configuration Manager 2007 Management point.
Mp_drivermanager.log
Provides information when a Configuration Manager 2007 Management Point 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
When the Configuration Manager 2007 Management Point responds to a request state store or frees a state store request from a State migration point, the log provides information about that management 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 that was generated when the PXE service Point site Server was created.
PXESetup.log
Provides information about the PXE service point that was generated when the PXE service Point site Server was created.
Setupact.logSetupapi.logSetuperr.log
Provides information about Windows Sysprep and the installation log.
SmpIsapi.log
Provides information about the State migration point Configuration Manager 2007 client request response.
Smpmgr.log
Provides information about health check results and configuration changes for state migration points.
SmpMSI.log
Provides information about the State migration point, which is generated when a state migration Point site Server has been created.
Smsprov.log
Provides information about the SMS provider.
Smspxe.log
Provides information about the Configuration Manager's PXE service point.
SMSSMPSetup.log
Provides information about the State migration point, which is generated when a 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 the task sequence finishes running in the full operating system (the Configuration Manager 2007 client is installed on the same computer): <CCM installation directory >\logs if the task sequence is not installed on the computer Configuration Manager 2007 Client Full operating system run-time complete:%temp%\smstslog if the task sequence is run in WindowsPE:< the maximum fixed partition >\smstslog attention
For most Configuration Manager 2007 clients, the <CCM installation directory > is%windir%\system32\ccm\logs, and for the Configuration Manager 2007 site server; <configuration Manager 2007 installs the drive >\SMS_CCM. For 64-bit operating systems,%windir%\syswow64\ccm\logs.
TaskSequenceProvider.log
When you import, export, or edit a task sequence, the log provides information about these task sequences.
USMT Log Loadstate.log
Provides information about the User State Migration Tool (USMT) about restoring user state data.
USMT Log Scanstate.log
Provides information about the USMT about capturing user state data.
Network Access Protection log files
By default, client log files related to network Access Protection can be found in%windir%\ccm\logs. For client computers that are also management points, you can find the log files in%programfiles%\sms_ccm\logs.
Ccmcca.log
Processing of records compliance evaluations is handled according to the Configuration Manager NAP policy, including remediation processing for each software update required for compliance.
CIAgent.log
Track the remediation process and compliance. However, the software update log file Updateshandler.log provides more detailed information about the software updates that are required to install compliance.
Locationservices.log
Used by other Configuration Manager features (for example, information about the client's assigned site), but when the client is remediated, it also contains information specific to network access protection. It records the names of the required remediation servers (management points, software update points, and distribution points that host the content required for compliance), which are also sent in the client health statement.
SDMAgent.log
Shared with the Configuration Manager features required to configure management, and contains procedures for tracking remediation and compliance. However, the software update log file Updateshandler.log provides more detailed information about the software updates that are required to install compliance.
SMSSha.log
The primary log file for the Configuration Manager Network Access Protection client, which contains information about the consolidated Health statement for the two Configuration Manager components: Location Service (LS) and Configuration Compliance Agent (CCA). This log file also contains information about the interaction between the Configuration Manager System Health Agent and the operating system NAP agent, as well as the Configuration Manager System Health Agent and the Configure Compliance agent and location service. It provides information about whether the NAP agent successfully starts, the health statement data, and the health statement response.
System Health Validator Point log files are located in%systemdrive%\smsshv\sms_shv\logs,ccmperf.log
Contains initialization information about the system health validator point performance counters.
SmsSHV.log
The primary log file of the system health verification point, which records the basic operations of the System Health Validator service, such as initialization progress.
SmsSHVADCacheClient.log
Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
SmsSHVCacheStore.log
Contains information about cache storage (used to hold Configuration Manager NAP health state references retrieved from Active Directory Domain Services), such as reading from storage and purging entries from local cache storage files. Cache storage is not configurable.
SmsSHVRegistrySettings.log
Records any dynamic changes to the System Health Validator component configuration when the service is running.
SmsSHVQuarValidator.log
Logs client Health statement information and processing operations. For complete information, change the registry key LogLevel from 1 to 0:hklm\software\microsoft\smsshv\logging\ in the following location @GLOBAL
Installation information for the system Health validator point can be found in the installation log file (as described in the following table) on the computer that is running Network policy server. <configmgrinstallationpath>\logs\smsshvsetup.log
Records whether the installation system Health Validator Point succeeded or failed (including the reason for the failure).
Required configuration Management log files
By default, the Configuration Manager 2007 client computer log files are located in%windir%\system32\ccm\logs or%windir%\syswow64\ccm\logs. For client computers that are also management points, the client log files are located in the Sms_ccm\logs folder. Ciagent.log
Provides information about downloading, storing, and accessing assigned configuration baselines.
Dcmagent.log
Provides high-level information about an assigned configuration baseline assessment and the required configuration management process.
Discovery.log
Provides detailed information about the Service Modeling Language (SML) process.
Sdmagent.log
Provides information about downloading, storing, and accessing the contents of a configuration item.
Sdmdiscagent.log
Provides high-level information about the evaluation process for objects and settings that are configured in a reference configuration item.
wake on LAN log file
The Configuration Manager 2007 site Server log files related to wake on LAN are located in the folder <configmgrinstallationpath>\logs on the site server. There is no client-wide wake on LAN log file. Wolmgr.log
Contains information about the wake-up process, such as when to wake up an advertisement or deployment configured for Wake on LAN.
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 retry wake-up packets.
Software Update site server log files
By default, the Configuration Manager 2007 site Server log files can be found in the < Installation path >\logs. Ciamgr.log
Provides information about adding, removing, and modifying software update configuration items.
Distmgr.log
Provides information about replication software update deployment packages.
Objreplmgr.log
Provides information about copying software update notification files from a parent site to a child site.
PatchDownloader.log
Provides procedural information about downloading software updates to a download destination on a site server from the update source specified in the Software updates metadata. Attention
On a 64-bit operating system and a 32-bit operating system that does not have Configuration Manager 2007 installed, PatchDownloader.log is created in the server log directory. On a 32-bit operating system, if the Configuration Manager 2007 client is installed, PatchDownloader.log is created in the client log directory.
Replmgr.log
Provides procedural information about copying files between sites.
Smsdbmon.log
Provides information about when a software update configuration item is inserted into the site server database, updated or deleted from the database, and a notification file is created for the software update component.
Supsetup
Provides information about the installation of the software update point. When the software update point installation is complete, the log file is written to "successful installation."
WCM.log
Provides information about the software update point configuration and information about connecting to a Windows server update Services (WSUS) Server for update categories, classifications, and languages for subscriptions.
WSUSCtrl.log
Provides information about the configuration of the site, the database connection, and the health of the WSUS server.
Wsyncmgr.log
Provides information about the software update synchronization process.
WSUS server log files
By default, the log files for WSUS that are running on the software Update Point site system role are located in%ProgramFiles%\Update services\logfiles. Change.log
Provides information about the WSUS server database information that has changed.
SoftwareDistribution.log
Provides information about software updates that are synchronized from a configured update source to the WSUS server database.
software updates client computer log files
By default, the Configuration Manager 2007 client computer log files can be found in%windir%\ccm\logs. For client computers that are also management points, you can find the log files in%programfiles%\sms_ccm\logs. CAS.log
Provides procedural information about downloading software updates to local cache and cache management.
CIAgent.log
Provides information about handling 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 procedural information about downloading software updates from an update source to a download destination on a site server. This log is only available on client computers that are configured as a synchronization host for the Microsoft Update Inventory Tool.
PolicyAgent.log
Provides procedural information about downloading, compiling, and deleting policies on client computers.
Policyuator
Provides procedural information about evaluating policies on client computers, including policies from software updates.
RebootCoordinator.log
Provides procedural information about reconciling a system restart on a client computer after a software update is installed.
ScanAgent.log
Provides information about scan requests for software updates, which tools are scanned for requests, where WSUS is located, and so on.
Scanwrapper
Provides information about prerequisite checks and scanning process initialization for the Microsoft Update Inventory Tool on the Systems Management Server (SMS) 2003 client.
SdmAgent.log
Provides procedural information about verifying and decompressing packages that contain configuration item information for software updates.
ServiceWindowManager.log
Provides procedural information about evaluating a configured Maintenance window.
SmscliUI.log
Provides information about user interaction in the Configuration Manager control Panel, such as starting a software update scan cycle from the Configuration Manager Properties dialog box, opening a program download monitor, and so on.
Smswushandler
Provides information about the scanning process for the Microsoft Update Inventory Tool on SMS 2003 client computers.
StateMessage.log
Provides information about when to create a software update state message and send it to a management point.
UpdatesDeployment.log
Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging displays additional information about interacting with the client user interface.
UpdatesHandler.log
Provides information about software update compliance scans and downloading and installing software updates on the client.
UpdatesStore.log
Provides information about the compliance status of software updates that are evaluated during a compliance scan cycle.
WUAHandler.log
Provides information about when the Windows update agent on a client searches for software updates.
WUSSyncXML.log
Provides information about the synchronization process for the Microsoft Update Inventory Tool. This log is only available on client computers that are configured as a synchronization host for the Microsoft Update Inventory Tool.
Windows Update agent log Files
By default, the Windows Update agent log files can be found in%windir% on the Configuration Manager client computer. WindowsUpdate.log
Provides information about when the Windows Update agent connects to the WSUS server and retrieves software updates for compliance evaluation, and whether the agent components are updated.
out of band management log files
Applies only to Configuration Manager SP1. These log files are in the following location: On the out of band Service Point site System server. On any computer running the out of band management Console from the Configuration Manager console. On a client computer that is running the Configuration manager SP1 client and is managed out of band. The following sections list the log files that are related to out of band management in Configuration Manager SP1 and explain these log files. Out of band Service Point log files
The Configuration Manager SP1 log files that are listed in the following table are located in the folder <configmgrinstallationpath>\logs on the site system server that is used to host the out of band Service point role. AMTSPSetup.log
Shows whether the install out of band service Point succeeded or failed (including the reason for failure).
Amtopmgr.log
Displays the activity of the Out of band service point associated with the management controller discovery, provisioning, and power control commands.
Amtproxymgr.log
Displays the activities of the site server associated with the settings, including: Publishing the configured computers to active Directory Domain Services. Registers the service principal name of the provisioned computer in Active Directory Domain Services. Requesting a WEB server certificate from a certification authority displays the activities that send the instruction file to the out of band Service point, including: Management controller discovery. Set up. Power control commands. Displays activities related to out of band management Site replication.
Out of band management Console log files
The Configuration Manager SP1 log files that are listed in the following table are located on any computer that is running the out of band management Console from the Configuration Manager console <configmgrinstallationpath& The Gt;\adminui\adminuilog folder.
Oobconsole.log
Displays activities related to running the out of band management Console.
Out-of-
band client computer log files
The Configuration Manager SP1 log files that are listed in the following table are located on a workstation computer that is running the Configuration Manager SP1 client and is managed out of band%windir%\system32\ccm\l The OGs folder.
Oobmgmt.log
Displays the out of band management activity that is performed on the workstation computer, including the settings state of the management controller.
This article is from the "Start from the Heart" blog, please be sure to keep this source http://ycrsjxy.blog.51cto.com/618627/203174
SCCM 2007 Logs
