After installing the primary site server, modifications may be necessary. Changes made to the site server are applied to the database through the SMS services and the SQL Server account.
After a primary site has been installed, the SMS setup program is added to the Systems Management Server program group. Whenever SMS setup is run, it examines the local computer to determine whether SMS components are installed, and ascertains the computer's SMS role. On a primary site server, SMS setup run from the SMS CD-ROM allows you to upgrade, remove, modify, or reset SMS. SMS setup run from the SMS installation directory does not allow the `Upgrade an existing SMS installation' option (Figure 2-12).
Figure 2-12. The SMS setup program run from the SMS CD-ROM.
This option is used only for upgrades to an existing SMS installation. The upgrade process first stops all SMS services, removes registrations for component object model (COM) controls, updates the SMS databases, and then begins the upgrade process. The upgrade reinstalls the SMS files to the site server, registers SMS COM controls, restarts the SMS services, and re-creates the SMS program group. The `upgrade' option is used for both version updates and service pack updates. In the case of a service pack update, the `upgrade' option is the only option listed in the Setup Options window. An upgrade to an existing site server can be used in case of SMS file or registry key corruption. File or registry corruption are commonly caused by a malfunctioning disc, a memory failure, or a computer virus.
Use the `Remove SMS' option to remove a primary site and the site systems managed by this site server. Removing SMS from a site deletes all SMS services, files, and SMS registry settings but does not remove the following:
When this option is selected, SMS setup displays various setup windows that can be used to modify the following items:
After any of the items in the bulleted list are changed, SMS setup must reset the site. If no changes are made, SMS setup displays a message box asking if you wish to reset the site. When a reset is requested, SMS setup shuts down all SMS services and then restarts them. Restarting applies any changes that have been made to the site. A reset initiated without any modification to site settings can be used if SMS services appear to be stopped.
Because SMS services run in the background, configuration changes are not immediate. The SMS Provider and two SMS thread components—the Hierarchy Manager and the Site Control Manager—play significant roles in installing and changing the configuration of SMS sites. These components communicate with each other through site control files.
Methods of Reconfiguration
The SMS Administrator console and SMS services can request that changes be made to the site database. These changes to the SMS site configuration are not immediate, because SMS services operate as background processes, checking only periodically for work to perform. The configuration is not changed until the appropriate SMS services operate on the proposal and carry out the request. For this reason, SMS maintains both a current and proposed set of site server configuration parameters in the site control table and the site control files. There are three types of site control files: the master site control file, SITECTRL.CT0; the proposed changes site control file, *.CT1; and the status site control file of completed changes, *.CT2. These files and change history information are stored in sub-directories below \<sms root directory>\ INBOXES\SITECTRL.BOX.
The SMS Administrator console and SMS services initiate change differently. Through the SMS Administrator console, changes are made to the site configuration. As a result, the SMS Provider creates a proposed change in the SMS database site control table. The Hierarchy Manager reads the proposed change and creates a *.CT1 file. The *.CT1 file is then delivered to the Site Control Manager. The Site Control Manager completes the site configuration changes, updates the SITECTRL.CT0, and creates a *.CT2 file. The Hierarchy Manager receives the *.CT2 file and updates the database to record the completed changes (Figure 2-13).
Figure 2-13. The site configuration change process.
SMS services update SITECTRL.CT0 directly and create the *.CT1 file, which is given to the Site Control Manager to initiate the change. From this point onward, the process is identical to that which takes place when site configuration changes are initiated through the SMS Administrator console.
See the Site Control Manager diagram in Appendix D of the SMS Administrator's Guide.