SMS 2003 Client log files helps more in troubleshooting the issues

Below are the basic log files (more understandable way) that are helpful in troubleshooting the client issues if there are any application instllation failure/inventory and other issues.This information has been compiled from Microsoft Knowledge Base Article 867490

A list of windows update error codes can be found here.

CAS.log ."CAS" means "Content Access Service". In this Log you will find the local Package Cache status. useful in Downloaded package issues and "cache out of space" errors. Make sure package content access is completed.

  • ccmexec.log ."CCMEXEC" means "Client Configuration Manager Executive" and it is nothing else that the SMS Service itself (ccmxec.exe) Log. One of the first logs where you should look when you are troubleshooting client issues.This service is reposible to track all the activities in the client. You can find here for example communication Problems from the client to the MP. Make sure that there are no errors, such as WinHTTP errors, listed.Very important Log!
  • ccmperf.log .  It contains information of the CCM Performance Counter. Not really a log that you will look at very often.
  • CertificateMaintenance.log. In this Log you will see if the Client got the right Certificate from the MP also tells if client cannot communicate with a management point or with Active Directory.
  • ClientIDManagerStartup.log. Each SMS Client has a unique ID, in case that the Client was deployed over a Image or Clone or you have a SMS ID Problem, the corresponding information will be logged here.
  • ClientLocation.log. Here you should look at when the Client is not sending informations to the SMS Server. You will also find on which SMS Site Server the Client is reporting to. Important Log
  • ContentTransferManager.log. In this Log you will find download activity of Packages to the local Cache like Package version issues or packages that are not available..
  • DataTransferService.log. Here you will see if there are any problems with the download of Policies from the MP and Records all BITS communication for policy or package access .To detemine if the client uses BITS or SMB, BITS downloads have a URL that starts with http://<distributionpoint> and SMB downloads with \\<distributionpoint>. Usually the Advanced Client will only use BITS to download software if the advertisement has been set to download and execute. If the advertisement has been set to run the program from the network, it always uses SMB.
  • EventLogForwarder.log. All entries done into the eventvwr are logged in this Log.
  • execmgr.log. Here you can see the Status of the Advertisements, how is the advertisement started and which are the results of it. It also helps yu in troubleshooting Package errors or packages that are unavailable. Make sure that the program command line has run successfully and that status is generated.
  • FileBITS.log. You will find here the Status of the downloads as also any reciving activity.
  • InventoryAgent.log. Here you will find any information related to the Hardware and Software Inventory.
  • LocationServices.log. This Log will show you how and which MP and DP are discovered.Very important Log!
  • mtrmgr.log. Software Metering Log. The Metering Agent monitors each Process that is started on the Client and compares it with the Metering Rules to very if one of the process needs to be tracked.
  • PatchInstall.log. Here you will see which patch was installed and with which parameter, when a Update Scan was done and which updates are missing. Very important Log!
  • PatchUIMonitor.log. This is the User Interface log of the Security Updates.
  • PolicyAgent.log. Any Policy request and Policy Download is logged here. Very important Log!
  • PolicyAgentProvider.log. Here you will see the most important tasks of the Policy Agent.
  • PolicyEvaluator.log. Each Policy is verified after ~2 Minutes after the download of the Policies is done, this verification is logged here. Important Log
  • RemCtrl.log . In this log you will find the Remote Tools agent installation.
  • ScanWrapper.LOG . This log corresponds to the "ITMU" Scanner. Every security update scan and installation is logged here. You can also see which wsusscan.cab is used and from where as also how and which parameters was the Scan started.
  • Scheduler.log . Here you can see what the SMS Scheduler has started and the result of it.
  • smscliui.log . Log for the SMS Client User Interface.
  • smscstat.log . Software Update Client Status Log.
  • SmsWusHandler.log . Another log related to ITMU, here you will find any Update Scan done on the PC.
  • SrcUpdateMgr.log . Every update of the Windows Installer Source Location Agent of SMS is logged here. Mor Infos about the Windows Installer Source Location Agent can be found here.
  • StatusAgent.log . Any new Status Message is logged here.
  • SWMTRReportGen.log . On aregular Basis the Metering Data is collected in a xml file and send to the SMS Server, in this log you will this process.
  • UpdateScan.log . It's the log for the "SMS Extended Security Update Inventory Tool". Some Updates that are not supported by ITMU and therefore this extended scan tool is required. More information about it can be found here.

Leave a Reply