Microsoft Systems Management Server
Setup Help Contents

System Requirements for the Site Server

Installing a Primary Site

Installing the Central Site

Setting Up Accounts for SMS

Preparing the Site Server

Preparing the SQL Server

Preparing the Site Server Domain

Preparing Clients for SMS

Preparing a Site for Macintosh Support

Maintaining a Site

Upgrading SMS Components

Adding Components to a Site

Resetting a Site

Shutting Down a Site

Changing the SQL Login ID, Site Database, and SQL Server Settings

Changing the SMS Service Account

Deinstalling a Site

Deinstalling a Primary Site

Deinstalling a Secondary Site

Deinstalling an Orphaned Secondary Site

Installing the SMS Administrator on a Windows NT Computer

Installing Network Monitor on a Windows NT Computer

Installing Network Monitor on a Windows for Workgroups Computer

Synchronizing Time and Running SMS Across Time Zones

Glossary


Microsoft Systems Management Server Setup

Welcome to Microsoft Systems Management Server (SMS)!

The SMS Setup program enables you to install the site server for a primary site. It also enables you to maintain or deinstall an existing site.

Installing a Primary Site.

Maintaining an Existing Site.

Deinstalling an Existing Site.

Installing the SMS Administrator and other administration utilities.


Installing a Primary Site

To install the Microsoft Systems Management Server (SMS) system, you install and configure sites. The SMS Setup program enables you to install a primary site.

Before you install SMS, you should plan how you want to structure the sites in your SMS system. For information about these concepts and about planning your overall system, see the SMS Administrator's Guide. The guide also provides the general steps for installing a complete SMS system--that is, a heirarchy of sites.

After you have planned your site hierarchy, you need to prepare the following computers for installing SMS:

The site server.

The SQL Server.

The site server domain (logon servers).

Once you've created individual sites, you can assemble them into a hierarchy of sites that form a single SMS system. The SMS Administrator's Guide explains how to set up a hierarchy of sites and shows how to configure a site's inventory collection, its domains, its SMS services, and its communication with other sites (Senders, Outboxes, and Addresses).

Note  If you install the Network Monitor, you must install the Network Monitor Agent on the computer to complete the setup of Network Monitor.

Installing the Network Monitor Agent on a Windows NT Computer


Preparing the Site Server

Each site in the SMS system must have a site server. A site server contains the SMS components needed to monitor and manage the site and its domains.

To prepare the site server before installing a site

1.	Make sure that the computer used for the site server meets the system requirements for a site server.

2.	Create an SMS Service Account for use in the site server domain.

After you have created the SMS Service Account, you specify it when you run the SMS Setup program. The SMS Service Account is also used to complete the setup of SMS at the site. After you've completed the setup of the site, the SMS Service Account is used by the SMS services.

3.	Set the Application Log of the Windows NT event log to overwrite events as needed (recommended).

From the Administrative Tools program group, double-click Event Viewer. From the Log menu, choose Log Settings. In the Change Settings For Log box, select Application. Under Event Log Wrapping, select the Overwrite Events As Needed option button. Click OK.

By making this setting, you will ensure that the most recent SMS events will continue to be logged to the event log even when the event log is full. You may also want to increase the maximum size of the Application Log.


System Requirements for the Site Server

The site server is a computer running Microsoft® Windows NT™ Server that contains the services and components needed to manage the SMS system.

The site server has the following requirements:

Windows NT Server version 3.5.

Primary domain controller or backup domain controller.

An 80486 66 megahertz or higher microprocessor, a Pentium™ microprocessor, or a RISC-based microprocessor supported by Windows NT Server version 3.5 (such as MIPS® or DEC™ Alpha).

Twenty megabytes (MB) of RAM, minimum. The recommended RAM requirement is 28 MB for a primary site server that also contains the Microsoft® SQL Server. Twenty MB of RAM is recommended for the site server at a secondary site.

A hard disk that is formatted as NTFS and that has at least 100 MB of free hard disk space on the partition that will contain the SMS system files. Five hundred MB of free space is recommended.

More disk space may be required for compressing and decompressing packages for jobs. For information about compression and decompression, see the SMS Administrator's Guide.

Access to any CD-ROM drive (primary site installation only).


Preparing the SQL Server

When you install a primary site, you must have a Microsoft SQL Server on which to install the SMS site database. You can install the site database on a SQL Server that is installed on the site server or on another server with Microsoft SQL Server installed. To reduce the load on the site server, you can install the site database on another server running Microsoft SQL Server.

A primary site's database contains system and inventory information for itself and the sites below it. The Central Site's database contains the system-wide configuration and inventory information for all sites in the SMS system.

Note that SMS will use the Character Set and Sort Order set on the SQL Server. These settings will affect how SMS queries and sorts data. For more information about how Character Sets and Sort Orders are used by SQL Server, see the Microsoft SQL Server documentation.

To set up the SQL Server for use as a site database

1.	Make sure you have an SMS SQL login id to use when you install the site database (you will need to specify this login ID when you run the SMS Setup program).

This is also the login ID you use to log in to the site database when you start the SMS Administrator. For more information about SQL Server security, see the SQL Server documentation.

2.	Create the site database device and transaction log device.

The site database and the transaction log must be on separate devices. You must have a site database device and a transaction log device.

If you choose to install the site database on the SQL Server on the site server, the SMS Setup program can create the devices for the site database and its transaction log as well as create a database for the site database. To create all devices and databases through the SMS Setup program, the SMS SQL login ID specified in the SMS Setup program must have system administrator (sa) permissions. Otherwise, you can manually create the devices as you would using a SQL Server on another server.

If you choose to install the site database on a SQL Server on another server (not the site server), you must manually create the device for the site database and the device for the site database's transaction log. The SMS SQL login ID specified in the SMS Setup program must have Create Database, Dump Database, and Dump Transaction permissions on the Master database. This enables the SMS Setup program to create and maintain the site database.

Caution  If you use an existing device for the site database or the transaction log, the SMS Setup program will delete all objects in the site database and transaction log devices. The SMS Setup program uses the entire site database device for the site database and the entire transaction log device for the transaction log.

3.	Make sure that the temporary database (tempdb) of the SQL server is large enough for the number of computers you want to include in the SMS inventory at that site (this includes all computers at the site and its subsites).

If you plan to store inventory for more than 2000 computers in the site database, the tempdb must be 5 megabytes (MB) or greater. Ten MB is recommended. A larger tempdb improves the performance of queries that contain sorts.

Note that the default size for the tempdb is 2 MB and that the tempdb is stored on the master device. You may want to create new device for the tempdb instead of expanding its size in the master device.

4.	Make sure that the SQL Server has a maximum user connection setting that has at least 5 connections for use by SMS. Ten connections are recommended.

If the SQL Server is used for the site database only, you should have a setting of 5 or greater. If you have other databases, you should add 5 or more to the existing number of connections.

If you are using SMS tools such as the SMS Security Manager and the SMS Database Manager or if you have installed the SMS Administrator on another Windows NT computer, you may need additional user connections so that those applications can access the site database.

5.	Tune the memory option in the system configuration for the SQL Server.

You can increase database performance for SMS by increasing the memory option in the system configuration for the SQL Server. The optimum setting for the memory option depends on how much RAM is installed on the SQL Server computer and on what other services or applications are running on that computer. Note that increasing the memory option will have an effect on other Windows NT processes on the SQL Server. Before you change the memory option, you should read the Microsoft SQL Server documentation.

For performance and tuning information for SQL Server, see the Microsoft SQL Server documentation.

6.	Tune the open objects option in the system configuration for the SQL Server.

A open objects setting of 5000 or greater is recommended.

7.	If you plan to install the site database on another server (instead of the site server), make sure the SMS Service Account has access to the SQL Server.

You should be able to use the SMS Service Account to make a network connection to SQL Server.

8.	Make sure that the SQL Server has been set with the current time.

The SMS Scheduler uses the SQL Server time to determine when to perform jobs.


Preparing the Site Server Domain

At a primary site, the site server is a server (with a role of Controller or Server) in a Windows NT domain. The domain containing the site server is called the site server domain.

You can choose to automatically add the other servers in the site server domain to the site's computer inventory. (The site server is always added to the computer inventory.) Or you can add them manually.

Once a server has been added, it is considered an SMS logon server. An SMS logon server supports configuration, inventory, package installation, and network applications on the SMS clients in its domain. Note that the site server is automatically added as a logon server.

To prepare the site server domain, make sure you have an SMS Service Account in the domain so that the SMS services can manage the domain's logon servers.


Deinstalling a Site

There are two main steps to deinstalling a site:

1.	Remove the site from the site hierarchy.

2.	Remove the SMS system from all computers in the site.

You deinstall primary and secondary sites using different steps.

Deinstalling a Primary Site

Deinstalling a Secondary Site.

Deinstalling an Orphaned Secondary Site.


Deinstalling an Orphaned Secondary Site

If you have removed a primary site and orphaned one or more secondary sites directly beneath it in the site hierarchy, you can use the SMS Setup program to deinstall these secondary sites. You should only use SMS Setup to deinstall a secondary site if it has been orphaned (its parent site has been deinstalled). If you delete a secondary site that still has an active parent site, the parent site will continue trying to manage the secondary site with system jobs. You should remove a secondary site using the SMS Administrator at the secondary site's parent site.

Note  Normally, you remove a secondary site using the SMS Administrator at the secondary site's parent site. You should only use SMS Setup to deinstall primary sites or orphaned secondary sites.

To remove an orphaned secondary site

1.	At the site server for the orphaned secondary site, log on using a user account with administrator privilege on the computer itself (the user account is a member of the Administrators group) and in the site server's domain (member of Domain Admins group).

2.	At the site server for the site, start the SMS Setup program from the SMS CD-ROM or from the Systems Management Server program group.

The Systems Management Server Setup dialog box appears.

3.	Click Continue.

Setup checks the disk drives and registry of the site server for an existing version of SMS.

The Existing Installation dialog box appears.

4.	Click Continue.

The Installation Options dialog box appears.

5.	Click Deinstall.

6.	Click OK.

7.	Click Yes when prompted for confirmation to deinstall the site.

The SMS Deinstallation dialog box appears.

When the deinstallation is complete, the Success dialog box appears.


Deinstalling a Secondary Site

You remove a secondary site using the SMS Administrator at the secondary site's parent site. For more information about removing a secondary site, see the SMS Help or the SMS Administrator's Guide.

If you have orphaned a secondary site by deinstalling its parent site, you can use the SMS Setup program to deinstall an orphaned secondary site.

Deinstalling an Orphaned Secondary Site.


Maintaining a Site

The SMS Setup program enables you to maintain an existing site:

Upgrading a Site

Changing the SMS Service Account for a Site

Changing the SMS Database Settings for a Primary Site

Resetting a Site

Shutting Down a Site

Adding Components to a Site


Site Operations Dialog Box

Enables you to maintain a existing site:

Upgrade Site

Reset Site

Shutdown Site

Service Account

SMS Database


Upgrade Site (Site Operations)

The Upgrade Site button upgrades all SMS components (all SMS services and files) on the site server and on all logon servers in all domains that are part of the site. The Setup program uses the components on the SMS CD-ROM to update the site's components.

When you perform an upgrade, the Site Configuration Manager replaces all SMS components at the site with components from the specified path. If the site has a secondary site directly beneath it, the Site Hierarchy Manager will create a system job to upgrade the components at those secondary sites (this means that you must upgrade a secondary site's direct parent site in order to upgrade that secondary site).

When you upgrade a site, the clients in the site and any secondary sites directly beneath it are upgraded to the new components when a user at the client runs the SMSLS batch file or the Client Setup program.


Reset Site (Site Operations)

The Reset Site button performs an SMS system reset on the site server.

An SMS system reset performs the following actions: SMS Setup stops all SMS services on the site server, removes the Site Configuration Manager, reinstalls and restarts the Site Configuration Manager, forces two new site configuration files to be written (one from the current site properties and one from the proposed site properties), evaluates the new configurations with the previous site configuration file, selects the best configuration, updates the site's configuration using the selected site configuration file, and restarts all the SMS services on the site server.


Shutdown Site (Site Operations)

The Shutdown Site button stops all SMS services on the site server and all logon servers in all domains that are part of the site.

You can restart the SMS services using the Reset Site button or the SMS Service Manager.


Service Account (Site Operations)

The Service Account button opens the Service Account dialog box, which enables you to change the SMS Service Account for the site.

For a primary or secondary site, you can use the SMS Setup program to change the SMS Service Account. (Note that you should use the Account dialog box to change the SMS Service Account for a secondary site.) The SMS Setup program can only change the SMS Service Account for the current site (the SMS Setup program runs on the site server). However, the SMS Setup program provides account verification (the SMS Setup program checks that the account exists and has the proper permissions). When you change the SMS Service Account in the Account dialog box, no account verification is performed.

Changing the SMS Service Account affects only SMS services--not the actual user account. The SMS Setup program only configures SMS services so that they will use the specified account and password. To change, modify, or delete a user account or a user account's password in the site server domain and all other domains in the site, you must use the User Manager for Domains tool (for Windows NT domains), the LAN Manager Administrator's Screen (for LAN Manager domains), or the NetWare SYSCON utility (for NetWare domains).

Caution  Although you can simply change the password of the SMS Service Account, it is highly recommended that you create a new SMS Service Account and switch from the old account to the new one.

If the site server is rebooted while the Site Configuration Manager is attempting to change the SMS Service Account for the SMS services and you have only changed the password, the Site Configuration Manager may not be able to restart depending on its progress before the site server was rebooted. If you only changed the password for the SMS Service Account, the Site Configuration Manager cannot use the old account to start itself and complete the SMS Service Account change. If you use a different account, the Site Configuration Manager can use the old SMS Service Account to successfully finish the SMS Service Account change.


SMS Database (Site Operations)

The SMS Database button opens the Active SQL Server And Database dialog box, which enables you to change the SMS SQL login ID, SQL Server name, and database name used for the site database of a primary site.

After you've installed a primary site, you can use the SMS Setup program to change the SMS SQL login ID used by the SMS services, switch the site to another site database, or switch to another SQL Server.

Caution  You should change the name of the site database or the SQL Server only if you have restored the site database for the site to a database with another name or if you have restored the site database to another SQL Server.

Changing the SMS SQL login ID affects only SMS services--not the actual SQL login account. The SMS Setup program only sets SMS services so that they will use the specified account and password. To change, modify, or delete a login account or a login account's password on the SQL Server, you must use the SQL Administrator (or an ISQL command).


Installation Options Dialog Box

Enables you to install a primary site, install the SMS Administrator and other administration utilities, add components to a primary site (and the secondary site directly beneath it), deinstall a primary site, or maintain an existing site.

Install Primary Site

Install Admin Tools

Deinstall

Add Components

Operations


Install Primary Site (Installation Options)

Install Primary Site

The Install Primary Site button installs the SMS system on a computer running Windows NT Server version 3.5. This computer serves as the site server for the primary site.

Installing a Primary Site


Install Admin Tools (Installation Options)

Install Admin Tools

The Install Admin Tools button installs the SMS Administrator (and other administration utilities) on a computer running Windows NT version 3.5.

When you install a primary site, the SMS Setup program automatically installs the SMS Administrator and other utilities on the site server and creates the Systems Management Server program group for the SMS Administrator. You can also install the SMS Administrator and administration utilities on other computers running Windows NT version 3.5.

Note that this button is not available on a site server. To install the SMS Administrator and utilites (such as Network Monitor) on a site server, you must use the Add Component button.


Deinstall (Installation Options)

Deinstall

The Deinstall button removes all SMS components (all SMS services, files, registry entries, program groups, and optionally the site database and its devices) from the site server and from all logon servers in all domains that are part of the site. However, the Setup program does not remove the SMS.INI file from any of the servers. The Setup program also does not remove SMS components from clients that have been added to the SMS system.

On a Windows NT computer where the SMS Administrator or Network Monitor were installed using the Install Admin Tools option in SMS Setup, the Deinstall button removes the SMS administrative tools that were installed on the computer.


Add Component (Installation Options)

Add Component

On a site server, the Add Component button enables you to add new components or update existing components in the site. On a Windows NT computer where the SMS Administrator or Network Monitor were installed using the Install Admin Tools option in SMS Setup, the Add Component button adds new SMS tools or updates the SMS tools that were installed on the computer.

On a site server, the SMS Setup program enables you to install the following items:

Server and client components for all supported platforms: x86 (Intel), Alpha, MIPS, and Macintosh (client components only).

Network Monitor for the x86, Alpha, and MIPS processors.

The SCRIPTS option, which contains the PDFs and installation scripts provided with SMS.

SMS Administrator and other administration utilities.

The online version of the SMS Administrator's Guide can also be installed.

By default, the site server has the following components installed:

Client and server components for the site server's processor type.

Intel client components.

The SMS Administrator and administration utilities for site server's processor type.

Network Monitor for the site server's processor type.

The SCRIPTS option.

When you add new components to a primary site, the Site Configuration Manager installs the new SMS components at the site. If the site has a secondary site directly beneath it and you choose to upgrade the secondary site, the Site Hierarchy Manager will create a system job to install the new components and upgrade the existing components at that secondary site (this means that you must add a new component to a secondary site's direct parent site in order to add it to that secondary site). Note that this system job upgrades all components at the secondary site.

On a Windows NT computer where the SMS Administrator was installed using the Install Admin Tools option in SMS Setup, the SMS Setup program enables you to install the following items:

Network Monitor for your computer's processor type

The SCRIPTS option, which contains the PDFs and installation scripts provided with SMS.

SMS Administrator and other administration utilities for your computer's processor type.

The online version of the SMS Administrator's Guide.


Operations (Installation Options)

Operations

The Operations button enables you to maintain an existing site.

The Operations button opens the Site Operations dialog box, which is used for the following tasks:

Upgrading a Site

Changing the SMS Service Account for a Site

Changing the SMS Database Settings for a Primary Site

Resetting a Site

Shutting Down a Site


Database Deinstallation Options dialog box

Database Deinstallation Options

Enables you to drop the site database, to drop the site database and its transaction log devices, and to delete the device files.

You can keep the site database and its transaction log by clearing all the check boxes.

Drop Database

Drop Database And Log Devices

Shutdown SQL Server And Delete Device Files


Drop Database

Drops the site database from its devices on the SQL Server.


Drop Database And Log Devices

Drops the site database's device and its transaction log device on the SQL Server. If you select Drop Database And Log Devices, Drop Database is automatically selected. You cannot clear Drop Database until you clear Drop Database And Log Devices.


Shutdown SQL Server And Delete Device Files

Shuts down the SQL Server and deletes the site database's device file and its transaction log device file. Shutdown SQL Server And Delete Device Files is only available if the SQL Server is installed on the site server. If you select Shutdown SQL Server And Delete Device Files, Drop Database and Drop Database And Log Devices are automatically selected. You cannot clear Drop Database and Drop Database And Log Devices until you clear Shutdown SQL Server And Delete Device Files.


Installation Directory Dialog Box

Specifies the directory in which to install the SMS components on the site server.

Installation Directory

Specifies the full path where the Setup program will install the SMS root directory on the site server. The directory must be on an NTFS partition. By default, Setup specifies the SMS directory at the root of the NTFS drive with the most available space (for example, C:\SMS).

It is recommended that at least 100 megabytes of free space is available on the installation drive.

The path must include the drive letter and directory path (for example, C:\SMSROOT). If the directory does not exist, the Setup program creates the new directory for you and sets that directory as the SMS root directory.

If you are installing SMS on the server for the first time, you should specify a new directory (one that doesn't exist) or an empty directory. If the directory exists, the Setup program displays a message box that asks you whether to delete the directory (and its contents) and create it again.

Caution  If the site will have LAN Manager or NetWare servers, make sure that you specify an 8.3 name for the directory so that the SMS root directory can be created properly on the Windows NT Servers and LAN Manager logon servers using the FAT file system and on the NetWare logon servers. SMS uses the name for the Installation Directory as the SMS root directory on logon servers.


SMS Install Options

Setup Install Options

Enables you to choose whether to install the selected components (Continue) or to select additional components you want to install (Custom).

Setup Will Install The Following Components

Displays the components selected for installation. The default components are x86 Client components and the Server and Client components for the processor type of the site server. For example, if your site server has a MIPS processor, Setup would, by default, install the x86 components and the MIPS Server and Client components.

Custom

Choose this button to select the components you want to install. If you want to add support for platforms beyond the default components, you should use this option to select all the platforms you want to support at the site.

The components that are selected for installation determine the platforms that the site can support. You should install the components for all the processors types that you intend to support within the site and at any secondary sites that you create from the site.

For example, if you install only the x86 Server and x86 Client components, the site can only support computers with x86 processors and you can only install secondary sites that have a site server that has an x86 processor. If you add a logon server that has an Alpha processor, the SMS system will not be able to add the logon server until you install the Alpha components on the site server.

Note  Using the SMS Setup program, you can add support for additional processors after you install the site. After a primary site has been installed, the Setup program is added to the Systems Management Server program group of site server. You can use the Setup program to install additional platform support and other options.


Software Installation Options

Enables you to select the processor types that you want to support at the site and any other options you want to install.

The Software To Install box specifies all the components to install. By default, the Software To Install box contains the Server and Client components for the processor type that Setup has detected on the site server. You cannot deselect these two items. The Software To Install box also contains the x86 Client components.

To add a component, select the component in the Available Software box and click Add.

The server components are the components that run on site servers and logon servers. The client components are the components that run on clients. Scripts are the installation scripts and network application configuration scripts for some popular applications (such as Microsoft Excel, Microsoft Office, and so on).


SQL Device Creation dialog box

SQL Device Creation

Specifies the configuration information used to create the database device and the log device.

Database Device

Path

Size

Log Device

Path

Size

Caution  The SMS Setup program can create devices on the SQL Server only if the SQL Server is installed on the site server. If the SQL Server you are using for the site database is installed on another server, you must manually create the database device and transaction log device, using SQL Server tools such as the Microsoft SQL Administrator.


Database Device (SQL Device Creation)

The name of the device that will store the site database.

The device name is the name you specified in the SQL Database Configuration dialog box.

Note that the site database and the transaction log must be on separate devices. You must have a site database device and a transaction log device.


 Database Device Path (SQL Device Creation)

Type the path and name of the file used for the device. By default, the device path is install_drive:\SMSDATA\SMS.DB where install_drive is the drive where you installed SMS on the site server. If you specify a local drive (such as C:), the path specifies a drive on the site server.

If the directory does not exist, the Setup program creates the new directory for you.


Database Device Size (SQL Device Creation)

Type the size of the device (in megabytes). The default is 45 megabytes. Note that the site database will occupy the entire device. For information about planning the database size, see the SMS Administrator's Guide.


Log Device (SQL Device Creation)

The name of the device that will store the site database's transaction log.

The device name is the name you specified in the SQL Database Configuration dialog box.

Note that the site database and the transaction log must be on separate devices. You must have a site database device and a transaction log device.


Log Device Path (SQL Device Creation)

Type the path and name of the file used for the device. By default, the device path is C:\SMSDATA\SMS.LOG. If you specify a local drive (such as C:), the path specifies a drive on the site server.

If the directory does not exist, the Setup program creates the new directory for you.


Log Device Size (SQL Device Creation)

Type the size of the transaction log for the database (in megabytes).

Note that the site database will use the entire device for its transaction log. For information about planning the log device size, see the SMS Administrator's Guide.

The transaction log records any changes made to the site database. The default is 5 megabytes. The default should be able to safely handle an SMS system with a relatively large number of computers.


SQL Connections dialog box

SQL Connections

Enables you to set the SQL Server's maximum number of user connections.

If the SQL Server does not have a maximum user connection setting that is greater than 20, the SQL Connections dialog box will appear.

Set Maximum User Connections To

Type the maximum number of connections to the SQL Server where the site database is installed. By default, Setup keeps the number of maximum user connections setting that already exists on the SQL Server. If the SQL Server is used for the site database only, you should have a setting of 20 or greater. If you have other databases, you should add 20 or more to the existing number of connections.

Choose Set to change the maximum user connections setting on the SQL Server. Choose Ignore to keep the current setting.

Caution  If you choose Set, the SMS setup program will stop and restart the SQL Server so that the new user connection setting can take effect on the SQL Server. Stopping the SQL Server will break all existing connections to the SQL Server.


SQL Database Configuration dialog box

SQL Database Configuration

Defines the configuration information used to set up the site database.

SQL Server Name

SQL Login

Password

Confirm Password

Database Name

Database Device

Log Device

Device Creation


SQL Server Name (SQL Database Configuration)

Type the name of the Microsoft SQL Server where you want to place the site database. The SQL Server must be running Microsoft SQL Server version 4.21. This can be any Microsoft SQL Server that the site server has access to.

If you specify a SQL Server that is installed on the site server, you can use Setup to create the database, database device, and log device for the site database for the site.

If you specify a SQL Server installed on another server, you must manually create the database device and log device for the site database for the site--before you complete the SMS Setup program. If you create only the devices, you can create the site database if you specify a login ID with administrator permissions on the SQL Server. If you do not want to use a login ID with administrator permissions, you must create the database, the database device, and the log device manually. For information about creating databases and devices, see the Microsoft SQL Server documentation.


SQL Login (SQL Database Configuration)
Login ID (SQL Database Configuration)

Type the SMS SQL login ID used by the Setup program to install the site database on the SQL Server specified by SQL Server Name. The SMS SQL login ID will also be used by SMS services that access the site database (such as the Site Hierarchy Manager and the SMS Executive).

The SQL Server must have a corresponding login ID with the same name and password specified in this box and that login ID must have database owner (dbo) privileges on the site database.

If you choose to install the site database on the SQL Server on the site server, the SMS Setup program can create the devices for the site database and its transaction log as well as creating a database for the site database. To create all devices and databases through the SMS Setup program, the SMS SQL login ID specified in the SMS Setup program must have system administrator (sa) permissions. Otherwise, you can manually create the devices as you would using a SQL Server on another server.

If you choose to install the site database on a SQL Server on another server (not the site server), you must manually create the device for the site database and the device for the site database's transaction log. The SMS SQL login ID specified in the SMS Setup program must have Create Database, Dump Database, and Dump Transaction permissions on the master database. This enables the SMS Setup program to create and maintain the site database.


Password (SQL Database Configuration)

Type the password for the SMS SQL login ID that you specified for SQL Login.


Confirm Password (SQL Database Configuration)

Retype the password that you specified for Password.


Database Name (SQL Database Configuration)

Type the name of the site database. By default, the database name is SMS.

If you are using an existing database for the site database, specify the name of the database. You should ensure that the existing database does not contain any data that you want to keep.

If you are creating the site database, the database name must follow the SQL Server rules for identifiers. The name must be from 1 through 30 characters long and the first character must be a letter or the symbols @ or _. By default, SQL Server is case sensitive--unless you have installed the SQL Server using a case insensitive sort order.


Database Device (SQL Database Configuration)

Type the name of the device that will store the site database.

If you are using an existing device, specify the name of the device. If you are using an existing device, you should ensure that the site database is the only database on the device. No other databases can exist on the database device.

Note that the site database and the transaction log must be on separate devices. You must have a site database device and a transaction log device.

If you are creating the device, the database name must follow the SQL Server rules for identifiers. See the rules for Database Name. By default, the device name is SMSData. Click Device Creation to set the configuration of the device.

Caution  Setup will automatically create the site database on the database device so that the site database will occupy the entire device. If other databases exist on the device specified by Database Device, the Setup program will prompt you to delete the existing databases on the device. The Setup program cannot proceed if other databases exist on the device. If you choose not to delete the existing databases on the device, the SQL Database Configuration dialog box will appear. You should specify a database device that has no existing databases or databases that you are willing to delete.


Log Device (SQL Database Configuration)

Type the name of the device that will store the site database's transaction log.

If you are using an existing device, specify the name of the device. If you are using an existing device, you should ensure that there are no databases on the device. The transaction log will occupy the entire device. No other databases can exist on the log device.

Note that the site database and the transaction log must be on separate devices. You must have a site database device and a transaction log device.

If you are creating the device, the database name must follow the SQL Server rules for identifiers. See the rules for Database Name. By default, the device name is SMSData. Click the Device Creation to set the configuration of the device.

Caution  Setup will automatically use the entire device for the transaction log. If other databases exist on the device specified by Log Device, the Setup program will prompt you to delete the existing databases on the device. The Setup program cannot proceed if other databases exist on the device. If you choose not to delete the existing databases on the device, the SQL Database Configuration dialog box will appear. You should specify a database device that has no existing databases or databases that you are willing to delete.


Device Creation (SQL Database Configuration)

If you want to create the database device and transaction log device through SMS Setup, you can click Device Creation to specify the database device and log device configuration.

Caution  The SMS Setup program can create devices on the SQL Server only if the SQL Server is installed on the site server.

If the SQL Server you are using for the site database is installed on another server, you must manually create the database device and log device, using SQL Server tools such as the SQL Administrator. If you specified a SQL Server that is not installed on the site server, the Device Creation button is disabled.


Primary Site Configuration Information Dialog Box

Specifies the configuration information used to set up a Primary Site.

Site Code

Site Name

Site Server

Site Server Domain

Automatically Detect All Logon Servers

Username

Password

Confirm Password


Site Server (Primary Site Configuration Information)

The name of a Windows NT Server that will act as the site server (the computer where you are currently running the SMS Setup program.


Service Account Dialog Box

Enables you to change the SMS Service Account that you set when you first ran the SMS Setup program. All SMS services at the site use the SMS Service Account to start up and to manage site. Setup will verify that the SMS Service Account is valid in the site server domain.

From Domain

Username

Password

Confirm Password

Note that changing the SMS Service Account in the Service Account dialog box affects only SMS services--not the actual user account. The Service Account dialog box only configures SMS services so that they will use the specified account and password. To change, modify, or delete a user account or a user account's password in the site server domain and all other domains at the site, you must use the User Manager for Domains tool (for Windows NT domains), the LAN Manager Administrator's Screen (for LAN Manager domains), or the NetWare SYSCON utility (for NetWare domains).

The Service Account dialog box in Setup enables you to change the SMS Service Account and have the change take effect immediately. The Setup program stops and restarts the SMS services. However, you can only change the SMS Service Account for the local site. The Service Account dialog box also enables you to restart the SMS services if you specified an invalid account or password for the SMS Service Account in the SMS Administrator.

Using the SMS Administrator, you can also change the SMS Service Account through the Accounts dialog box from the Services dialog box of the Site Properties dialog box. Using the SMS Administrator, you can change the SMS Service Account for the current site and any site below it in the hierarchy. However, SMS does not verify that the new SMS Service Account is valid.


Active SQL Server and Database Dialog Box

Enables you to change the SMS SQL login ID used by the SMS services that access the site database.

If you have restored the site database to another SQL Server or you have renamed the site database, you can also specify the new SQL Server and site database name. Setup will verify that the SMS SQL login ID is valid on the specified SQL Server.

SQL Server

Login ID

Password

Confirm Password

Database Name

Note that changing the SMS SQL login ID in the Active SQL Server And Database dialog box affects only SMS services--not the actual SMS SQL login ID. The Active SQL Server And Database dialog box only configures SMS services so that they will use the specified SMS SQL login ID and password. To change, modify, or delete an SMS SQL login ID on the SQL Server, you must use the SQL Administrator (or an ISQL command).

The Active SQL Server And Database dialog box in Setup enables you to change the SMS SQL login ID and have the change take effect immediately. The Setup program stops and restarts the SMS services. However, you can only change the SMS SQL login ID for the local site. The Active SQL Server And Database dialog box also enables you to restart the SMS services if you specified an invalid SMS SQL login ID or password for the SMS SQL login ID in the SMS Administrator.

Using the SMS Administrator, you can also change the SMS SQL login ID through the Accounts dialog box from the Services dialog box of the Site Properties dialog box. Using the SMS Administrator, you can change the SMS SQL login ID for the current site and for any site below it in the hierarchy. However, SMS does not verify that the new SMS SQL login ID is valid.


SQL Server (Active SQL Server and Database)
SQL Server

Type the name of the SQL Server where site database is installed.

If you have restored the site database to another SQL Server, you can specify the new SQL Server. You should only use this box if you are restoring the site database to another server.


Login ID (Active SQL Server and Database)
Login ID

Type the SMS SQL login ID that you want the SMS services to use to access the site database.

The SQL Server must have a corresponding login ID with the same name and password specified in this box and that login ID must have database owner (dbo) privileges on the site database.


Database Name (Active SQL Server and Database)
Database Name

Type the name of the site database.

If you have restored the site database using a different database name, you can specify the new database name. You should only use this box if you are restoring the site database using a different database name.


Upgrading SMS Components

Upgrading SMS Components at a Site

Through the SMS Setup program, you can upgrade all SMS components (all SMS services and files) on the site server and on all logon servers in all domains that are part of the site. The components installed at the site are upgraded to the components at the specified path.

During an upgrade, the Site Configuration Manager replaces all SMS components at the site with components from the specified path. If the site has a secondary site directly beneath it, the Site Hierarchy Manager will create a system job to upgrade the components at those secondary sites (this means that you must upgrade a secondary site's direct parent site in order to upgrade that secondary site).

When you upgrade a site, the clients at the site and at any secondary sites directly beneath it are upgraded to the new components when a user at the client runs the SMSLS batch file or the Client Setup program.

To upgrade a primary site and its direct secondary sites

1.	At the site server for the site, start the SMS Setup program from the SMS CD-ROM or from the Systems Management Server program group in the Program Manager.

The SMS Setup dialog box appears.

2.	Click Continue.

Setup checks the disk drives and registry of the site server for an existing version of SMS.

The Existing Installation dialog box appears.

3.	Click Continue.

The Existing Installation Options dialog box appears.

4.	Click Upgrade Site.

If you run the Setup program from the SMS CD-ROM, Setup uses the components on the SMS CD-ROM to update the site's components.

If you run the Setup program from the SMS root directory on the site server, Setup prompts you for the location of the components you want to use to upgrade the site.

In the entry box, type the drive and directory path to the SYSTEM.MAP file. For example, if you wanted to upgrade from the SMS CD-ROM in the E: drive, you would use the path E:\SMSSETUP. You can also use a UNC path.

A message box appears and asks if you want to upgrade the components at the secondary sites directly beneath the current site.

5.	Choose whether to upgrade the components at the secondary sites directly beneath the current site.

6.	Click Yes when prompted for confirmation to upgrade the site.

The Microsoft Systems Management Server Upgrade dialog box appears. The Upgrade dialog box displays the progress of the upgrade. Setup performs the upgrade in three phases: Shutdown (shutdown of all SMS services at the site), File Installation (decompression, installation, and configuration of the upgraded SMS components), and System Restart (restart all SMS services at the site). The current phase of the upgrade is displayed in the title bar of the dialog box. The progress for the current phase is displayed by the progress bar.

The Upgrade dialog box displays the progress of the upgrade.

When the upgrade is complete, the Success dialog box appears. The upgrade components have been installed at the site and all SMS services at the site are running with the upgraded components.

To upgrade components at clients, users at the clients must run the SMSLS batch file or the Client Setup program.


Adding Components to a Site

On a site server, the client and server components of the site server's processor type, the Intel client components, the SMS Administrator of the site server's processor type, Network Monitor of the site server's processor type, and the SCRIPTS option are installed by default. Using the Add Components button in SMS Setup, you can upgrade those components or add new components to the site.

On a Windows NT computer where the SMS Administrator or Network Monitor were installed using the Install Admin Tools option in SMS Setup, the Add Component button adds new SMS tools or updates the SMS tools that were installed on the computer.

When you add new components to a primary site, the Site Configuration Manager installs the new SMS components at the site. If the site has a secondary site directly beneath it and you choose to upgrade the secondary sites, the Site Hierarchy Manager will create a system job to install the new components and upgrade the existing components at that secondary site (this means that you must add a new component to a secondary site's direct parent site to add it to that secondary site). Note that this system job upgrades all components at the secondary site.

To add new components to a primary site and its direct secondary sites

1.	At the site server of the site where you want to add the new components, log on using a user account with administrator privilege on the computer itself (the user account is a member of the Administrators group) and on the site server's domain (member of Domain Admins group).

If the SQL Server that you will use for the site database is installed on another computer (not the site server computer), make sure that the user account that you have used to log on at the site server has access to the SQL Server and that the SMS Service Account has access to the SQL Server.

If you are upgrading or adding components to a Windows NT computer where the SMS Administrator or Network Monitor were installed using the Install Admin Tools option in SMS Setup, log on using a user account with administrator privilege on the computer (the user account is a member of the Administrators group.

2.	Start the SMS Setup program from the SMS CD-ROM or from the Systems Management Server program group in the Program Manager.

The SMS Setup dialog box appears.

3.	Click Continue.

Setup checks the disk drives and registry of your computer for an existing version of SMS.

The Existing Installation dialog box appears.

4.	Click Continue.

The Existing Installation Options dialog box appears.

5.	Click Add New Components.

If you run the Setup program from the SMS CD-ROM, Setup uses the components on the SMS CD-ROM to update the site's components.

If you run the Setup program from the SMS root directory on the site server, Setup prompts you for the location of the components you want to use to upgrade the site.

In the entry box, type the drive and directory path to the SYSTEM.MAP file. For example, if you wanted to upgrade from the SMS CD-ROM in the E: drive, you would use the path E:\SMSSETUP. You can also use a UNC path.

The Software Installation Options dialog box appears.

6.	Select the components that you want to install.

The Software To Install box specifies all the components to install. To add a component, in the Available Software box, select the component and click Add.

The server components are the components that run on site servers and logon servers. The client components are the components that run on clients. Scripts are the installation scripts and network application configuration scripts for some popular applications (such as Microsoft Excel, Microsoft Office, and so on). Network Monitor is a network analyzer tool.

7.	Click OK.

A message box appears and asks if you want to install the components to the secondary sites directly beneath the current site.

8.	Choose whether to install the components to the secondary sites directly beneath the current site.

Click Yes when prompted for confirmation to upgrade the site.

The SMS New Software Components dialog box appears. This dialog box displays the progress of the new component installation.

When the installation is complete, the Success dialog box appears. The new components have been installed at the site.


Resetting a Site

When the system is reset, SMS Setup does the following:

Stops all SMS services on the site server.

Deinstalls the Site Configuration Manager.

Reinstalls and restarts the Site Configuration Manager.

Forces two new site configuration files to be written (one from the Current site properties and one from the Proposed site properties).

Evaluates the new configurations with the previous site configuration file.

Selects the best configuration.

Updates the site's configuration using the selected site configuration file.

Restarts all the SMS services on the site server.

To reset a site

1.	At the site server of the site that you want to reset, log on using a user account with administrator privilege on the computer itself (the user account is a member of the Administrators group) and on the site server's domain (member of Domain Admins group).

If the SQL Server that you will use for the site database is installed on another computer (not the site server computer), make sure that the user account that you have used to log on at the site server has access to the SQL Server and that the SMS Service Account has access to the SQL Server.

2.	Start the SMS Setup program from the SMS CD-ROM or from the Systems Management Server program group in the Program Manager.

The SMS Setup dialog box appears.

3.	Click Continue.

Setup checks the disk drives and registry of the site server for an existing version of SMS.

The Existing Installation dialog box appears.

4.	Click Continue.

The Existing Installation Options dialog box appears.

5.	Click Reset Installation.

The SMS System Reset dialog box appears, showing the progress of the reset and the current action that SMS Setup is performing.

When the reset is complete, the Success message box appears.


Shutting Down a Site

You can use SMS Setup to stop all SMS services on the site server and all logon servers in all domains that are part of the site.

You can restart the SMS services clicking the Reset Site or the SMS Service Manager.

To shutdown a site

1.	At the site server of the site whose services you want to shutdown, log on using a user account with administrator privilege on the computer itself (the user account is a member of the Administrators group) and on the site server's domain (member of Domain Admins group).

If the SQL Server that you will use for the site database is installed on another computer (not the site server computer), make sure that the user account that you have used to log on at the site server has access to the SQL Server and that the SMS Service Account has access to the SQL Server.

2.	Start the SMS Setup program from the SMS CD-ROM or from the Systems Management Server program group in the Program Manager.

The SMS Setup dialog box appears.

3.	Click Continue.

Setup checks the disk drives and registry of the site server for an existing version of SMS.

The Existing Installation dialog box appears.

4.	Click Continue.

The Installation Options dialog box appears.

5.	Click Operations.

The Site Operations dialog box appears.

6.	Click Shutdown.

The SMS System Shutdown dialog box appears, showing the progress of the shutdown and the current action that SMS Setup is performing.

When the shutdown is complete, the Success message box appears.


Changing the SQL Login ID, Site Database, and SQL Server Settings

After you've installed a primary site, the SMS Setup program lets you change the SQL login ID used by the SMS services, switch the site to another site database, or switch to another SQL Server.

Caution  You should change the name of the site database or the SQL Server only if you have restored the site database for the site to a database with another name or if you have restored the site database to another SQL Server.

Changing the SMS SQL login ID affects only SMS services--not the actual SMS SQL login ID account. The SMS Setup program sets SMS services only so that they will use the specified account and password. To change, modify, or delete a login account or a login account's password on the SQL Server, you must use the SQL Administrator (or an ISQL command).

You can also change the SMS SQL login ID through the Accounts dialog box for the site (from the Site Properties dialog box). However, the SMS Setup program verifies the account (checks that the SMS SQL login ID exists and has the proper permissions). When you change the SMS SQL login ID with the Accounts dialog box, Setup does not verify the account.

To change settings for the site database of a site

1.	If you are changing the SMS SQL login ID, change the SMS SQL login ID or create a new SMS SQL login ID on the SQL Server containing the site database.

Using the SQL Administrator, connect to the SQL Server that contains the site database and then change the SMS SQL login ID or create a new SMS SQL login ID.

If you create a new SMS SQL login ID, make sure that the login ID has the appropriate permissions on the site database device and the transaction log device.

2.	If you are restoring the site database to the current SQL Server or restoring it to another SQL Server, restore the site database to the SQL Server that you want to contain the site database.

For information about backing up and restoring the database, see the Microsoft SQL Server documentation.

3.	At the site server of the site where you want to change the SMS SQL login ID, log on using a user account with administrator privilege on the computer itself (the user account is a member of the Administrators group) and in the site server's domain (member of Domain Admins group).

If the SQL Server that you will use for the site database is installed on another computer (not the site server computer), make sure that the user account that you have used to log on to the site server has access to the SQL Server and that the SMS Service Account has access to the SQL Server.

4.	Start the SMS Setup program from the SMS CD-ROM or from the Systems Management Server program group in the Program Manager.

The SMS Setup dialog box appears.

5.	Click Continue.

Setup checks the disk drives and registry of the site server for an existing version of SMS.

The Existing Installation dialog box appears.

6.	Click Continue.

The Existing Installation Options dialog box appears.

7.	Click Active SQL Server.

The Active SQL Server And Database dialog box appears.

8.	Make changes to the SMS SQL login ID account:

SQL Server

Lets you specify the SQL Server where site database is installed.

If you have restored the site database to another SQL Server, you can specify the new SQL Server. You should only use this box if you are restoring the site database to another server.

Login ID

Type the SMS SQL login ID that you want the SMS services to use to access the site database.

The SQL Server must have a corresponding login ID with the same name and password specified in this box and that login ID must have database owner (dbo) privileges on the site database.

Password

Type the password for the SMS SQL login ID that you specified for Login ID.

Confirm Password

Retype the password that you specified in for Password.

Database Name

Type the name of the site database.

If you have restored the site database using a different database name, you can specify the new database name. You should fill in this box only if you are restoring the site database under a different database name.

9.	Click OK.

The Setup program verifies that all the settings are valid (the SQL Server exists, the SMS SQL login ID exists on the SQL Server, and that the specified database is an SMS site database), and then makes the changes to site.


Changing the SMS Service Account

Changing the SMS Service Account affects only SMS services--not the actual user account. The SMS Setup program configures SMS services only so that they will use the specified account and password. To change, modify, or delete a user account or a user account's password on the site server domain and all other domains in the site, you must use the User Manager for Domains tool (for Windows NT domains), the LAN Manager Administrator's Screen (for LAN Manager domains), or the NetWare SYSCON utility (for NetWare domains).

Caution  Although you can simply change the password of the SMS Service Account, it is highly recommended that you create a new SMS Service Account and switch from the old account to the new one.

If the site server is restarted while the Site Configuration Manager is attempting to change the SMS Service Account for the SMS services and you have only changed the password, the Site Configuration Manager may not be able to restart, depending on its progress before the site server was restarted. If you changed the password only for the SMS Service Account, the Site Configuration Manager cannot fall back to the old account to start itself and complete the SMS Service Account change. If you use a different account, the Site Configuration Manager can use the old SMS Service Account to successfully finish the SMS Service Account change.

To change the SMS Service Account

1.	At all domains in the site, use the appropriate user account management tool to change the SMS Service Account or create a new SMS Service Account.

If you create a new SMS Service Account, make sure that SMS Service Account has the appropriate permissions on each domain in the site. For information about creating a SMS Service Account in a domain, see the SMS Administrator's Guide.

2.	At the site server of the site where you want to change the SMS Service Account, log on through a user account with administrator privilege on the computer itself (the user account is a member of the Administrators group) and in the site server's domain (member of Domain Admins group).

If the SQL Server that you will use for the site database is installed on another computer (not the site server computer), make sure that the user account through which you have logged on at the site server has access to the SQL Server and that the SMS Service Account has access to the SQL Server.

3.	Start the SMS Setup program from the SMS CD-ROM or from the Systems Management Server program group in the Program Manager.

The SMS Setup dialog box appears.

4.	Click Continue.

Setup checks the disk drives and registry of the site server for an existing version of SMS.

The Existing Installation dialog box appears.

5.	Click Continue.

The Existing Installation Options dialog box appears.

6.	Click Service Account.

The Service Account dialog box appears.

7.	Make changes to the SMS Service Account:

From Domain

Type the domain containing the SMS Service Account.

If you specified a trusted domain account, the From Domain box displays the domain containing the SMS Service Account. If you specified a local domain account, the From Domain box displays the name of the site server domain.

For information about the SMS Service Account, see the SMS Administrator's Guide.

Username

Type the name for the SMS Service Account.

All SMS services at the site run in the specified user account context. Make sure that you have created a user account for use as the SMS Service Account and you have set up the proper permissions for that account at the site server domain and all other domains at the site.

For information about creating an SMS Service Account, see the SMS Administrator's Guide.

Password

Type the password for the user account that you specified for Username.

Confirm Password

Retype the password that you specified for Password.

8.	Click OK.

The Setup program verifies that all the settings are valid (the SMS Service Account exists in the specified domain and that the account from that domain has the proper permissions on the site server domain) and that the specified database is an SMS site database), and then makes the changes to site.


Removing a Primary Site

Removing a primary site is a four step process. You must delete the site from the SMS site hierarchy (if the site is part of a hierarchy), remove SMS from clients in the site, remove the site, and maintain the site databases of the parent sites of the removed site.

To remove a primary site

1.	Remove any secondary sites that are direct children of the site you want to remove.

Removing a Secondary Site

If you do not remove the direct secondary sites, the secondary site will be orphaned--you cannot administer an orphaned secondary site.

Removing an Orphaned Secondary Site

2.	Remove the site from the site hierarchy.

If the site you want to remove is part of a site hierarchy (the site has subsites below it or a parent site above it), you must adjust the hierarchy to account for the removed site. For example, if the site to remove has a parent site and also has two subsites, you need to detach the site from its parent site, detach the two subsites from the site, and then attach the two subsites to a new parent site (replacing the removed site as the parent site).

Caution  Make sure that the parent site has received and completed the detach instructions from the site you want to remove. To verify that the site to remove has been detached from its parent site, log in to the site database of the parent site, open the Sites window, refresh the display, and make sure that the site to remove is no longer displayed in the Sites window.

For information about attaching and detaching a parent site, see the SMS Administrator's Guide.

3.	If you are also removing the clients from SMS (instead of moving them to another site), remove the SMS components from the clients.

4.	Deinstall the site itself.

The SMS Setup program can remove all SMS components from the site server and all logon servers in the site's domains. Note that if the SMSLS batch file or Client Setup program have been run on a site server or logon server to install the client components on those computers, these client components must be removed using the Client Setup program. Setup does not remove client components that have been installed on computers. You can use the SMS Setup program to remove all SMS components from either a primary site or a secondary site.

Deinstalling a Primary Site

5.	If the clients in the site are being completely removed from the SMS system, you should remove those computers from the site databases of all parent sites above the deinstalled site. Using the database maintenance utility, you can remove the inventory for those clients from each site database.

If you do not remove the clients from the site databases of the parent sites, the clients will be orphaned without a site in those databases. When you start or refresh the SMS Administrator, a message box will appear displaying the sites that have orphaned their clients.

To find the orphaned clients in the site database, execute a query against the Personal Computer architecture, searching for computers that have the site code of the removed site (Site attribute of the Identification group). Use the database maintenance utility to remove those computers from the site database.

For information about the database maintenance utility, see the SMS Tools help file.

If the clients are being moved to another site, make sure that the clients run the SMSLS batch file from the logon servers at the new site.

If the clients are being moved to a site that is not within the same part of the hierarchy as the removed site, you may still need to remove the clients from the site databases of some parent sites.

6.	Optionally, you can confirm that all SMS components have been removed from the site server and logon servers.

To confirm that SMS has been removed from the site server and logon servers at the site's domains, make sure that the following items are removed:

On the site server:

All SMS services.

All SMS shares (SMS_SHRx, SMS_SHR, SMS_SITE).

If the site has Macintosh support enabled, make sure that the SMS_SHR volume is removed.

The SMS root directory and all its files and subdirectories.

The SMS key in the registry. The full key name is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS.

The MS\SMS directory.

The SMS.INI file in the root of the C: drive. Note that the SMS.INI file is a hidden file.

On the LAN Manager and Windows NT Server logon servers:

All SMS shares (SMS_SHRx, SMS_SHR).

If the logon server has Macintosh support enabled, make sure that the SMS_SHR volume is removed.

The SMS root directory and all its files and subdirectories.

The MS\SMS directory.

On computers running Windows NT Server, make sure the SMS key in the registry is removed. The full key name is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS.

The SMS Inventory Agent service.

The Package Command Manager service.

The SMS.INI file in the root of drive C.

If the site has the Automatically Configure Workstation Logon Scripts option enabled, make sure that the SMS components are removed from the SCRIPTS subdirectory of the REPL$ shares of the primary domain controllers and the NETLOGON shares of all logon servers running LAN Manager and Windows NT .
In addition, make sure that the SMSLS batch file is removed from any logon scripts that were modified by SMS. You should also ensure that the SMSLS batch file is removed from the user profiles of user accounts that have the SMSLS batch file as their logon script.

If the logon server is also a helper server, make sure that the SMS Executive service is removed.

On the NetWare logon servers:

The SMS root directory and all its files and subdirectories.

If the site has the Automatically Configure Workstation Logon Scripts option enabled, make sure that the SMS commands are removed from the system login script of each NetWare logon server.


Deinstalling a Primary Site

To deinstall a primary site

1.	At the site server of the site that you want to deinstall, log on using a user account with administrator privilege on the computer itself (the user account is a member of the Administrators group) and in the site server's domain (member of Domain Admins group).

If the SQL Server that you will use for the site database is installed on another computer (not the site server computer), make sure that the user account that you have used to log on to the site server has access to the SQL Server and that the SMS Service Account has access to the SQL Server.

2.	At the site server for the site, start the SMS Setup program from the SMS CD-ROM. Optionally, you can run the SMS Setup program from site server's Program Manager, using the SMS Setup program item in the Systems Management Server program group.

The Systems Management Server Setup dialog box appears.

3.	Click Continue.

Setup checks the disk drives and registry of the site server for an existing version of SMS.

The Existing Installation dialog box appears.

4.	Click Continue.

The Existing Installation Options dialog box appears.

The Existing Installation Options dialog box lets you remove or upgrade the site.

5.	Click Deinstall.

The Database Deinstallation Options dialog box appears.

The Database Deinstallation Options dialog box lets you drop the site database, drop its devices, and delete the device files.

6.	Select the deinstallation options for the site database.

You can keep the site database and its transaction log by clearing all the check boxes. Or you can choose to drop the database, drop the site database's device and its transaction log device, or delete the device files.

You can make the following settings:

Drop Database drops the site database from its devices on the SQL Server.

Drop Database And Log Devices drops the site database's device and its transaction log device on the SQL Server. If you select this option, Drop Database is automatically selected. You cannot clear Drop Database until you clear Drop Database And Log Devices.

Shutdown SQL Server And Delete Device Files shuts down the SQL Server and deletes the site database's device file and its transaction log device file. This option is only available if the SQL Server is installed on the site server. If you select this option, Drop Database and Drop Database And Log Devices are automatically selected. You cannot clear Drop Database and Drop Database And Log Devices until you clear Shutdown SQL Server And Delete Device Files.

7.	Click OK.

8.	Click Yes when prompted for confirmation to deinstall the site.

The Microsoft Systems Management Server Deinstallation dialog box appears, displaying the progress of the deinstallation. When the deinstallation is complete, the Success dialog box appears.


Installing the SMS Administrator

Installing the SMS Administrator on a Computer Running Windows NT

When you install a primary site, the SMS Setup program automatically installs the SMS Administrator and other utilities on the site server and creates the Systems Management Server program group for the SMS Administrator. You can also install the SMS Administrator and administration utilities on other computers running Windows NT version 3.5.

To install the SMS Administrator on a computer running Windows NT

1.	Start the Setup program.

Insert the SMS CD-ROM into the computer's CD-ROM drive, switch to the CD-ROM drive, change to the SMSSETUP directory, change to the directory of the processor type of the site server (X86, MIPS, or Alpha), and type setup

The Systems Management Server Setup dialog box appears.

2.	Click Continue.

The SMS Setup program checks your computer's hard disk for an existing version of SMS.

If SMS is not currently installed on your computer, the Registration dialog box appears. In the Registration dialog box, type your name, your organization name, and your product identification number, and then click Continue. The Registration dialog box appears again. Verify that the name, organization, and product identification number you entered is correct, and then click Continue. If you need to change the user registration information, click Change and make your changes. The Installation Options dialog box appears.

If SMS is currently installed on your computer, the Existing Installation dialog box appears. Click Continue. The Installation Options dialog box appears.

3.	Click Install Admin Tools.

The Installation Directory dialog box appears.

4.	In the Installation Directory box, type the directory in which to install the SMS Administrator on your Windows NT computer.

You must specify the full path where you want the Setup program to install the SMS root directory on your Windows NT computer. By default, Setup specifies the SMSADMIN directory at the root of the drive with the most available space (for example, C:\SMSADMIN).

The path must include the drive letter and directory path (for example, C:\SMSADMIN). If the directory does not exist, the Setup program creates the new directory for you and sets that directory as the SMS root directory.

If you are installing SMS on the server for the first time, you should specify a new directory (one that doesn't exist) or an empty directory. If the directory exists, the Setup program displays a message box that asks you whether to delete the directory (and its contents) and create it again.

Caution  If you are installing the SMS Administrator on a computer that is already part of the SMS system (such as a secondary site server, helper server, logon server, or client), avoid installing the SMS Administrator in an existing directory used by SMS. By placing the SMS Administrator in its own directory, the SMS directories and components can be maintained separately from the SMS Administrator. This means you can deinstall or upgrade the SMS Administrator and the SMS components independently. Note that you cannot deinstall an SMS Administrator if it is installed in the SMS root directory and the SMS Administrator will be removed if SMS is removed from that computer.

5.	Click Continue.

The Setup Install Options dialog box appears.

The Setup Will Install The Following Components box displays the components selected for installation. The default components are the SMS Admin Tools (the SMS Administrator and other utilities) and Network Monitor for the processor type of your computer.

6.	Click Continue to install the default components or click Custom to select the additional components you want to install.

If you want to install the online version of the Microsoft Systems Management Server Administrator's Guide or you want to remove one of the default components, click Custom so that you can select the items you want to install.

If you click Custom, the Software Installation Options dialog box appears.

7.	Select the items you want to install.

8.	Click OK.

The Software To Install box specifies all the components to install. To add a component, in the Available Software box, select the component, and click Add. To remove a component, in the Software To Install box, select the component, and click Remove.

After you click OK, the Setup program checks for available disk space on the specified drive.

The Setup Install Options dialog box appears. The Setup Will Install The Following Components box displays the components you selected for installation.

9.	Click Continue.

The File Installation dialog box appears, displaying the progress of the file installation. The Network Monitor dialog box (if you choose to install the Network Monitor) appears, displaying the progress of the installation of Network Monitor. The System Installation dialog box appears, displaying the progress of the system configuration.

The Successful Installation dialog box appears.

10.	Click OK.

The SMS Administrator is installed on the computer. SMS Setup creates a Systems Management Server program group containing the SMS Administrator, SMS Security Manager, SMS Network Monitor (if you choose to install the Network Monitor), SMS MIF Form Generator, and SMS Help.

11.	If the computer where you have installed the SMS Administrator is running Windows NT Workstation, install the Server Manager and User Manager for Domains tools in a directory in the path of that computer.

The Server Manager and User Manager for Domains tools are provided with Windows NT Server and the Windows NT Resource Kit. On Windows NT Server computers, no additional programs or configuration is necessary.

12.	If you install the Network Monitor, install the Network Monitor Agent on the computer to complete the setup of Network Monitor.

Installing the Network Monitor Agent on a Windows NT Computer


SMS Administrator Console Setup Dialog Box

Specifies the directory in which to install the SMS Administrator and other SMS utilities on your Windows NT computer.

Installation Directory

Specifies the drive and directory in which to install the SMS Administrator and other utilities on your Windows NT Computer.

You must specify the full path where you want the Setup program to install the SMS root directory on your Windows NT computer. By default, Setup specifies the SMSADMIN directory at the root of the drive with the most available space (for example, C:\SMSADMIN).

The path must include the drive letter and directory path (for example, C:\SMSADMIN). If the directory does not exist, the Setup program creates the new directory for you and sets that directory as the SMS root directory.

If you are installing SMS on the server for the first time, you should specify a new directory (one that doesn't exist) or an empty directory. If the directory exists, the Setup program displays a message box that asks you whether to delete the directory (and its contents) and create it again.

Caution  If you are installing the SMS Administrator on a computer that is already part of the SMS system (such as a secondary site server, helper server, logon server, or client), avoid installing the SMS Administrator in an existing directory used by SMS. By placing the SMS Administrator in its own directory, the SMS directories and components can be maintained separately from the SMS Administrator. This means you can deinstall or upgrade the SMS Administrator and the SMS components independently. Note that you cannot deinstall an SMS Administrator if it is installed in the SMS root directory and the SMS Administrator will be removed if SMS is removed from that computer.


Installing Network Monitor on a Computer Running Windows NT

When you install a primary site, the SMS Setup program automatically installs the Network Monitor on the site server and creates the Systems Management Server program group for the SMS Administrator, Network Monitor, and other utilities. You can also install the Network Monitor (independently of SMS) on other computers running Windows NT version 3.5.

To install Network Monitor on a computer running Windows NT

1.	Start the Setup program.

Insert the SMS CD-ROM into the computer's CD-ROM drive, switch to the CD-ROM drive, change to the SMSSETUP directory, change to the directory of the processor type of the site server (X86, MIPS, or Alpha), and type setup

The Systems Management Server Setup dialog box appears.

2.	Click Continue.

The SMS Setup program checks your computer's hard disk for an existing version of SMS.

If SMS is not currently installed on your computer, the Registration dialog box appears. In the Registration dialog box, type your name, your organization name, and your product identification number, and then click Continue. The Registration dialog box appears again. Verify that the name, organization, and product identification number you entered is correct, and then click Continue. If you need to change the user registration information, click Change and make your changes. The Installation Options dialog box appears.

If SMS is currently installed on your computer, the Existing Installation dialog box appears. Click Continue. The Installation Options dialog box appears.

3.	Click Install Admin Tools.

The Installation Directory dialog box appears.

4.	In the Installation Directory box, type the directory in which to install the Network Monitor on your Windows NT computer.

You must specify the full path where you want the Setup program to install the SMS root directory on your Windows NT computer. By default, Setup specifies the SMSADMIN directory at the root of the drive with the most available space (for example, C:\SMSADMIN).

The path must include the drive letter and directory path (for example, C:\SMSADMIN). If the directory does not exist, the Setup program creates the new directory for you and sets that directory as the SMS root directory.

If you are installing SMS on the server for the first time, you should specify a new directory (one that doesn't exist) or an empty directory. If the directory exists, the Setup program displays a message box that asks you whether to delete the directory (and its contents) and create it again.

Caution  If you are installing the Network Monitor on a computer that is already part of the SMS system (such as a secondary site server, helper server, logon server, or client), avoid installing the Network Monitor in an existing directory used by SMS. By placing the Network Monitor in its own directory, the SMS directories and components can be maintained separately from the SMS Network Monitor. This means you can deinstall or upgrade the Network Monitor and the SMS components independently. Note that you cannot deinstall an Network Monitor if it is installed in the SMS root directory and the Network Monitor will be removed if SMS is removed from that computer.

5.	Click Continue.

The Setup Install Options dialog box appears.

The Setup Will Install The Following Components box displays the components selected for installation. The default components are the SMS Admin Tools (the SMS Administrator and other utilities) for the processor type of your computer and scripts.

6.	Click Custom to select the Network Monitor for installation.

The Software Installation Options dialog box appears.

7.	From the Available Software dialog box, select the Network Monitor and other items you want to install.

8.	Click Add.

The items that will be installed are displayed in the Software To Install box.

9.	Click OK.

After you click OK, the Setup program checks for available disk space on the specified drive.

The Setup Install Options dialog box appears. The Setup Will Install The Following Components box displays the components you selected for installation.

10.	Click Continue.

The File Installation dialog box appears, displaying the progress of the file installation. The Network Monitor dialog box (if you choose to install the Network Monitor) appears, displaying the progress of the installation of Network Monitor. The System Installation dialog box appears, displaying the progress of the system configuration.

11.	Click OK.

The Network Monitor is installed on the computer. SMS Setup creates a Systems Management Server program group containing the SMS Network Monitor and any other items that you chose to install.

12.	Install the Network Monitor Agent on the computer to complete the setup of Network Monitor.

Installing the Network Monitor Agent on a Windows NT Computer


Site Code

A three character code that the SMS system uses to identify the site. The site code for any site must be unique across the SMS system. This code is used as part of the addressing information for communicating between sites. The code is not case sensitive.

Caution  If you are installing a site that you plan to add to an existing SMS system, make sure that the site code you specify does not already exist in that SMS system. You should contact the administrator for your SMS system's Central Site to get a unique site code.


Site Name

The text used to label the site in the Sites window of the SMS Administrator.


Site Server

The name of a Windows NT Server computer that will act as the site server for the site.


Site Server Domain

The name of the domain containing the Windows NT Server computer that you specified as the Site Server.


Service Account

The user account used by the SMS services at the site. All SMS services at the site run in the specified user account context.

Creating an SMS Service Account


From Domain

The domain containing the SMS Service Account.

If you specified a trusted domain account, the From Domain box displays the domain containing the SMS Service Account. If you specified a local domain account, the From Domain box displays the name of the site server domain.


Username

The user name of the SMS Service Account.

Username specifies the user account name of the SMS Service Account. All SMS services at the site run in the specified user account context. This account will be used by site services to access all domains that are added to the site. Make sure that you have created a user account for the SMS Service Account.

You can specify a local domain account or a trusted domain account.

Local Domain Account

Trusted Domain Account


Local Domain Account (Service Account)

Specifies that the user account used by an SMS service for running in a domain or accessing servers in a domain is an account in that domain. You specify a local domain account by typing only the account name. For example, if you specify SMSAccount as the site's service account, a domain that gets added to the site uses the account SMSAccount within its own domain (when you install a site, you are also "adding" the site server domain at the same time). In addition, the Site Configuration Manager and Site Maintenance Manager services will use the account at the added domain to access and maintain the domain's logon servers. At the added domain, the SMS Inventory Agent service is installed on the domain's logon servers using that domain's account.


Trusted Domain Account (Service Account)

Specifies that the user account used by an SMS service for running in a domain or accessing servers in a domain is a trusted account from a specific domain. You specify a trusted domain account by typing the domain name and account name separated by a backslash (DOMAIN_NAME\account). However, the added domain must trust the domain specified by DOMAIN (this means that even if the equivalent user account in the local domain exists, that local account won't be used--unless the domain specified is the added domain's name).

For example, if you specify MASTERDOM\SMSAccount as the site's service account, a domain that gets added to the site uses the account SMSAccount from the trusted domain (when you install a site, you are also "adding" the site server domain at the same time). In addition, the Site Configuration Manager and Site Maintenance Manager services will use the trusted account at the added domain to access and maintain the domain's logon servers. At the added domain, the SMS Inventory Agent service is installed on the domain's logon servers using the trusted domain account.


Password

The password for the SMS Service Account (that you specified for Username).


Confirm Password

Verifies the password you specified in the Password box.


Automatically Detect Logon Servers
Automatically Detect All Logon Servers

Specifies whether the logon servers for the site server domain are automatically added to the site. If you enable this option, the SMS system automatically adds the site domain's logon servers to the SMS inventory and installs SMS components on these servers. If you clear this option, the logon servers are not added to the site domain--you must add logon servers to the site domain manually.

Caution  If you want to use the Automatically Configure Workstation Logon Scripts option (which must be configured after installing the site) on the site server domain, you must select the Automatically Detect Logon Servers option. Or you must select Use All Detected Servers for the site server domain after the site installation has completed. If a LAN Manager or Windows NT domain has the Use Specified Servers setting selected, the Site Configuration Manager will not set up the logon scripts for that domain.

If the site will have primarily only NetWare domains (besides the site server's Windows NT domain), you can select either Use Detected Servers or Use Specified Servers. If you have enabled Automatically Configure Workstation Logon Scripts, the Site Configuration Manager will always set up the logon scripts on the file servers for a NetWare domain.

For more information about adding logon servers to domains in a site, see the SMS Administrator's Guide.


Installing the Central Site

When installing the SMS system, you need to set up the Central Site first.

The Central Site is a primary site where all other sites in the SMS system report their inventory and events. At the Central Site, you can manage software and view the inventory for any client at any site in the SMS system. The Central Site is a primary site that has no sites above it.

To set up the Central Site, you follow the same steps used for setting up a primary site--except that all other sites must report to the Central Site or one of the Central Site's subsites.

Creating a Primary Site


Preparing Clients for SMS

SMS can install and maintain SMS components on all clients in supported domains. The Client Setup program, which runs in the SMSLS logon script for clients running Windows NT and LAN Manager, installs, configures, and maintains the SMS components on the client. On clients, the Client Setup program installs the SMS client files in the MS\SMS directory on the disk drive containing the most free space.

To prepare a client before adding it to the SMS system

1.	Make sure that the computer meets the system requirements.

For information about the system requirements for installing and running the SMS components on a client, see "Before You Begin" in the SMS Administrator's Guide.

2.	Make sure that the date and time is synchronized with the site server of the site where the client will be added to the SMS computer inventory.

For computers running LAN Manager and Windows NT, use the following command to set each client's time to the site server's time:

net time \\siteserver /set

For NetWare clients, the time on the computer is changed to the time on the server where the user has logged on. Make sure that the time on the server matches the time on the site server.

You should ensure that the times on the clients are current because the accuracy of the dates and times reported by SMS components for the client's inventory information is affected by the date and time set on the computers running the SMS components. Run Command On Workstation jobs are also affected by the time set on the client.


Preparing a Site for Macintosh Support

The SMS system can include Macintosh clients in the SMS computer inventory. To enable Macintosh support at a site, you must install Windows NT Server Services for Macintosh on the site server. Then, you must install the Macintosh components on the site server in the site where you want Macintosh support, using the SMS Setup program (by default, the Macintosh components are not installed).

By installing Windows NT Server Services for Macintosh on other Windows NT Server computers in an SMS domain, you enable those servers to provide logon server support to Macintosh clients. At every SMS domain, SMS will automatically install an SMS logon server volume on all Windows NT Server computers that have the File Service for Macintosh service installed and running.

Once SMS has set up Macintosh support on a Windows NT Server computer running the File Service for Macintosh service, Macintosh clients can be added to the SMS system. For information about adding Macintosh clients to a site, see the SMS Administrator's Guide.

For a list of all components installed on Macintosh clients, see the SMS Administrator's Guide.

To prepare a site to support Macintosh clients

1.	Install Windows NT Server Services for Macintosh on the site server in the site where you want to add Macintosh support.

For more information about installing Services for Macintosh, see the Windows NT Server Services for Macintosh documentation.

2.	Make sure that the Macintosh client components have been installed at the site.

You can use the SMS Setup program to install the Macintosh client components at the site.

3.	On the Windows NT Server computers where you want to add Macintosh support, make sure that the File Service for Macintosh service is started.

For more information about starting the File Service for Macintosh service, see the Windows NT Server Services for Macintosh documentation.

4.	In the Windows NT domain containing the Services for Macintosh server, create user accounts to be used at the Macintosh clients you want to include in the SMS system.


Setting Up Accounts for SMS

All SMS services at the site run in the context of a user account. This user account is called the SMS Service Account. Each site has an SMS Service Account.

At a site, the SMS Service Account is used by the SMS services to access servers in the site server domain and in all other domains that are added to the site. When you add a domain to a site, you should ensure that the SMS Service Account has access to that domain. How you set up access for the SMS Service Account depends on the type of domain: Windows NT, LAN Manager, or NetWare.

You can configure a site to use an SMS Service Account that is a local domain account or a trusted domain account:

Local Domain Account

Trusted Domain Account

You specify the SMS Service Account when you first install a site. After a site is installed, you can change the SMS Service Account that a site uses. To change the SMS Service Account, you can use either the SMS Setup program or the Site Properties dialog box in the SMS Administrator.

When you first install a primary site, you should create the SMS Service Account for use in the site server domain before you start the SMS Setup program. For a secondary site, you should create the SMS Service Account for use in the site server domain for the secondary site before you start the secondary site installation using the SMS Administrator.

When you add a new domain to a site, the SMS Service Account must have access to that domain.


Local Domain Account

A user account in the domain where the SMS services are installed. When a site contains multiple domains, the Site Configuration Manager and Maintenance Manager services access logon servers in a domain using the user account from that domain.

For example, if you specify SMSAccount as the site's SMS service account, the SMS services will run using the SMSAccount in the site server domain. If a new Windows NT domain is added to the site, the Inventory Agent and Package Command Manager services run on that domain's logon servers using the SMSAccount within that domain. In addition, the Site Configuration Manager service and the Maintenance Manager will use the SMSAccount at the added domain to access and maintain the domain's logon servers.

SMS Service Account in Windows NT Domains

If you add a LAN Manager domain, the Site Configuration Manager and Maintenance Manager will use the SMSAccount in that domain to access and maintain the domain's logon servers. The Inventory Agent service is installed using the SMSAccount in that domain.

SMS Service Account in LAN Manager Domains

If you add a NetWare domain, the Site Configuration Manager and Maintenance Manager will use the SMSAccount at each server in the domain to access and maintain the domain's logon servers.

SMS Service Account in NetWare Domains


Trusted Domain Account

A user account from a trusted domain. When a site contains multiple Windows NT domains, the Site Configuration Manager and Maintenance Manager services access logon servers in those domains using the user account from the trusted domain.

All Windows NT domains in the site (including the site server domain) must trust the domain specified by the SMS Service Account (this means that even if the equivalent SMS Service Account exists in the local domain, that local account won't be used--unless the domain specified by the SMS Service Account is the local domain itself).

At LAN Manager and NetWare domains, the local domain accounts are used. The domain specified by the SMS Service Account is only used for Windows NT domains. If a domain is specified for the SMS Service Account, the domain is ignored for LAN Manager version 2.x and NetWare domains.

For example, if you specify MASTERDOM\SMSAccount as the site's SMS Service Account, a Windows NT domain that gets added to the site uses the account SMSAccount from the trusted domain (when you install a site, you are implicitly adding the site server domain to site). In addition, the Site Configuration Manager service and the Maintenance Manager will use the trusted account at the added Windows NT domain to access and maintain the domain's logon servers. At the added domain, the SMS Inventory Agent and Package Command Manager services are installed on the domain's logon servers using the trusted domain account.

If you add a LAN Manager domain, the Site Configuration Manager and Maintenance Manager will use the SMSAccount at that domain to access and maintain the domain's logon servers. The Inventory Agent service is installed using the SMSAccount at that domain.

If you add a NetWare domain, the Site Configuration Manager and Maintenance Manager will use the SMSAccount at each server in the domain to access and maintain the domain's logon servers.


Service Account on Windows NT Domains

SMS Service Account in Windows NT Domains

When you add a Windows NT domain to a site, the SMS Service Account must have the following privileges in that domain:

Administrative privileges in the domain (must be a member of Administrators local group)

The Log On As A Service right

To manage the SMS services and SMS shares on the logon servers in a Windows NT domain, the SMS Service Account must have administrator permissions (be a member of the Administrators local group) and the Log On As A Service right in that domain.

You can configure a site to use an SMS Service Account that is a local domain account or a trusted domain account. How you set up the SMS Service Account in the Windows NT domains at the site depends on which type of user account you specify.

Setting Up a Local Domain SMS Service Account in a Windows NT Domain

Setting Up a Trusted SMS Service Account in a Windows NT Domain


Creating a Local Domain Service Account on a Windows NT Domain

Setting Up a Local Domain SMS Service Account in a Windows NT Domain

1.	Create a user account for the SMS Service Account in the Windows NT domain that you want to add to the SMS system.

For more information about creating user accounts in a Windows NT domain, see the Windows NT Server documentation.

Caution  If you plan to add a NetWare domain to the site, make sure that you do not use a password that is the same as the user account name. NetWare servers can be configured to not allow user accounts to have passwords that are the same as the user account name.

2.	Add the user account to the Administrators local group.

Optionally, you can add the user account to a global group that is a member of the Administrators local group.

3.	Grant the Log On As A Service right to the user account.

For more information about managing the user rights policy, see the Microsoft Windows NT Server System Guide.


Setting Up a Trusted Service Account on a Windows NT Domain

Setting Up a Trusted SMS Service Account in a Windows NT Domain

1.	Make sure that the Windows NT domain where you want to set up the trusted SMS Service Account trusts the Windows NT domain that contains the trusted SMS Service Account.

2.	Make sure that you have created the trusted SMS Service Account in the trusted domain.

3.	Add the trusted SMS Service Account to the Administrators local group in the domain where you want to set up the trusted SMS Service Account.

4.	Grant the Log On As A Service right to the trusted SMS Service Account.

If a Windows NT domain contains both Windows NT Server computers and LAN Manager version 2.x servers, you must follow the domain user account setup for the Local Domain Account. In addition, you must add the domain's SMS Service Account to the Domain Admins global group (LAN Manager version 2.x servers recognize only Windows NT global groups--not local groups). This lets the SMS services administer both the Windows NT and LAN Manager logon servers in the domain. If you specified a Trusted Domain Account as the SMS Service Account, follow the domain user account setup steps for the Trusted Domain Account.

For more information about Windows NT domains, user accounts, and network security, see the Microsoft Windows NT Server Concepts and Planning Guide.


Service Account on LAN Manager Domains

SMS Service Account in LAN Manager Domains

In a LAN Manager version 2.x domain, you must create a user account that has the same user name and password as the SMS Service Account and add the account to the ADMINS group. This will enable the SMS Service Account to administer all logon servers in the domain.


Service Account on NetWare Domains

SMS Service Account in NetWare Domains

At each NetWare server you want to include in the NetWare domain, make sure that the SMS Service Account for the site has all rights to all volumes.

In order to install and maintain the SMS components on the NetWare logon servers, you must create a user account with the same user name and password as the SMS Service Account. On each NetWare server in the domain, this account must have SUPERVISOR privilege and must have all permissions for all the volumes. All permissions for all volumes is required because the SMS Site Configuration Manager searches for the volume with the most available space and installs the SMS logon server components on that volume.


Synchronizing Time and Running SMS Across Time Zones

SMS uses times and dates for scheduling jobs in the system, reporting system status, and reporting computer inventory. The SMS system is designed to work efficiently across time zones; however, the accuracy of the dates and times reported by SMS components for inventory information and events is affected by the date and time set on the computers running the SMS components.

For example, if you run the Inventory Agent on a client, the Inventory Agent reports the Last Hardware Scan attribute in the Workstation Status group using the local time on the client. If the date and time on the client are not accurate (the time or date is wrong), an inaccurate date is reported for the Last Hardware Scan attribute.

To ensure that SMS reports information and performs actions using accurate times, you should make sure that all computers that handle the job have the times and dates that are current. For information about the computers involved in a job, see the SMS Administrator's Guide.


Installing Network Monitor on a Windows for Workgroups Client

Installing Network Monitor on a Windows for Workgroups 3.1x Client

You can install Network Monitor on a Windows for Workgroups computer. When running Network Monitor on Windows for Workgroups, the following options are unavailable:

You cannot connect to the Network Monitor Agent and capture remotely.

You cannot display Performance Monitor from within Network Monitor.

Windows NT-specific features, such as Event Logging, are unavailable.

To install Network Monitor on a Windows for Workgroups computer

1.	Insert the SMS CD-ROM into the computer's CD-ROM drive, switch to the CD-ROM drive, change directory to the NMWFW\DISK1 directory, and type the setup command.

The Network Monitor Setup dialog box appears.

2.	Follow the Setup instructions on the screen.


Completing the Setup for Network Monitor

Before using Network Monitor to capture data, you must manually install the Network Monitor Agent device driver. Until this driver is installed, you can use Network Monitor only to open capture files.

To install the Network Monitor device driver

1.	From the Windows NT Program Manager, open the Main program group, and click Control Panel icon.

2.	Click Network icon.

The Network Settings dialog box appears.

3.	Click Add Software.

The Add Network Software dialog box appears.

4.	In the Network Software box, select Network Monitor Agent.

5.	Click Continue.

The Network Settings dialog box reappears.

6.	Click OK.

The Network Settings Change message box appears, reminding you to restart your computer for the changes to take effect.

7.	To restart your computer, click Restart Now.


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

Ad Hoc query

Address

alert

Alerter

APPCTL

Applications Manager

Applications Manager database

APPSTART

architecture

attribute

audited software

C

D

E

G

H

I

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

C

Central Site

child site

clause

client

command

conventional memory

CRC-CCITT

current site

D

E

G

H

I

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

C

D

database server

default servers machine group

Delta-MIF

Despooler

distribution server

domain

E

G

H

I

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

C

D

E

expression

G

H

I

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

C

D

E

G

group

H

I

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

C

D

E

G

H

helper servers

hit count

I

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

C

D

E

G

H

I

identification group

installation

installation script

instance (inventory/query)

inventory

Inventory Agent

Inventory Data Loader

inventory frequency

Inventory Processor

inventory rule

J

L

M

N

O

P

Q

R

S

T

W


 Glossary

A

C

D

E

G

H

I

J

job

L

M

N

O

P

R

Q

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

LAN Sender

logical operator

logon server

M

N

O

P

R

Q

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

machine group

Maintenance Manager

Management Information Format

mandatory package

N

O

P

Q

R

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

named pipes

network application

Network Monitor

O

P

Q

R

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

object

optional package

Outboxes

P

Q

R

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

P

package

package command

Package Command Manager

package definition file (PDF)

package distribution

package source directory

parent site

primary site

program group

Program Group Control

program item

promiscuous mode

Q

R

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

P

Q

query

query criteria

query format

Query Results window

R

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

P

Q

R

RAS Sender

relational operator

Remote Control Agent

remote site

remote troubleshooting utilities

Remove Package From Server job

repeating job

Run Command On Workstation job

S

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

P

Q

R

S

Scheduler

secondary site

send

send request file

Sender

Share Package On Server job

site

site code

Site Configuration Manager

site control file

site database

site group

Site Reporter

site server

SMS Administrator

SMS client

SMS Site Hierarchy Manager service

SNA Receiver

SNA Sender

subclause

subsite

system job

T

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

P

Q

R

S

T

target clients

target sites

trigger

W


 Glossary

A

C

D

E

G

H

I

J

L

M

N

O

P

Q

R

S

T

W

Workgroup


 Glossary

A

Ad Hoc query

Address

alert

Alerter

APPCTL

Applications Manager

Applications Manager database

APPSTART

architecture

attribute

audited software

C

Central Site

child site

clause

client

command

conventional memory

CRC-CCITT

current site

D

database server

default servers machine group

Delta-MIF

Despooler

distribution server

domain

E

expression

G

group

H

helper servers

hit count

I

identification group

installation

installation script

instance (inventory/query)

inventory

Inventory Agent

Inventory Data Loader

inventory frequency

Inventory Processor

inventory rule

J

job

L

LAN Sender

logical operator

logon server

M

machine group

Maintenance Manager

Management Information Format

mandatory package

N

named pipes

network application

Network Monitor

O

object

optional package

Outboxes

P

package

package command

Package Command Manager

package definition file (PDF)

package distribution

package source directory

parent site

primary site

program group

Program Group Control

program item

promiscuous mode

Q

query

query criteria

query format

Query Results window

R

RAS Sender

relational operator

Remote Control Agent

remote site

remote troubleshooting utilities

Remove Package From Server job

repeating job

Run Command On Workstation job

S

Scheduler

secondary site

send

send request file

Sender

Share Package On Server job

site

site code

Site Configuration Manager

site control file

site database

site group

Site Reporter

site server

SMS Administrator

SMS client

SMS Site Hierarchy Manager service

SNA Receiver

SNA Sender

subclause

subsite

system job

T

target clients

target sites

trigger

W

Workgroup


Ad Hoc query

A query created for immediate execution. Ad Hoc queries are not stored in the site database, do not affect any queries in the database, and are not displayed in the Queries window. An Ad Hoc query can be created from scratch or by modifying an existing query.


Address

An address provides specific information for connecting to a target site, so that instructions and data can be sent to that site.


alert

A set of actions that depend on the results of a specified query. An alert defines how the SMS system should detect a specific condition, using a query, and what actions it should take when that condition is detected. For example, an alert can log an SMS event, execute a command from the computer where the Alerter is installed, and send a message to a computer or user on the local network.

See Also

Alerter


Alerter Service
Alerter

An SMS component (within the SMS Executive service) that processes alerts by evaluating alert conditions and triggering alert actions when the conditions are true. The Alerter also monitors the database for new alerts and any changes to existing alerts.

See Also

alert


APPCTL

A program that is part of the Program Group Control feature on SMS clients. This SMS program creates the assigned program groups in the client's Program Manager.


Applications Manager Service
Applications Manager

An SMS component (within the SMS Executive service) that communicates package and program group configuration information from the site database to the other components at that site and to the sites below it.


Applications Manager database

A set of configuration files used by the Program Group Control feature at Windows-based clients. The Applications Manager is installed on all logon servers. At Windows-based clients, the APPCTL program connects to a logon server and collects all program groups assigned to the user logged on at that client. Then it rebuilds the program groups in the Program Manager on the client.


APPSTART

An SMS program that is part of the Program Group Control feature on SMS clients. APPSTART lets users start and run network applications that are assigned to them. When a user launches an assigned network application, APPSTART automatically makes the connection to the appropriate server and, along with APPCTL, sets up the proper execution environment for the application.


architecture

A structure for recording inventory for a specific type of object. An architecture defines the structure for a set of objects. Each object is composed of groups that contain attributes.

See Also

attribute

object


attribute

A property of a group. Each attribute is assigned a value. The set of attribute values for a group comprises the inventory for the component.


audited software

A set of software items defined by the administrator. Each software item is defined by the set of files (and their attributes) that the administrator wants to use to identify that item. At clients, the user can run the Software Audit program, which scans for these items and reports the items that were found.


Central Site

The primary site that stores system-wide information and manages all sites, with any number of subsites beneath it. The Central Site is a primary site to which all other sites in the SMS system report their inventory and events. When you build a site hierarchy, child sites report their inventory to their parent sites, the parent sites report their inventory and their child sites' inventory to their parent sites, and so on up to the Central Site. At the Central Site, the administrator can manage software and view the inventory for any computer at any site in the SMS system. The Central Site is a primary site that has no sites above it.


child site

A site that has a parent site. A child site can be a primary site that has been attached to another primary site. Or a child site can be a secondary site (a secondary site is always the child site of the primary site that created the secondary site).


clause

The combination of an expression (or subclause) and its adjacent logical operator, in a query.

See Also

subclause


client

A computer connected to a network and running network client software.


command (package command)

A command line in Run Command On Workstation jobs that executes a program on target clients. A command can be used to install a package (such as an application like Microsoft Excel) or to just run a program (such as a virus scan utility).


conventional memory

The lower 640K (or less) of main memory. The remaining portion of main memory, up to 1 MB, is called upper memory. Beyond 1 MB, an MS-DOS-based computer's memory is either expanded memory or extended memory. Memory map does not map beyond upper memory.


CRC-CCITT

A standard algorithm that calculates the sum of all values stored at a specific set of bytes and compares the sum to a specified value. Unlike CHECKSUM, CRC-CCITT takes into account the sequence of the summed bytes, making it a more reliable tool for identifying files.


current site

The primary site whose database you have logged in to with the SMS Administrator. In the Sites window of the SMS Administrator, the current site is represented as a primary site (with a globe icon).


database server

A computer running Microsoft SQL Server on which the SMS site database is installed.


Despooler
default servers machine group

A special machine group that processes jobs at target sites. The default servers machine group specifies the servers where package source directories are installed:

If Default Servers is selected as the target for distribution servers.

If a target site does not contain any of the servers specified by Put On New Distribution Servers.

At each site, the SMS system creates the default servers machine group. By default, the default servers machine group contains only the site server.


Delta-MIF File
Delta-MIF

A binary file with information stored in the Management Information Format and used by the SMS services to add information to the site database.


Despooler

An SMS component (within the SMS Executive) that watches for despooler instruction files and compressed packages created by the Scheduler (the instructions and packages can come from the local site or from another site). The Despooler reads the instruction file and uses the instructions to decompress the package files. For example, it decompresses inventory files so they can be processed by the Inventory Data Loader, which then updates the database.


distribution server

A server on which the source directory of a sent package is stored and made available to the target clients. These servers install the package on clients. They are called distribution servers because they have a distributed copy of the package's source directory.


domain

A set of servers and clients that are grouped to create an administrative unit within a site.

A domain, for Windows NT and LAN Manager networks, is an administrative unit based on a database of security and user account information shared by a set of servers. For servers running Microsoft LAN Manager and Microsoft Windows NT Server, a domain supplies centralized security and user-account information for a group of servers. When a user at a client running LAN Manager or Windows NT logs on to a domain, that client participates in that domain while that user is logged on.

For NetWare networks, a domain is based on a group of NetWare servers on a LAN. The servers in a NetWare domain are specified when the domain is added to a site.


expression

An instruction to search for objects that have a specified relationship to a specified value for a specified attribute.

An expression compares a specified value against a specific attribute, using an operator (such as is equal to or is like). An expression is made up of an attribute, an operator, and a value.


Group (Definition)
group

A set of expressions that are explicitly combined with parentheses. Making a set of expressions a group ensures that the group's expressions are treated as a single entity. Groups have a higher operator precedence than the logical operators (AND and OR). Groups can be used to help make complex queries easier to read.


helper servers

A helper server is a logon server running SMS components that have been moved from the site server (Scheduler, Despooler, and Inventory Data Loader) or simply installed to those servers (the Sender components).


Hit Count
hit count (query result)

The number of objects that the SMS system has found in the site database, according to the criteria specified by a query.


identification group

A collection of attributes that uniquely identify a computer.


installation

A process that includes creating a Run Command On Workstation job, which enables the administrator to run a package command line at target clients. The command line can start an executable file, batch file, or Microsoft Test script to install a package or simply to run a command.


installation script

A file of script commands that a shell program (for example, Microsoft Test) uses to automate a setup program.


instance (inventory/query)

A single occurrence of a group in the inventory for an object.

Some groups (such as Disk Drives and Software Packages) can have multiple instances on a single client. For example, a client can have multiple instances of the group Software Packages--one for each package installed (such as a Microsoft Excel version 4.0 package, Microsoft Word version 2.0 package, and so on).

Other groups logically or physically can have only a single instance (such as Identification and Mouse).


inventory

The information that SMS collects for each computer on the network. The inventory includes hardware (CPU, BIOS, drive information, and so on), software (specified package), and collected files.


INVENTORY_AGENT Service
Inventory Agent

A component that scans a computer for hardware and software inventory and reports the inventory to the SMS system.

On clients, the Inventory Agent is a program that is run from logon servers. When a user runs the SMSLS batch file, the Inventory Agent is executed within the SMSLS batch file.

On computers running Windows NT Server and LAN Manager, the Inventory Agent is a service (SMS Inventory Agent for Windows NT and SMS Inventory Agent for OS/2) that reports inventory every 24 hours. For NetWare servers, the Maintenance Manager reports inventory on NetWare logon servers.


INVENTORY_DATA_LOADER
Inventory Data Loader

An SMS component (within the SMS Executive service) that monitors the SMS system for Delta-MIFs (which store information about computer inventory, job status, and events) used to update the database.


inventory frequency

The interval at which the Inventory Agent scans a computer for inventory. Each site has settings for inventory frequency. A site's inventory frequency settings apply to all clients in the site.

The inventory frequency is the time between the last scan and current time when the Inventory Agent program is invoked, either from a logon script or explicitly from the command line. The Inventory Agent program scans for two types of inventory: hardware and software. The administrator can set the frequency independently for both hardware and software scanning.


INVENTORY_PROCESSOR Service
Inventory Processor

An SMS component (within the SMS Executive service) that collects all the raw files created by the Inventory Agent and creates a history file for each computer (an image of the last RAW file). When new RAW files are ready, it compares them with the history files and writes out changes to inventory files called Delta-MIFs. The Inventory Processor also converts MIFs in the ISVMIF directory into Delta-MIFs.


inventory rule

The set of files used to identify the package. To detect each file, specify its attributes (such as file date, file size, CRC, and so on). The SMS inventory system uses this criteria to identify a software package on individual computers and to include it in the computer inventory.


job

An object that stores instructions for actions that the system performs. For example, the administrator can define a Run Command On Workstation job to install a package on clients or SMS can create a job to maintain part of the system.


LAN Sender

See Sender


Logical Operator (Definition)
logical operator

The connector between two expressions, two subclauses, or a combination of an expression and a subclause. A logical operator defines the relationship between two adjacent expressions or subclauses.

There are two logical operators: AND and OR. AND takes precedence over OR.


logon server

A server added to the computer inventory at a site. A logon server supports configuration, inventory collection, package installation, and network applications for the SMS clients in its domain. A site server is automatically added as a logon server.


machine group

An alias for a group of machines. A machine group is a list of the computers. The administrator can use a machine group as a shortcut for referring to multiple computers--instead of having to refer to each computer in a group individually, the computers can be included in a machine group and referred to by the machine group name.

Machine groups can be used to specify the job targets and distribution servers for Run Command On Workstation jobs and to specify distribution servers for Share Package On Server jobs.


Maintenance Manager

An SMS component (within the SMS Executive service) that installs and maintains the SMS components at the logon servers in a site. It replicates client components and configuration information to logon servers within the site and collects inventory and status information.


Management Information Format (MIF)
Management Information Format

A standard for accessing desktop computer components (hardware and software) across multiple platforms. A management information file (MIF) is an ASCII file that contains information about a computer component. A MIF is a description of the component that is available to other applications through a standard management interface.


mandatory package

A package command that must be executed within the Package Command Manager at an SMS client before the user can continue working on their computer.

See Also

optional package


named pipes

An interprocess communication (IPC) method used to transfer data between separate processes, usually on separate computers. A system administrator can set permissions on named pipes.


network application

A computer program defined within a package and run over the network by individual users at clients. In the SMS system, network applications are defined as program items within a package. The administrator can assemble program items from any packages into program groups. These program groups are then assigned to LAN Manager user groups, Windows NT Server global groups, or NetWare user groups. Wherever these users log on, they will see a program group that contains their assigned network applications in the Program Manager on the local client.


Network Monitor

An SMS network diagnostic tool that captures network traffic and provides a graphical display of network activity. Network Monitor can capture traffic from, to, or between specific computers. Additionally, using the Network Monitor Agent service (provided with Windows NT Server and Windows NT Workstation version 3.5), Network Monitor can capture from remote subnets.

Using filters, Network Monitor can focus on specific types of network traffic. For example, you can use the SMS Administrator's Personal Computer Properties window to preset Network Monitor to capture from a specific computer on startup. Network Monitor can also identify the top broadcasters on a network, generate traffic for testing and diagnostic purposes, and monitor specific frames on a network segment.


object

An item (whose structure is defined by its architecture) stored in the site inventory database. For example, a Macintosh computer is an object with the Personal Computer architecture.


optional package

A package command that can be executed by the user at any time (or not at all) from the Package Command Manager at an SMS client.

See Also

mandatory package


Outboxes

A set of directories where SMS services can put send request files, which contain instructions for transferring data and instructions to other sites. There is a separate Outbox for each type of Sender.


package

An SMS object that contains diverse information about software so that the software can be identified and installed.

A package is an object that defines software to the SMS system. To create a package, the administrator defines the files that comprise the software and the package's configuration and identification information. After creating a package, the SMS system can be used to install the package on clients, share the package so that it can be run from network servers, or maintain inventory on the package.


package command

A command line (within a package) that executes a program or runs an installation script that installs an application. A package can have multiple package commands defined. When the administrator uses a package in a Run Command On Workstation job, the administrator can choose the specific package command to run on the job's target computers.


Package Command Manager

An SMS program that runs package commands on SMS clients. The Package Command Manager lets users see the packages that are available and control the installation of optional packages, mandatory packages are automatically installed by the Package Command Manager.

There is a different version of the Package Command Manager for each supported operating system (MS-DOS, Windows version 3.1, and Windows NT). On logon servers running Windows NT Server, the Package Command Manager is installed as a service.


package definition file (PDF)

An ASCII text file that contains pre-defined Workstations, Sharing, and Inventory property settings for a package. When the administrator creates a new package, the administrator can use the Import command from the Package Properties dialog box to define the properties for the package, using a PDF. By importing a PDF, SMS uses the PDF's property definitions to enter the package properties. SMS includes PDFs for some of the most popular applications (such as Microsoft Excel).


package distribution

A type of action performed with a package. Distribution means placing a package on servers and making the package available from a shared directory.

For a Run Command On Workstation job, distribution installs the package's Workstation Source Directory on the specified distribution servers at the target sites, shares the directories on the network, and makes them available to the Package Command Manager.

For a Share Package On Server job, distribution installs the package's Sharing Source Directory on the specified servers, shares the directories on the network, and makes them available to users with the specified permissions. The package can be used as just a shared directory or as a network application.


package source directory

A shared directory (in the Central Site LAN) that contains a package's source files. For each package, one source directory can be specified for Workstations properties and another source directory for Sharing properties.


parent site

A primary site to which another site has been attached (that is, a primary site that has child sites beneath it in the site hierarchy). A parent site can have a primary or a secondary site attached to it.


primary site

A site that has its own SQL Server database to store the system, package, inventory, and status information for the site itself and the sites below it in the site hierarchy. It also has administrative tools that enable an administrator to directly manage the site and the sites below it in the site hierarchy.

A primary site must be installed from the SMS Setup CD-ROM. When a primary site is initially installed, it is a standalone Central Site. Once a primary site is installed, the administrator can use the SMS Administrator to integrate the new site (and any of its subsites) in the hierarchy of another SMS system.


Program Group (general)
program group (SMS program group)

A collection of program items within the Program Manager. The administrator creates program groups using program items defined by the Sharing properties of packages. From the packages, the administrator chooses the program items to include in the program group. The administrator then assigns program groups to LAN Manager user groups, NetWare user groups, and Windows NT global groups. Wherever these users log on, their assigned program groups appear in the Program Manager on the local computer. By double-clicking a program item, these users start the network application for that item.


Program Group Control

A set of programs (APPCTL and APPSTART) on computers running Windows version 3.1 and Windows NT that enable users to run network applications. The Program Group Control feature sets up and starts the network applications so that the applications can be run over the network from distribution servers.


Program Item
program item (package)

An object composed of an icon and the command line for running a network application. A program item also contains other details about how the network application should be started (such as running the application minimized). Program items are displayed to the user as icons contained within a program group that is assigned to a user group in which that user is a member. The user can use the program items to start network applications. You define a package's program items in the package's Sharing properties.


promiscuous mode

A state in which a network adapter card detects all the frames that pass over the network.


query

An SMS object that contains the criteria used to find objects in the site database. A query defines and stores the criteria used to identify the objects to find. When a query is executed, it searches the inventory for the objects that match the query's criteria. The results are displayed in a Query Results window.


query criteria

The set of instructions used to search for the objects to find. When a query is executed, the SMS system finds the objects that satisfy the query's criteria and displays them in a Query Results window.


Query Format (Definition)
query format

An object that stores the format used to display the results of a query. A query result format is used to select which attributes to display for the list of objects returned in the Query Results window. A format is specific to a single architecture. For example, a query format defined for an Employee architecture cannot be used to display computers, which may have a Personal Computer architecture.


Query Results window

A window that displays the results of a query  using the specified query result format. A Query Results window displays all the objects that match the query's criteria.

A query can be modified and re-executed by choosing the query bar (by double-clicking it). Note that any modifications made to the query from a Query Results window do not affect the original query (which is stored in the database).


RAS Sender

See Sender.


Relational Operator
relational operator (query)

The part of an expression (such as is equal to or is like) that defines how the specified value should be compared with the actual value stored for the specified attribute.

See Also

expression


Remote Control Agent

A program (either USERTSR.EXE or USERIPX.EXE) that a client must be running in order to be diagnosed or controlled by the administrator with the remote troubleshooting utilities.


remote site

A site other than the current one.


remote troubleshooting utilities

A set of tools that allow direct control and monitoring of remote clients running MS-DOS, Windows version 3.1, and Windows for Workgroups version 3.11.


Remove Package From Server job (Definition)
Remove Package From Server job

A job that removes a package installed on servers.

A Remove Package From Server job removes the compressed package stored at the site server and the package source directory installed on specific distribution servers.


Repeating job (Definition)
repeating job

A job with its Repeat option set to a time interval. (The Repeat option is set in the Job Schedule dialog box.) The SMS system measures the interval starting from the Start After time. For example, a job with a Repeat setting of Daily and a Start After setting of 8/1/93 10:00 PM will have its second repeat job activated after 8/2/93 10:00 PM, the third at 8/3/93 10:00 PM, and so on.


Run Command On Workstation job (Definition)
Run Command On Workstation job

A job that runs a package command on target clients.

A Run Command On Workstation job sends the source directory specified by the package's Workstations properties to target sites (and places them on specified distribution servers) and makes the package command available at target clients.


Scheduler

An SMS component (within the SMS Executive service) that detects pending jobs and creates auxiliary files that allow jobs to be processed. This includes jobs initiated by a user, such as a Run Command On Workstation job, as well as system jobs.


secondary site

A site that has no SQL Server database to store its system, package, inventory, and status information. Instead, it forwards inventory and status information to its primary site for processing and storage. It also does not have administrative tools for direct administration of the site--a secondary site must be administered through one of its parent sites (a primary site above the secondary site).

A secondary site is installed by using the SMS Administrator at the primary site under which the new secondary site will be placed. A secondary site can only be created and configured from an immediate primary site. A secondary site cannot have subsites beneath it.


send

A type of action performed by a job when handling a package. Sending is the method used by the SMS system to transfer data and instructions for jobs between sites (limited sending also occurs within a site). When a job is activated by the Scheduler, the Scheduler compresses the data or instructions needed to complete the job and writes a send request for a Sender to transfer the data or instructions. The Sender transfers the data or instructions to the target site, where the Despooler handles or routes the data or instructions to the SMS services required to complete the job at that site.


send request file

A file with instructions that the Sender uses to connect to a specified site and to transfer the specified data to the site.


Sender Service
Sender

An SMS component (within the SMS Executive service) that is used by the SMS system to send instructions and data from one site to another (such as reporting inventory information or installing software on clients at another site). There are three types of Senders: LAN Sender, RAS Sender, and SNA Sender. The RAS Sender and SNA Sender are divided into subtypes to support different means of communication.

SMS supplies three RAS Senders (MS_ASYNC_RAS_SENDER, MS_ISDN_RAS_SENDER, and MS_X25_RAS_SENDER) and two SNA Senders (MS_BATCH_SNA_SENDER and MS_INTER_SNA_SENDER).


Share Package On Server job (Definition)
Share Package On Server job

A job that puts files on servers and shares them, giving users access to the files at each target site. A Share Package On Server job installs the package's Sharing source directory on target servers and shares that directory using the specified share name and permissions.

This job can distribute and share a directory on a set of servers in a site, giving users access to a copy of the source directory files. Or it can install a package so that the applications it contains can be set up as network applications, letting assigned users run the package's programs over the network.


    site

An SMS object that logically groups a set of domains into an administrative unit for managing computers. Each site has a site server.

The domains to be included in a site are selected when the site is configured.

There are two types of sites: primary sites and secondary sites.

When setting up an SMS system, there must be at least one primary site that serves as a Central Site. Once the Central Site is installed, a hierarchy of primary sites can be created beneath the Central Site.


Site Code (Definition)
site code

A three-character code that the SMS system uses to identify a site. Used as part of the addressing information for communicating between sites, the code for any site must be unique across the SMS system.


SITE_CONFIG_MANAGER Service
Site Configuration Manager

An SMS service that installs and maintains the SMS services at the site server and the logon servers in the site. The Site Configuration Manager monitors all the SMS services on the site server and all the logon servers to ensure that those servers are active and that the SMS services are started.


site control file

An ASCII text file that contains the configuration for a site.

When a site is first created or the site properties are modified, the Site Hierarchy Manager creates a site control file with the proposed configuration for the site. The Site Configuration Manager reads this file to configure the site.

A site control file is also used by the Site Configuration Manager to report the current site configuration to the Site Hierarchy Manager, which uses the file to update the site configuration information stored in the site database.


site database

A Microsoft SQL Server database that stores system information (configuration and status) and the software and hardware inventory at a primary site. Each primary site must have a site database.


site group

An alias for a group of sites--that is, a shortcut for referring to multiple sites. Instead of referring to each site individually, the sites can be included in a site group and referred to by the site group name. A site group can be used to limit a job to the sites in the site group. A site group can also be used to narrow down a query.


Site Reporter

An SMS component (within the SMS Executive service), at child site, that detects a queue of Delta-MIFs containing inventory, job status, or event information, and creates a mini-job to send these files on to the parent site. The Site Reporter exists at both primary sites and secondary sites.


site server

A computer that contains the SMS components needed to monitor and manage the site, its domains, and its computers. Each site must have a site server.


SMS Administrator

The program used to administer the SMS system.


SMS client

A computer included in the SMS computer inventory. An SMS client is included in the computer inventory, receives packages for installation, and can run network applications. In addition, the SMS system assigns the client an ID that is unique across the whole SMS system.


SMS Site Hierarchy Manager service

An SMS service that monitors the site database for changes to the configuration of that site or its direct secondary sites. If the SMS Hierarchy Manager detects a change in a site's proposed configuration, it creates a site control file (which contains all proposed configurations for a site) and sends it to the site. The SMS Hierarchy Manager exists only on primary sites.


SNA Receiver

An SMS service that processes instructions and data sent by an SNA Sender. When you install an SNA Sender on a computer, the SNA Receiver is automatically installed with it.


SNA Sender

See Sender.


Subclause (Definition)
subclause (query)

A set of expressions that can be logically treated as a single expression. A subclause can be explicitly specified as a group. A group is surrounded by parentheses.


subsite

A site under another site in the site hierarchy.


system job

A job that transfers system instructions to other sites. System jobs are used to maintain a site or report event, status, or inventory data to other sites.


Target Workstations
target clients

The computers where a package is installed by a Run Command On Workstation job. The target clients can be specified as a machine group, as the result of a query at the job's start time, or as all clients in the whole corporation, a site, or a domain.


target sites

The sites where a job sends a package or performs an action. For example, when creating a Run Command On Workstation job, the target sites are the sites where the target clients are located.


trigger

A condition that sets off an alert when the condition is true.

See Also

alert


workgroup

A logical grouping of computers for browsing network resources. Windows NT, Windows for Workgroups, and Workgroup Add-On for MS-DOS support workgroups.