An SMS site is a set of resources and site systems defined by
a list of subnets, such as an IP subnet or IPX network.
Resources and Resource Discovery
Resource discovery is integral to the operation of an SMS site. Most SMS
functions cannot be carried out until a client has been discovered and
installed. A resource is an object that can potentially be managed
by SMS. SMS recognizes a variety of objects as site resources. These include:
Computers, Routers, Hubs, Any object with an IP address, any Windows NT users
and user groups.
Discovery is the process of locating resources and collecting
information about them. When a resource is discovered, the discovery data
is passed in a discovery data record (DDR) to the site server and stored in
the site database. The resource can then be added to collections and, if they
are computers, they can be installed as clients.
Resources are discovered by SMS using a variety of methods. There are different
services and agents for each method, depending on the type of resource or the
method of discovery. These discovery methods are configured by the administrator
and< in combination< provides the means for locating and collecting information
about most objects in the network.
Supported Clients
SMS clients are computers that have SMS client software installed. A computer
may be stored in the discovery database and not be installed as a client. The
following cient computers are supported by SMS: Windows NT Workstation and
Server 3.51 and 4.0, Windows 3.1x, Windows 9x, and Windows 2000.
Client software and methods vary, but all SMS features are supported for all
client operating systems, except that 16-bit clients do not support a Network
Monitor agent or software metering.
Site Systems
Site systems are servers, Windows NT shares, or NetWare volumes that provide
specific functions in an SMS site. A single site system may actually be
assigned multiple functions. The various site systems are:
Site Server
The site server is a computer running NT 4.0 SP4 on which SMS is installed.
It hosts the SMS components needed to manage the SMS site and often performs
multiple site system roles. Although it can carry out all site system roles
simultaneously, this configuration is generally not recommended, except in a
test environment. The site server computer must be a member of a domain. The
site server runs the following SMS services, and all the applicable threads
for the following services:
- SMS Executive. This is the main SMS service. It contains many threads, also called SMS components, to carry out specific SMS functions.
- SMS Site Component Manager. This service makes sure that the site server components are running as configured. It installs components initally and checks regularly to make sure they are running properly.
Component Server
A component server is a server that runs one or more of the SMS Executive
threads in order to lessen the processing burden on the site server, or to
provide duplicate threads. The site server is also listed as a component
server because it runs the SMS Executive service.
A component server is created by configuring SMS to run specific components
on another computer running NT Server 4.0 that is participating within the
SMS site. SMS automatically installs SMS Executive on the component server
and turns on the specific SMS components that have been moved to the
component server. The component server should be on the same LAN as the
site server b/c the SMS components will be accessing and moving files b/w
the two computers.
The main use for a component server is when a special communications method,
such as RAS, is required to communicate with another site. Installing RAS
on a component server and then running the communication component there
helps reduce the site server processing load.
Site Database Server
SQL Server is used to store and manage the site database. SQL Server can be
installed on a seperate computer running Windows NT Server, or it can be
installed on the same computer as SMS. The site database runs a special SMS
service called SMS SQL Monitor. This service is used to monitor the site
database in SQL Server, and it performs maitaince and cleanup of the site
database.
Logon Points
A logon point is the inital point of contact b/w the client computer and the
SMS environment. Effort has been made to reduce the amount of processing that
is performed by the logon point b/c logon points typically serve other
functions within an enterprise. When NT logon point is configured, an SMSlogon
directory is created and a Netlogon share is established. The logon point
provides clients with a site list from which they determine their site
assignments and a CAP list from which they find a client access point. In
addition, clients will copy a DDR to the logon point. This is done to provide
initial discovery data to the site.
A logon point is setup when either logon discovery or logon installation is
configured. In a NT environment, all domain controllers in a domain are
added as logon points. In a NetWare environment, you specify which servers
or NDS containers will be added as logon points.
Client Access Points (CAPs)
Client access points are the main interface for the client to the SMS system.
A client access point can be any NT Server or NetWare server. There will be at
least one CAP per site. The site server is initally configured to be a CAP,
however, once another CAP has been established, it is recommended to remove
this function from the site server. Generally, you do not want client
interaction directly with the site server.
Once a client determines to which site(s) it is assigned and determines which
CAP to use at that site, the SMS client software is installed and the client
DDR is written to the CAP. Recall that the DDR is also written to the logon
point. The CAP provides specific configuration instructions and files for
clients. The CAP is also the location at which the client will check for
advertisements of programs that can be run or installed.
When the client has completed either hardware or software inventory and created
an inventory data file, it writes this data to the CAP. In addition, any status
messaages originating from the client are also copied to the CAP. For example,
a status message may be generated when the client runs an advertised program.
Distribution Points
A distribution point is a server, or NetWare volume where package files are
stored. When a program is advertised by the site server, the advertisement
and program data is stored on the client access point. When the client accepts
the advertisement and attempts to run the program, the package instructions
list which distribution points the client can access to find the files required
to run the advertised program.
When a package is distributed, SMS searches the distribution point for the
drive with the most free disk space, and stores the data in the SSMPKGd$
folder and share. Each new attempt to store a package on a distribution point
may cause SMS to search for the drive with the most free space, so that
packages may be stored on multiple drives of a distribution point.
Alternately, the share name and location for a package can be configured
by the administrator.
Software Metering Servers
A software metering server runs a service that provides software metering
and license management. This computer must be running NT 4.0 and will
generally be a seperate computer from the site server. The software
metering server provides an intermediary point b/w the site server and client
computers. The site server copies licensing and metering configuration
information to the software metering server, and retrieves data. Client
computers check for configuration information and copy metering data to
the software metering server.
SMS Administrator Console Computer
The SMS Administrator console may be run on any computer running NT 4.0 that
can connect to the WMI component on either the site database server, or the
site server. In a site with several administrators, there will be several
SMS Administrator console computers accessing the site database.
The MMC with the SMS Administrator snap-in can be run on either NT4 workstation
or server. The SMS Administrator snap-in does not run on 9x machines. Typically
SMS Administrator consoles run on site administrators' desktop computers. In a
large site, there may be multiple site administrators with different areas of
responsibility, and therefore multiple SMS Administartor console computers.
SMS Site Hierarchies
An SMS hierchy can include multiple primary and secondary sites,
which are arranged in parent-child relationships. The major difference b/w
primary and secondary sites is that a secondary site does not maintain a
SQL Server database. It stores its site information at its parent site. A site
can be both a parent and a child site, if it meets the following definitions.
Parent Sites
A parent site is any SMS site with one or more child sites below it in the
heirchy.
- The central site is the top-level site in the hierarchy and must be a primary site.
- Any primary site that installs a secondary site below it becomes the parent site to that secondary site.
- A parent site can administer all child sites in its hierarchy.
- Because secondary sites do not maintain SQL databases, they cannot be parent sites.
Child Sites
- A primary site can be a child site to another primary site.
- All secondary sites are child sites.
- A child site has only one parent site.