You can trace the activity described in this flowchart by studying the status messages and optional log files for the server components listed in the following table.
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 19.1 Status Message Components and Log Files at Primary Site Server forSecondary Site Installation Initiated from Parent
| Server components | Log files |
|---|---|
| SMS Provider | SMS\Logs\SMSprov.log |
| Hierarchy Manager | SMS\Logs\Hman.log |
| Scheduler | SMS\Logs\Sched.log |
| Sender | SMS\Logs\Sender.log |
| Despooler | SMS\Logs\Despool.log |
| Replication Manager | SMS\Logs\Replmgr.log |
Table 19.2 Status Message Components and Log Files at Secondary Site Server forSecondary Site Installation Initiated from Parent
| Server components | Log files |
|---|---|
| SMS_Bootstrap Service | <InstallationDrive>\SMS_bootstrap.log |
| Setup | <SystemDrive>\SMSsetup.log |
| Site Component Manager | SMS\Logs\Sitecomp.log |
| Hierarchy Manager | SMS\Logs\Hman.log |
| Replication Manager | SMS\Logs\Replmgr.log |
| Scheduler | SMS\Logs\Sched.log |
| Sender | SMS\Logs\Sender.log |