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 following tables.
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 24.1 Status Message Components and Log Files at the Site Server forWindows Logon Discovery and Installation: 32-Bit Client
| Server components | Log files |
|---|---|
| Windows Networking Logon Discovery | SMS\Logs\NTlgdscm.log |
| Windows Networking Logon Installation | SMS\Logs\NTlginst.log |
| SMS NT Logon Manager | SMS\Logs\NT_logon.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 24.2 Client Log Files for Windows Logon Discovery and Installation: 32-BitClient
| Client components | Log files |
|---|---|
| SMS Boot1 or Boot32Wn process | %Windir%\MS\SMS\Logs\Wn_logon.log |
| Launch32 process | %Windir%\MS\SMS\Logs\Launch32.log |
| SMS Client Service | %Windir%\MS\SMS\Logs\Clisvc.log |
| Core Client Installation process | %Windir%\MS\SMS\Logs\Clicore.log |
| Client Component Installation Manager | %Windir%\MS\SMS\Logs\Ccim32.log |
| Installing optional client agents | %Windir%\MS\SMS\Logs\Ccim32.log %Windir%\MS\SMS\Logs\SMSapm32.log %Windir%\MS\SMS\Logs\<IndividualLogs> For more information about which logs to check, read the flowchart for the client agent in Chapter 25, “Client Feature Flowcharts.” |