Site Configuration Change

The Site Configuration Change flowchart illustrates the processing that occurs when an SMS administrator creates or changes a site system. When a site system gets created, Site Component Manager installs and starts the service and thread components that are necessary for that particular site system to perform its role. For more information about the server components that run on each type of site system, see Table 2.11, “Where SMS Service Components Are Installed” and Table 2.12 “Sites Where SMS Thread Components Run.”

The activity described in this flowchart takes place on both primary and secondary site servers and on any site systems that each particular site server administers.

Tracing Information

You can trace the activity described in this flowchart by studying the status messages for the server component listed in the table below. Or, you can enable the log file for this component. You can then study the log file and status messages associated with this component 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 viewing status messages and enabling logging, see “Status Messages Versus Logging” in Chapter 16, “Introducing the SMS 2.0 Flowcharts.”

Table 18.1 Status Message Component and Log File for Site Component Manager:Site Configuration Change

Troubleshooting Tips

If SMS service and thread components do not appear to be installed and started on a new CAP server:

• Review the status messages and log files for Site Component Manager.
• Verify that the SMS service account has Domain Admins privileges on the CAP server. Also verify that the SMSSvc_XXX_0000 account password or rights have not been changed. This is an account whose passwords and rights should never be changed.
• Verify connectivity between the site server and the newly assigned CAP.