Microsoft Systems Management Server
SNA Secondary Site Setup Help

The SNASETUP.EXE program enables you to complete a secondary site installation that uses the SNA Sender. The SNA Setup dialog box specifies the configuration information used to install the SNA Receiver service for setting up a secondary site across an SNA link.

Site Code

Installation Directory

Site Server Domain

Username

Password

Confirm Password

The SNASETUP.EXE program installs the SMS SNA Receiver and SMS Bootstrap services on the site server at the secondary site.

After you click OK in the SNA Setup dialog box, the SNASETUP.EXE program installs and starts the SNA Receiver and SMS Bootstrap services. These services wait for site installation instructions from the parent site where the secondary site was created. When the SMS Bootstrap service receives the instructions, it configures and starts the SMS Site Configuration Manager, which completes the secondary site's installation.


Site Code (SNA Setup dialog box)

Site Code

A three character code that the SMS system uses to identify the site.

The site code must match the site code that you specified as the Site Code for the site in the New Secondary Site dialog box.


Site Code
The site code must match the site code that you specified as the Site Code for the site in the New Secondary Site dialog box.


Site Server Domain (SNA Setup dialog box)

Site Server Domain

The name of the domain containing the site server for the secondary site.

The domain must match the domain that you specified as the Site Server Domain for the site in the New Secondary Site dialog box.


Site Server Domain
The domain must match the domain that you specified as the Site Server Domain for the site in the New Secondary Site dialog box.


Username (SNA Setup dialog box)

Username

The SMS Service Account at the secondary site. All SMS services at the site run in the specified user account context. Make sure that you have created an SMS Service Account for the SMS system in the site server domain at the secondary site.

The SMS Service Account must match the account that you specified as the Service Account for the site in the New Secondary Site dialog box.

Setting Up an SMS Service Account


Service Account
The SMS Service Account must match the account that you specified as the Service Account for the site in the New Secondary Site dialog box.


Password (SNA Setup dialog box)

Password

The password for the SMS Service Account.

The password must match the password that you specified for the SMS Service Account in the New Secondary Site dialog box.


Confirm Password
The password must match the password that you specified for the SMS Service Account in the New Secondary Site dialog box.


Confirm Password (SNA Setup dialog box)

Confirm Password

Verifies the password you specified in the Password box.


Installation Directory (SNA Setup dialog box)

Installation Directory

The directory in which to install the SMS components on the site server for the secondary site.

You must specify the full path where you want the SMS Site Configuration Manager to install the SMS root directory. The path must include the drive letter for a hard disk on the site server (for example, C:\SMS). If the directory does not exist, the SMS Site Configuration Manager will create the directory for you.

The Installation Directory must match the path that you specified as the Installation Directory for the site in the New Secondary Site dialog box.


Installation Directory
The Installation Directory must match the path that you specified as the Installation Directory for the site in the New Secondary Site dialog box.


SMS Service Account

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.

You specify the Service Account when you first install a site. For a secondary site, you specify the Service Account in the New Secondary Site dialog box.

When you install a secondary site, you should create the Service Account for use in the secondary site's site server domain before you start the secondary site installation using the SMS Administrator. The service account for the secondary site must match the account specified in the New Secondary Site dialog box.

An SMS Service Account can be a local domain account or a trusted domain account:

Local Domain Account

Trusted Domain Account

For information about creating an SMS Service Account on the site server domain, see Service Account on Windows NT Domains.


Local Domain Account

Is 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 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.

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.


Trusted Domain Account

Is 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 service account (this means that even if the equivalent service account exists in the local domain, that local account won't be used--unless the domain specified by the service account is the local domain itself).

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

For example, if you specify MASTERDOM\SMSAccount as the site's 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 to 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.


Setting Up an SMS Service Account on Windows NT Domains

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

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

The Log On As Service right

To manage the SMS services and SMS shares on the logon servers of 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 Service right on that domain.

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

Creating a Local Domain Service Account on a Windows NT Domain

Setting Up a Trusted Service Account on a Windows NT Domain


Creating a Local Domain Service Account on a Windows NT Domain

1.	Create a user account for the SMS service account on the Windows NT domain that you want to add to the SMS system.

For more information about creating user accounts on 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.

To assign the Log On As A Service user right to the SMS system user account, use the Windows NT User Manager for Domains tool.

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

1.	Make sure that the Windows NT domain where you want to set up the trusted service account trusts the Windows NT domain that contains the trusted service account.

2.	Make sure that you have created the trusted service account on the trusted domain.

3.	Add the trusted service account to the Administrators local group of the domain where you want to set up the trusted service account.

4.	Grant the Log On As A Service right to the trusted service account.

If a Windows NT domain contains both Windows NT Servers 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 system 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.


  Central Site

The primary site that stores system-wide information and manages all sites, with any number of sites 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.


    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.


  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.


  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 sites beneath it.


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.


  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.