To relieve the load on your primary or secondary site server, you might want SMS to perform some server tasks on computers other than the site server. To do so, you create site systems within a site. A site system is a server, share, or NetWare volume that provides functionality to the SMS site. SMS provides four types of site systems:
The roles assigned to a site system determine the functionality that it contributes. The site server itself is a site system. You can assign each SMS server one or more roles within the site. Due to the distributed nature of SMS, a role might exist only on the site server or on one or more servers within the site.
In SMS 2.0 documentation, references to a site system role refer to both a server and the type of task it performs. For example, a reference to a distribution point refers to a server that performs the distribution point role. The roles that you can assign to site systems other than the site server include:
| Client access point (CAP) | The client access point (CAP) role provides a communication point between the site server and clients. After SMS installs client software on a computer in a site (thereby making that computer an SMS client), the client contacts a CAP for management information from the site. Files, inventory information, and status information collected at the client computers are forwarded to the CAP, which also provides client agent configuration and setup files to client computers. Because CAPs provide communication among client computers and the site server, consider assigning this role to one or more site systems other than the site server to reduce the load on the site server. |
| Component server role | Any site system that runs the SMS Executive service component provides the component server role. A component server can run only selected threads of the SMS Executive. Use this role to lessen the processing burden on the site server or to provide duplicate threads. A component server can provide a special communications method, such as RAS, to communicate with another site. |
| Distribution point | A site system that stores package files received from a site server performs the distribution point role. Client computers contact distribution points to obtain programs and files after they have received software distribution advertisements from a CAP. A distribution point can be a Windows NT share, a Windows NT Server, or a NetWare volume. If you plan to provide a large number of packages to a site's client computers, consider assigning this role to one or more computers other than the site server. |
| Logon point | The logon point role provides an initial point of contact
between client computers and the SMS environment. Logon points host
the logon discovery and logon installation methods. For example, if
logon installation is enabled, when a client logs on to a logon
point, the client runs the logon script, determines which site it
belongs to, and finds a CAP for installation. In Windows NT, SMS
installs logon software onto the domain logon servers within your
network. You do not need to plan for separate servers to act as
logon points. NetWare NDS and bindery volumes are also installed as
logon points in their respective environments.
This role can be assigned at any time. The method for assigning the role depends on whether the logon point serves a Windows NT domain users, NetWare NDS users, or NetWare bindery users. |
| SMS site server | The SMS Site Server is role filled by the Windows NT
Server computer where SMS setup has been run. When an SMS site is
installed on a computer, it is automatically assigned the site
server role. The site server, which hosts SMS components needed to
monitor and manage an SMS site, typically performs several
additional roles, including: component server, client access point
(CAP), and distribution point.
This role is assigned during SMS 2.0 installation. |
| SMS site database server | A site system that stores the SMS site database for an SMS
primary site performs the SMS site database server role. The
site database server must be a Windows NT server that has SQL
Server installed. You can install SQL Server on the primary site
server or reduce the load by installing SQL Server on a computer
other than the primary site server. If you install the Software
Metering feature, SQL Server stores and maintains a software
metering database that is separate from the SMS site database but
that can reside on the same site database server.
This role is assigned during SMS 2.0 installation. |
| SMS Provider | The SMS Provider role furnishes the interface between the SMS
Administrator console and the SMS site database. The SMS Provider
must be on the same site system as either the site server or the
site database server.
This role is assigned during SMS 2.0 installation. |
| Software metering server | The software metering server role performs server-side software metering tasks. Client computers running the Software Metering Client Agent communicate directly with these site systems to receive licensed product details, check for license availability, and log application use. Each software metering server caches real-time licensing data that it passes through the site hierarchy to the software metering database. |
| Software Metering database server | A site system that stores the software metering database for an
SMS primary site performs the software metering database
server role. The software metering database server must
be a Windows NT server that has SQL Server installed. It can
be installed on the same computer as a primary site, or to reduce
the load, it can be installed on a computer other than the primary
site server.
This role is assigned during the installation of Software Metering. |
Note NetWare bindery, NetWare NDS, and site database servers cannot perform either the component server or the software metering server role.
Related Topics
Site Systems Configuration Overview