- CAP
-
See client access point
(CAP).
- central site
- The primary site at the top of the
SMS hierarchy, to which all other sites in the SMS system report
their inventory and events.
-
See also child site; parent site; secondary
site.
For more information, see About Site
Hierarchies.
- child site
- A site that has a parent site. In an
SMS site hierarchy, every site except the central site is another site's child. Unlike
the terms primary site and secondary site, in which a
site is one or the other, the terms parent and child
are relative; a site can be both.
-
For more information, see About Site
Hierarchies.
- CIMOM
-
See CIM Object
Manager.
- CIM Object Manager
- The primary component in the management infrastructure of the
WBEM
technology. Client applications access the CIM Object Manager to
find the correct provider.
- client
- A computer that has SMS client software installed and belongs
to an SMS site.
-
See also resource.
- client access point
(CAP)
- A site system with the CAP role
provides a communication point between the site server and client
computers. Computers contact CAPs to install and update SMS client
software. After SMS client software has been installed on computers
in a site, they contact a CAP for updated information from the SMS
site server. Clients deliver collected files, inventory
information, discovery data records, and status information to
CAPs.
-
See also collected files;
discovery data record;
site server; site
system; site system role.
For more information, see About Client Access
Points.
- client agents
- Software that runs on SMS clients to perform specific
functions. For example, the Software Metering Client Agent reports
the applications run on a client to the site
system that is assigned the software metering server role.
-
For more information, see Client Agents
Configuration Overview.
- client assignment
-
See site assignment.
- client components
- SMS threads, services, and applications that run on client
computers and provide SMS functionality.
- client installation
- The act of installing SMS client software on discovered
computers in a site.
-
For more information, see Client
Installation Configuration Overview.
- collected files
- Files copied from SMS clients as part of software inventory. After the files are collected from
clients, they are stored on the site server.
-
See also file
collection.
- collection
- A set of resources in a site defined by membership rules. Collections are used to
distribute software, view inventory on clients, and access clients
for remote control sessions. An example of a collection is "All
Windows NT Workstations."
-
See also subcollection;
resource.
- collection limiting
- A method of restricting the scope of a query or a collection
membership rule. A query that is
collection limited can only return resources that are in a specified collection, even
if other resources in the SMS site
database match the query criteria.
- Common
Information Model Object Manager
-
See CIM Object
Manager.
- community
- An administrative security relationship between SNMP entities.
For SNMP transactions, it is always necessary to specify the
community name.
- complete inventory
- A hardware or software inventory cycle
that creates a complete inventory file containing all of the
hardware attributes or inventoried software types found on a
client. A complete inventory is taken only at initial inventory or
when there is a resynchronization. A resynchronization
occurs whenever an inventory file tries to update data that does
not exist in the SMS site
database, when the inventory data is corrupted, or when a
client attaches to a new site). Otherwise, a
delta inventory is taken.
-
See also site server.
- compliance database
- A tab-delimited ASCII text file that contains a list of
software with a compliance level assigned to each product.
- compliance level
- The category types indicating the compliance level of a
software product.
- compliance type
- A list of items that differentiates one type of product
compliance from another. Y2K compliance and Euro compliance are
both compliance types.
- component server
- A site system that runs one or more
of the SMS executive thread components to lessen the processing
burden on the site server or to provide
duplicate threads. A component server is used when a special
communications method, such as RAS, is required to communicate with
another site.
- console tree
- An ordered, hierarchical listing of objects. By default, the
console tree is displayed in the left pane of the Microsoft Management Console
(MMC) window, but it can be hidden. The items in the console
tree and their hierarchical order determine the management
capabilities of that console.
-
See also SMS Administrator console;
snap-in.
- Courier Sender
-
See sender, sender types.
- Crystal Info
- A tool for designing, scheduling, and viewing reports.
- package
- An object that contains the files and instructions for
distributing software to a distribution point.
-
See also program.
For more information, see About Packages.
- package definition
file
- An ASCII text file that contains predefined programs and
property settings for a package. You can create a new package by
importing a package definition file. SMS includes package
definition files for a number of software applications and
operating systems.
-
For more information, see About Package Definition
Files.
- package distribution
- The process of placing a decompressed package image on distribution points, sharing that
image, and making it accessible to clients.
This occurs automatically when you specify distribution points for a package.
- package routing
- The SMS 2.0 software distribution process in which a site
can route a package to its destination even
if it has no direct address. The routing
site is able to determine the most appropriate path for the package
to reach its destination. Also known as fan-out
sending.
- package source
directory
- A directory containing package source files that are used for
package distribution.
-
For more information, see About Package Source
Directories.
- package source files
- The files contained within an SMS package that each advertised program needs in order to run.
Each program within the package uses one or
more of these source files, if they do not already exist on the
target client. For example, Setup program might need installation
files and libraries to operate properly when run.
-
See also package
distribution; software
distribution.
- parcel
- Any set of files that is transferred from one site to another
with Courier Sender. Parcels are created in Courier Sender
Manager.
-
See also sender; sender types.
- parent site
- An SMS site that has one or more child
sites.
-
For more information, see About Site
Hierarchies.
- permission
- The part of a security right that
determines what a user can do to a security object; for example, Read, Create,
or Delete.
-
For more information, see About
Permissions.
- permitted viewers
- A list of users and user groups who can remotely control a
Windows NT-based client.
- pragma statement
- A line in a Management Information
Format (MIF) file or event
configuration file that indicates how the information in the
file relates to the information in an SMS site database. For example, a pragma
might state to add information to the SMS site database.
- primary site
- A site that has its own SMS site database to store information
for itself and its child sites. Primary sites can report to other
primary sites and can have both primary and secondary sites report
to them.
-
For more information, see About Site
Hierarchies.
- product compliance
- An SMS feature that helps identify software products affected
by the year 2000, Euro, and other compliance issues.
-
For more information, see Product Compliance Overview.
- program
- A set of instructions that controls package execution. Each
package typically contains one or more
programs, each of which includes parameters such as a command-line
to be executed and attributes to control command-line execution.
The command line can be an executable file or an installation
script that installs a software application, or it can simply copy
data files.
-
See also advertisement;
collection.
For more information, see About Programs.
- prompted query
- A query in which a dialog box prompts a
user for more information. Prompted queries are constructed with a
general expression, not a specific value. The
SMS Administrator console prompts for the actual value when
the query is run.
-
For more information, see About Criterion
Types.
- secondary site
- An SMS site that has no SMS site database or administrative
tools. A secondary site is managed by and forwards inventory and
status information to its parent site. A secondary site can only be
a child site.
-
For more information, see About Site
Hierarchies.
- security object
- The part of a security right on
which permissions act. SMS has the
following security objects:
Security objects make up both classes and instances. Object
classes define a category of instances. For example, the
Package object class is all packages, but a Package object
instance is one specific package. A user with the
Modify permission on the Package object class can modify all
packages, but a user with the Modify permission on a Package
object instance can modify only the specific package to which the
permission applies.
-
For more information, see Security
Configuration Overview.
- security right
- The functional level of access given to an
SMS Administrator. Security rights comprise three parts:
- A user or user group
- The Windows NT username or group name to which the
security right applies, such as Terry Smith, Administrator, or
Power Users.
- A permission
- The type of action that is permitted, such as Read, Create, or
Delete.
- A security object
- The item on which the permission acts. Security objects can be
either a class (such as all collections), or an instance (such as a
particular collection).
-
See also explicit
security right; implicit
security right.
For more information, see Security Rights
Overview.
- send
- The method SMS uses to transfer data and instructions among
sites. (Limited sending also occurs within a site). Data or
instructions are compressed and written to a send request file. A
sender transfers the file to the target site, which routes the data
or instructions to the appropriate SMS services.
- sender
- An SMS thread component that uses an existing connectivity
system to communicate with other sites. A sender manages the
connection, ensures the integrity of transferred data, recovers
from errors, and closes connections when they are no longer needed.
See also sender_types
-
For more information, see About
Senders.
- send request file
- A file with instructions that a sender uses to connect to and
transfer data to a destination.
- sender types
- There are six types of senders available
for use in SMS:
- Standard
- Used in all local area network (LAN) communication. Standard
Sender is also used for wide area network (WAN) communications when
routers are used to connect to LAN segments.
- Asynchronous RAS
- Used in Remote Access Service (RAS) communication over an
asynchronous line.
- ISDN RAS
- Used in Remote Access Service (RAS) communication over an ISDN
line.
- SNA RAS
- Used in SNA communication over a Remote Access Service (RAS)
line.
- X25 RAS
- Used in Remote Access Service (RAS) communication over an X.25
line.
- Courier
- Used to send and receive SMS data (parcels) through compact discs, floppy disks, or
tapes. Courier Sender is typically used to send large volumes of
data when available bandwidth is very limited.
- service component
- SMS programs that run as Windows NT services that can be
started and stopped through the Services icon in Control
Panel, in Windows NT 4.0.
- site
-
See SMS site.
- site assignment
- The process of allocating selected resources to an SMS
site.
-
See also site assignment
rules
For more information, see About
Sites.
- site assignment
rules
- The list of subnets and IPX network numbers that an SMS
administrator defines as the boundaries of an SMS site. SMS uses
these rules to determine which resources
and clients belong to the site.
-
See also site
assignment.
- site boundaries
- The list of subnets and IPX network numbers that an SMS
administrator defines as the boundaries of an SMS site.
-
For more information, see About
Sites.
- site code
- A three-character code that SMS uses to identify a site. When a
site is installed, a site code assigned. The site code cannot be
changed after installation. Site codes must be unique across an SMS
site hierarchy. The valid characters for site codes are A through Z
and 0 through 9.
- site control file
- An ASCII text file (Sitectrl.ct0) that contains the
configuration of a site. There are two types of site control files:
- actual site control
file
- A working copy of the site control file stored in the SMS site database.
- delta site control
file
- Changes to the site control file in .var file format that are
processed through Site Control Manager.
- site database
-
See SMS site
database.
- site database server
- A site system role assigned to the computer that hosts the SMS
site database (a SQL Server database). The computer might or
might not be the site server.
-
See also site server; SMS site database.
- site hierarchy
- The relationship of all the SMS sites
in an organization. A site hierarchy is made up of primary and
secondary sites. The main
administrative site at the top of the hierarchy is known as the
central site.
-
See also primary site; SMS
site; subsite.
For more information, see About Site
Hierarchies.
- site server
- A Windows NT Server computer on which SMS site Setup has
been run. When SMS is installed on a computer, that computer 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.
-
See also site system
role.
- site server domain
- A Windows NT domain that contains the site server.
- site server role
- A role assigned by the SMS site server to a site server computer when SMS components are
installed on that computer.
- site system
- A server, Windows NT share, or NetWare volume that
provides SMS functionality to the site. The functionality
contributed by a site system is indicated by its assigned roles. A
site system can perform all roles, or it can perform only one role.
You determine some site system roles during installation and others
by using the SMS Administrator console. In SMS 2.0, there
are four types of site systems:
-
- NetWare bindery volume
- NetWare NDS volume
- Windows NT server
- Windows NT share
For more information, see Site Systems
Configuration Overview.
- site system role
- A role that a site system can perform in an SMS site. There are
several possible site system roles. All of the roles can be
assigned to the primary site server, or they can be spread out over
several different site systems. Some of the roles are assigned
during installation, and others are assigned through the
SMS Administrator console. Although the items below are
defined as site system roles, they are also often referred to as
servers. For example, the text might refer to the distribution
point. In this context, it means the server performing the
distribution point role.
-
- client access point (CAP)
- A site system role that functions as the main communication
point between the site server and clients.
- component server
- A site system role that can be filled by any SMS site system
that runs the SMS Executive service. SMS logon points are also
component servers.
- distribution point
- A site system role that stores package files received from a
site server. Clients contact distribution points to obtain programs
and files after they detect that an advertisement is available from
a CAP.
- logon point
- A site system role that hosts the logon discovery and logon
installation methods.
- site database server
- A site system role assigned to the computer that hosts the SMS
site database (which is SQL Server). The computer with this
role does not have to be the site server as well.
- site server
- A site system 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.
- SMS Administrator console role
- A site system role filled by a computer that is running
Windows NT Server or Windows NT Workstation and that has
the SMS Administrator console installed.
- SMS Provider Role
- A site system role that processes requests for data from the
SMS site database. The SMS Provider can be installed only on a
primary site server or the site database server.
- software
metering database server
- A site system role assigned to the computer that hosts the
software metering database (which is a SQL Server
database).
- software metering
server
- A site system role that determines whether a software license
can be used. When the Software Metering Client Agent queries the
software metering server for a license, the software metering
server first determines whether the software can be used and then
sends a response to the client. Each software metering site must
include at least one software metering server.
- site transaction log
- A SQL Server log that maintains before and after images of
transactions, so that if corruption (such as power loss) occurs,
the transaction can be backed out and the database can be returned
to its previous state.
- SMS Administrator
console
- The graphical user interface (GUI) used to administer SMS.
-
See also Microsoft Management Console
(MMC); snap-in.
- SMS component
- A program that performs a specific SMS task. In SMS, there are
three types of components: service
components, thread
components, and client
components.
- SMS Provider
- The WBEM
provider that exposes SMS site data. The SMS Provider is an
intermediary between the CIM Object
Manager and any SMS data. The SMS Provider also accesses the
SMS site database to provide data
to the SMS Administrator
console.
- SMS Service account
- An account used by SMS services on Windows NT computers to
access the SMS site systems in a
site.
-
For more information, see About the SMS
Service Account.
- SMS site
- Site systems and resources bounded by a group of subnets, such
as an Internet Protocol (IP) subnet or an Internetwork Packet
Exchange (IPX) network number.
-
For more information, see About
Sites.
- SMS site database
- A Microsoft SQL Server database that stores discovery
data, configuration and status inventory, and software inventory.
Every primary site has an SMS site database. The server supporting
the SMS site database is automatically assigned the site database
server role.
-
See also site system
role.
- snap-in
- A management tool or set of management tools designed to run
within the Microsoft
Management Console (MMC). A snap-in can also be defined as code
that provides management functionality.
-
See also SMS Administrator
console.
- SNA RAS Sender
-
See sender; sender types.
- SNMP agent
- A process running on an SNMP-managed device that uses SNMP to
exchange management information with one or more management
stations.
- SNMP trap
- An unsolicited SNMP packet sent from one SNMP entity to
another, usually in response to a stimulus or an event on the
sending entity.
-
For more information, see Translating SNMP Traps Overview.
- SNMP Trap Translator
-
See Event to Trap
Translator.
- software
distribution
- The automated process of distributing software programs to
client computers in your SMS hierarchy.
- software inventory
- The automated process SMS uses to gather information about
software in use on client computers in your organization.
-
For more information, see About Software
Inventory.
- software metering
- The process by which SMS manages software licenses and
restricts the use of specific software applications.
- Software Metering
tool
- An SMS tool that you can use to monitor and control the use of
software on a network.
- Standard Sender
-
See sender; sender types.
- status filter rule
- A user-defined rule that determines the actions performed by
Status Manager when it receives a status message from a component.
Status Manager actions determine whether status messages are
written to the SMS site database, replicated to the parent site,
and/or written to the Windows NT Event Log.
-
For more information, see Status Filter
Rules Configuration Overview.
- status indicator
- Graphics that depict the overall status of an SMS component or
site system. These graphics overlay the Component Status Summarizer and the Site System
Status Summarizer in the SMS console tree. The three status
indicators are:
OK. No item has crossed a threshold.
Warning. An item has crossed its warning
threshold.
Critical. An item has crossed its critical
threshold.
A status indicator depicts the state of the most troubled component or site
system within a site.
- status message
- A message for the SMS Administrator console generated by
an SMS component. Status messages differ from Windows NT
events in that they represent the flow of activity within an SMS
site.
-
For more information, see Status Messages Overview.
- status message ID
- A unique status message identifier. However, each instance of
the same status message does not have a different ID. For example,
if a certain message's ID is 62, it is 62 every time the message is
generated. A status message has the same ID regardless of locale.
Status Message Viewer maps
each ID to locale-specific message text.
- status message
property
- An optional attribute of a status message that lets you
differentiate among groups of messages when querying, finding, and
filtering. A status message property can be one of the following:
Advertisement ID, Collection ID, Package ID, or User Name.
-
For more information, see About Status Message
Properties and Property Values.
- status message
property value
- An optional attribute of a status message property that is
applied by the SMS component
generating the message. Status message properties let you
differentiate messages associated with particular advertisements,
collections, packages, and users when querying, finding, and
filtering.
-
For more information about status message property value,
see About Status Message Properties and Property
Values.
- status message
severity
- Each status message has one of three severity levels:
- Error
- A condition that could cause loss of data or services and
requires swift operator intervention.
- Warning
- A condition that could degrade system performance, but is not
expected to cause loss of data or services. Warnings are generally
recoverable if acted on quickly.
- Informational
- A change of state or condition. For example, informational
messages are generated each time a service stops or restarts.
- status message type
- Each status message has one of the following types:
- Audit
- Provides an audit trail of SMS configuration create, set, and
delete activities. For example, an audit message is generated every
time you create or delete a package or set package properties.
Audit messages, which are reported by the SMS Provider, all have
the Informational severity level.
- Detail
- Contains information about processing a system action. For
example, a status detail message can report that the Despooler is
decompressing a package into a specific directory on a specific
drive. Detail messages usually occur between milestone messages.
For example, a component can report a status milestone when it
begins replicating files, a status detail for each operation it
performs during replication, and a status milestone when the
replication is completed.
- Milestone
- Delimits the separate stages of a system action. For example:
- An SMS component starting or stopping
- The Scheduler detecting and processing a new send request
- A Standard sender establishing a
connection and sending a package file and instructions
- Status Message
Viewer
- A tool in the SMS Administrator console used to browse the
status messages stored in the SMS site database.
-
For more information, see Status Message Viewer
Overview.
- status summarizer
- A component that works with Status Manager to produce status
summaries from status messages and
other data in the SMS site
database. Status summarizers are displayed in the
SMS Administrator console tree, and some use status indicators. Status summarizers are
not reports; they are dynamic real-time views of the state of SMS,
and they change constantly based on the flow of status messages in
a site.
-
For more information, see About Status
Summarizers.
- status system
- The overall system that generates, collects, processes,
replicates, and presents status
messages and other data to the SMS Administrator console.
The status system includes Status Manager, status summarizers, and Status Message Viewer.
- storage object
- Any addressable device capable of storing data, including:
- SQL Server database
- SQL Server transaction log
- Windows NT share of the form \\server\share
- Windows NT share of the form \\server\D$, where D is a
share
- NetWare NDS volumes
- subcollection
- A collection that is associated with
another collection for the purpose of software distribution.
-
For more information, see About
Subcollections.
- subnet
- In SMS, a network (such as Internet Protocol [IP] or
Internetwork Packet Exchange [IPX]) that is a component of a larger
network.
- subsite
- Any site that is any number of levels below the current site in
a hierarchy.
-
For more information, see About Site
Hierarchies.
- system database
-
See SMS site
database.