Contributed By: Cliff Hobbs [MVP SMS]
The Advanced Client generates numerous log files. To try to make life a little easier this article contains a list of the Advanced Client log files and a description of their use.

This information has been compiled from Microsoft Knowledge Base Article 867490 "A list of log files that are created in Systems Management Server 2003", by Wally Mead of Microsoft and my fellow MVPs.
 

Log Name	Description
CAS.log	Content Access Service log file, showing when an Advanced Client tries to access Package content or Advertised programs from a DP.  The log shows if the Advanced Client can find the DP and whether or not the Client can access the content on the DP.
CCMExec.log	Log file for the SMS Agent Host.  After the Advanced Client has generated discovery, inventory, status data, etc. this log file shows any communications errors with the MP. (Example: WINHTTP ERROR may appear when a client can’t talk to the MP)
CcmRepair.log	Details of the Client has had to repair itself (typically triggered if the SMS Agent Host service is disabled or isn’t running).
CertificateMaintenance.log	Used for retrieving certificates for the MP, performed periodically to verify that the certificates are correct for the MP.
ClientIDManagerStartup.log	Manages the SMS Unique ID.  Each client maintains a unique ID and if the Client determines that the unique ID is in a cloning scenario or needs to changed, the event is logged here, including what had changed on the Client to trigger the GUID change.
ClientLocation.log	Determines the assigned SMS Site.  This is the first place to look when a client isn’t reporting data.  A Client won’t do anything until it has been assigned to a Primary site.  It could be that auto-discovery isn’t functioning successfully (the AD Schema hasn’t been extended or SMS data hasn’t been published in AD or an SLP can’t be located).
ContentTransferManager.log	Shows the management of the local cache for downloaded and executed programs, and then the aging of that content out of the cache when it is no longer needed.
DataTransferService.log	Shows the actual download of Policies that are retrieved from the MP (including the URL used by the Client to retrieve the data).  The Data Transfer Service is what actually completes the download of those policies.  Check this log for Advanced Client problems transferring or obtaining polices from the MP.
execmgr.log	Running Advertised Programs, similar to the SMSapm32.log from SMS 2.0.  Command lines executed, successful or not, and exit codes will appear in this log.  Check this log for issues with Advertisements.
FileBITS.log	When using Server Message Blocks (SMBs) to download and execute content retrieval from the DP, this file tracks all activity.  This implies that the DP isn’t BITS-enabled (or WebDAV is not enabled), thus using SMBs to download the content.
FileSystemFile.log	The SMS 2003 SP1 version of the File Software Inventory Provider log.
Fsinvprovider.log	File Software Inventory Provider.  Used for Software Inventory.  Look in this log file to observe the Software Inventory scanning process.  Renamed to FileSystemFile.log in SMS 2003 SP1.
InventoryAgent.log	This log is for Discovery, Hardware and Software Inventory processing of the Advanced Client.  There is a single agent on the Advanced Client that is used for all three of these processes.  This log shows properties being discovered in Hardware Inventory as well as paths in Software Inventory being discovered.  Look for the mp_xxxxEndpoint to see what data is being sent to the MP.
LocationServices.log	Use this log if Advanced Clients are downloading policies or looking for DPs to access Package source files.  This log is also used to determine if Clients are finding the default MP.  Messages you want to look for are: Attempting to retrieve default Management Point from AD Attempting to retrieve default Management Point from WINS Attempting to retrieve proxy Management Point Attempts to find a local (resident) management point when roaming When an MP is found, this log will show messages like: Retrieved default Management Point from AD Persisted Management Point in WMI Retrieved Management Point from WINS and then display the computer name of the MP (or its IP address if the MP is retrieved from WINS).  This log is also used to locate DPs.  The Client sends a content location request, location services goes to the MP to request content location from the MP regarding DPs available to the Client.
Mifprovider.log	WMI provider for .MIF files.  Useful for troubleshooting when .mif files are marked as “invalid”.
mtrmgr.log	Software Metering log.  Mtrmgr sees each process that starts on a Client computer and logs any of those processes that fall into a specific Software Metering rule.  If metering is enabled and downloaded to the Client, this log shows processes that match those rules.
PatchInstall.log	Details the status of patch installations on the Client.  This log only gets created wants you’ve authorized and distributed Patches to a Client.
PatchUIMonitor.log	The SMS 2003 Patch Management user interface.
PolicyAgent.log	Tracks Policy requests and downloads, updating on an hourly basis.  If you’ve made a change to the SMS Site and want to verify the Advanced Client is working, look in this log after performing “Initiate Action” for Machine Policy Retrieval & Evaluation Policy from the SMS program in Control Panel (Actions Tab).  This will show whether the new Policy has been successfully retrieved from the MP.  Look for “Requesting Machine Assignments” and then the actual policy IDs (as GUIDs).
PolicyAgentProvider.log	Logs major tasks of the Policy Agent.
PolicyEvaluator.log	Used for evaluation of Policies after they are downloaded from the MP.  Two minutes after downloading the Policy, it gets evaluated by the Policy Evaluator which means tasks will take place. (i.e. Software Inventory, Hardware Inventory, Advertised Programs available for use, etc.)
RemCtrl.log	Used for the installation of the Remote Tools Client Agent.
Scheduler.log	Scheduler will launch scheduled tasks and log the results in this log.
setuppolicyevaluator.log	Shows major tasks of the Policy Evaluator.
SMSCliUi.log	Whenever you start the SMS program from Control Panel, all actions performed are logged here.
SrcUpdateMgr.log	Manages Windows Installer source locations managed by SMS.  Some Windows Installer applications are installed in download and execute mode, where the cache is eventually cleared.  When the application needs to self-heal or perform an “install on demand” option, it no longer has a source location for these files.  SMS can publish the Windows Installer information program properties.  The SMS Advanced Client detects that published information, looking for a DP, for self-healing purposes, and pulls files from the DP.
StatusAgent.log	Used for the creation of Status messages.
SWMTRReportGen.log	Contains a usage data report collected by the Software Metering Agent.

To see other SMS 2003 Troubleshooting FAQs click here.