You can trace the activity described in this flowchart by studying the status messages and optional log files for the server components and the automatically-generated log files for client agents listed in the tables below.
For server components, you can view status messages, or you can enable the log files. You can then study the log files and status messages associated with these components to trace the activity that is actually occurring on your SMS system and compare it to the activity described in the flowchart. For more information about how to access status messages for a specific component and how to enable logging, see “Status Messages Versus Logging” in Chapter 16, “Introducing the SMS 2.0 Flowcharts”.
Table 25.1 Status Message Components and Log Files on Site Systems for HardwareInventory: 32-Bit Client
| Server components | Log files |
|---|---|
| Inbox Manager | SMS\Logs\Inboxmgr.log |
| Inbox Manager Assistant (at the CAP) | SMS\Logs\Inboxast.log |
| Inventory Processor | SMS\Logs\Invproc.log |
| Inventory Data Loader | SMS\Logs\Dataldr.log |
| Replication Manager | SMS\Logs\Replmgr.log |
SMS automatically generates log files for processes that occur on SMS clients. You can examine the client log files to identify the problems occurring on clients.
Table 25.2 Client Tracing for Hardware Inventory: 32-Bit Client
| Client agents | Log files |
|---|---|
| Hardware Inventory Agent | %Windir%\MS\SMS\Logs\Hinv32.log |
| Client Component Installation Manager | %Windir%\MS\SMS\Logs\Ccim32.log |
| Client Service (CliSvcl) | %Windir%\MS\SMS\Logs\Clisvc.log |
| Copy Queue | %Windir%\MS\SMS\Logs\Cqmgr32.log |