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 file. You can then study the log file 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.7 Status Message Component and Log File at the Site Server forNetWare Bindery Client Logon Discovery and Installation:
32-Bit Client
| Server component | Log file |
|---|---|
| NetWare Bindery Logon Installation | SMS\Logs\Nw_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.8 Log Files at the Client for NetWare Bindery Client Logon Discovery andInstallation: 32-Bit Client
| Client components | Log files |
|---|---|
| SMS Boot1 or Boot32NW process | %Windir%\MS\SMS\Logs\Nw_logon.log |
| SMS Client Service | %Windir%\MS\SMS\Logs\Clisvc.log |
| Launch32 process | %Windir%\MS\SMS\Logs\Launch32.log |
| Core Client Installation process | %Windir%\MS\SMS\Logs\Clicore.log |
| Client Component Installation Manager | %Windir%\MS\SMS\Logs\Ccim32.log |