ConfigMgr - Glossary of Terms


TermDefinition
SiteA site is a management boundary that consists of all computers managed by a common set of management servers. All computers at UT exist within a single Configuration Manager site with the site code AUS.
CollectionA group of computers based on a static grouping or query. A computer may be a member of multiple collections.
Configuration Manager Subscription*A space "carved" off in the central CM environment using Role Based Access Controls.
CSUCollege/School/Unit, is a generalized term that does not specifically refer to an IT group.
ITSO*Information Technology Support Organization refers to a specific IT group. A CSU may have more than one ITSO.
ITSO Prefix*This is a unique code assigned to a ITSO which the ITSO uses as a prefix in the names of all objects it manages.
Delegated Administrator Role*

This a Role defined within Configuration Manager that, when applied to an AD group of users, allows staff to have permission over the set of objects in their subscription.  Users granted this role through membership in ITSO provided AD Security groups MAY NOT BE EIDs.  These users should be privileged accounts created through the Austin Active Directory Department User Tools. Austin Tools (utexas.edu)

Client Certificate Auto-enrollment*This is a process by which a computer enrolls for its own client-based certificate.  The Configuration Manager client uses this certificate to authenticate itself with the CM site server.
Standard Client*A UT owned endpoint with the Configuration Manager Client installed that is included in the default Maintenance Window and default Software Update deployment collections.
Non-Standard Client*A UT owned endpoint with the Configuration Manager Client installed that is excluded from the default Maintenance Window and default Software Update Deployment collections.
Maintenance WindowA property set on a collection that determines the time windows and frequencies of actions performed by the CM client.  Software updates, application installs, and task sequences can all be controlled by Maintenance Windows.
Client Settings

A collection of policy and settings that control basic functionality of the Configuration Manager client. A subscription may have its own Client Settings policy and it inherits the Site Default Client settings.  Conflicts are resolved through the highest precedence applying last.  The "highest precedence" is the Client Settings with the lowest number.  A precedence of 10 is higher than 11, for example.

Task SequenceA Task Sequence is a step-by-step prescription of a list of actions a client will perform in order.
Required

Applications, updates, packages, and other configuration objects can be deployed to clients as "required" or "available".  A "Required" deployment is one that is automatically applied to the targeted devices during any established maintenance window.

AvailableApplications, updates, packages, and other configuration objects can be deployed to clients as "required" or "available". An "Available" deployment is one that is available for end users to initiate through the Software Center on the device they are using.
Software CenterAn application that users can use to interact with packages and applications that have been deployed to their devices.  Installs of packages, applications, and updates can also be initiated from Software Center.
Hardware InventoryUse hardware inventory in Configuration Manager to collect information about the hardware configuration of client devices in your organization. Installed software is also collected with this scan.
Software InventoryDespite its name, software inventory is used to collect information about files on client devices. If you are looking for installed software, use hardware inventory scans.
Configuration Items (CI)

Configuration Items can be any of the following: Software Updates, Registry Values, Files, Custom scripts. Configuration Items themselves are not deployed directly but are deployed using Configuration Baselines.

Configuration Baselines (CB)

The following can be part of a Configuration Baseline: Configuration Items, Software Updates other Configuration Baselines. CBs can be deployed to a collection. 

  * These are terms used by EPM.