c
c 



   

 
Updated: October 14, 2010

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2,
System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System
Center Configuration Manager 2007 SP2

All the client and site server components in Microsoft System Center Configuration Manager 2007 record
process information in individual log files. You can use the information in the client and site server log files
to help you troubleshoot issues that might occur in your Configuration Manager 2007 hierarchy.

By default, client and server component logging is turned on in Configuration Manager 2007.


c 

The Configuration Manager 2007 client logs are located in one of the following locations:

y On computers that serve as management points, the client logs are located in the
G


GSMS_CCM\Logs folder.

y On all other computers, the client log files are located in the G 
G\System32\CCM\Logs folder
or the G 
G\SysWOW64\CCM\Logs.

The following table lists and describes the client log files.



Log File Name Description

CAS.log 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 Windows Management Instrumentation (WMI) provider for

FileSystemFile.log in all SMS 2003 Service software inventory and file collection.
Packs)

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.

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

ë  ë  c 

Most Configuration Manager 2007 site server log files are located in the <D
 Î\LOGS folder.
Because Configuration Manager 2007 relies heavily on 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

Adsgdis.log Records Active Directory Security Group Discovery actions.
Adsysgrp.log Records Active Directory System Group Discovery actions.

Adsysdis.log Records Active Directory System Discovery actions.

Adusrdis.log Records Active Directory User Discovery actions.

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.

Fspmgr.log Records activities of the fallback status point site system role.

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.

Netdisc.log Records Network Discovery actions.

Ntsvrdis.log Records NT 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.

Smsfspsetup.log Records messages generated by the installation of a fallback status point.

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.

The Admin UI log files are located in <D

 Î\AdminUI\. The following table lists and describes
the Admin UI log files.



Log File Name Description

RepairWizard.log Records errors, warnings, and information about the process of running the Repair
 Wizard.

ResourceExplorer.log Records errors, warnings, and information about running the Resource Explorer.

SMSAdminUI.log Records the local Configuration Manager 2007 console tasks when you connect to
Configuration Manager 2007 sites.


 

c 

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. 

ë

c 

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



Log File Name Description

fspmsi.log Records messages generated by the installation of a fallback status point. 

fspisapi.log Records activities of the fallback status point site system role. 

     
 
c 

If mobile device management is enabled in the site hierarchy, mobile device management point log files are
generally stored in the ·  
D
 \Logs folder on the mobile device management point
computer. The following table lists and describes the mobile device management point log files.

     
 

c




Log File Name Description

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 Windows Installer 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.

     
 

c


For the locations of log files on managed mobile devices and on computers that are used to deploy the
mobile device client, see -
  
   
 
 


. The
following table lists and describes the mobile device management client log files.



Log File Name Description

DmCertEnroll.log Records certificate enrollment data on mobile device clients.

DMCertResp.htm (in Records HTML response from the certificate server when the mobile device
\Temp) 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.

 
ë
   
c 

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.

Log file location:

·  
D
  D


Dism.log Provides information about drivers installed during operating system

deployment.

Configuration Manager 2007 SP2 installs drivers by using the Deployment

Image Servicing and Management (DISM) tool in Windows Automated
Installation Kit (AIK) 2.0.

Log file location:

G G



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 Pre-Boot Execution Environment (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 jj   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.

PkgMgr.log Provides information about drivers installed during operating system

deployment.

Configuration Manager 2007 with SP1 installs drivers by using the Package
Manager tool.

Log file location:

G G
 


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 Provide information about Windows Sysprep and setup logs.

Setupapi.log

Setuperr.log

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:

y If task sequence completes when running in the full operating system

with a Configuration Manager 2007 client installed on the computer:
· D




y If task sequence completes when running in the full operating system

with no Configuration Manager 2007 client installed on the computer:
G G


y If task sequence completes when running in Windows PE: ·


 

 

 º 
<CCM Install DirÎ is %Windir%\System32\Ccm\Logs for most
Configuration Manager 2007 clients and is <Configuration Manager 2007
installation driveÎ\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.

º  j

   

c 

By default, client log files related to Network Access Protection are found in G 
GCCM\Logs. For
client computers that are also management points, the log files are found in
G


GSMS_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 about 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.

The System Health Validator point log files are located in %systemdrive%\SMSSHV\SMS_SHV\Logs, and
they are listed and described in the following table.



Log File Name Description

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:

HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL
Setup information for the System Health Validator point can be found in a setup log file, described in the
following table, on the computer running the Network Policy Server.



Log File Name Description

·  
D
 \Logs\SMSSHVSetup.log Records the success or failure (with failure reason)
of installing the System Health Validator point.



   

 
c 

By default, the Configuration Manager 2007 client computer log files are found in
%Windir%\System32\CCM\Logs or in %Windir%\SysWOW64\CCM\Logs. For client computers that are also
management points, the client log files are located in the SMS_CCM\Logs folder. The following table lists
and describes these log files.



Log File Name Description

ciagent.log Provides information about downloading, storing, and accessing assigned configuration
baselines.

dcmagent.log Provides high-level information about the evaluation of assigned configuration

baselines and desired configuration management processes.

discovery.log Provides detailed information about the Service Modeling Language (SML) processes.

sdmagent.log Provides information about downloading, storing, and accessing configuration item
content.

sdmdiscagent.log Provides high-level information about the evaluation process for the objects and
settings configured in the referenced configuration items.

 
cjºc 

The Configuration Manager 2007 site server log files related to Wake On LAN are located in the folder
·  
D
 \Logs on the site server. There are no client-side log files for Wake On LAN.
The following table lists and describes the Wake On LAN log files.



Log File Description

Name
Wolmgr.log Contains information about wake-up procedures such as when to wake up advertisements
 or deployments that are 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 wake-up packets retried.

ë  

c 

By default, the Configuration Manager 2007 site system log files are found in
<  
D
 \Logs. The following table lists and describes the software updates site system
log files.



Log File Name Description

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.

º 
On 64-bit operating systems and on 32-bit operating systems with no
Configuration Manager 2007 installed, PatchDownloader.log is created in the
server logs directory. On 32-bit operating systems, if the Configuration Manager
2007 client is installed, PatchDownloader.log is created in the client logs
directory.

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,

 




 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.

ëëë  c 

By default, the log files for WSUS running on the software update point site system role are found in
%ProgramFiles%\Update Services\LogFiles. The following table lists and describes the WSUS server log files.



Log File Name Description

Change.log Provides information about the WSUS server database information that has
changed.

SoftwareDistribution.log Provides information about the software updates that are synchronized from the
configured update source to the WSUS server database.

ë 

 c 

By default, the Configuration Manager 2007 client computer log files are found in % 
%\CCM\Logs.
For client computers that are also management points, the log files are found in
%


%\SMS_CCM\Logs. The following table lists and describes the software updates client
computer log files.



Log File Name Description

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

   

   
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.



 j
c  
By default, the Windows Update Agent log file is found on the Configuration Manager Client computer in
% 
%. The following table provides the log file name and description.



Log File Name Description

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.

!

 
c 

Applies only to Configuration Manager 2007 SP1 and later.

These log files are found in the following locations:

y On the out of band service point site system server.

y On any computer that runs the out of band management console from the Configuration Manager
console.

y On computers that are running the client for Configuration Manager 2007 SP1 or later and that are
managed out of band.

The following sections lists and describes the log files related to out of band management in Configuration
Manager 2007 SP1 and later.

!
ë   
c 


The out of band service point log files listed in the following table are located in the folder
·  
D
 \Logs on the site system server selected to host the out of band service point
role.



Log File Name More Information

AMTSPSetup.log Shows the success or failure (with failure reason) of installing the out of band service
point.
Amtopmgr.log Shows the activities of the out of band service point relating to discovery of
management controllers, provisioning, and power control commands.

Amtproxymgr.log Shows the activities of the site server relating to provisioning, which include the
following:

y Publishing provisioned computers to Active Directory Domain Services.

y Registering the service principal name of provisioned computers in Active

Directory Domain Services.

y Requesting the Web server certificate from the issuing certification authority.

Shows the activities of sending instruction files to the out of band service point, which
include the following:

y Discovery of management controllers.

y Provisioning.

y Power control commands.

Shows the activities related to out of band management site replication.

!

 


 c 


The out of band management console log file listed in the following table is located in the folder
·  
D
 \AdminUI\AdminUILog on any computer that runs the out of band
management console from the Configuration Manager console.



Log File Name More Information

Oobconsole.log Shows activities related to running the out of band management console.

!

 

 c 


The out of band management client log file listed in the following table is located in the folder
G 
G\System32\CCM\Logs on workstation computers that are running the client for Configuration
Manager 2007 SP1 or later and that are managed out of band.



Log File More Information

Name
Oobmgmt.log Shows out of band management activities performed on workstation computers, including
the provisioning state of the management controller.

 
 
c 

Applies only to Configuration Manager 2007 R3.

The log files listed in the following table are located in the folder G 
G^ë
 "^^c
on 32-
bit workstation computers and in the folder G 
G^ë
#$^^c
on 64-bit workstation
computers that have the Power Management Client Agent enabled.



Log File Name More Information

pwrmgmt.log Shows power management activities performed on the client computer that include
monitoring and enforcement activities performed by the Power Management Client
Agent. On computers that are running Windows XP, this log also records power settings
to the computer.

PwrProvider.log Shows 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. On computers that are running Windows Vista, Windows Server 2008,
Windows 7, and Windows Server 2008 R2, the provider is also responsible for applying
power plan settings to the computer.

ë j

%



-