Skip to content
CapaSystems Docs

What is Configuration Management

The following is a description of the individual elements in Configuration Management.

How Configuration Management fits together

Section titled “How Configuration Management fits together”

Everything in Configuration Management lives under a Configuration Management Point (CMP). You normally have a Development point — where packages, profiles, and power schemes are created and tested — and a Production point they are promoted to. Each CMP is organized into the areas below.

graph TD
  CMP["Configuration Management Point<br/>(Development promoted to Production)"]
  CMP --> BU["Business Units"]
  CMP --> AP["Applications and Packages"]
  CMP --> PR["Profiles"]
  CMP --> UN["Units"]
  CMP --> GR["Groups"]
  CMP --> MS["Management Servers"]
  CMP --> VW["Views"]
  AP --> CP["Computer Packages<br/>(incl. CapaPacks)"]
  AP --> UP["User Packages"]
  UN --> UNc["Computers and Devices"]
  UN --> UNu["Users"]
  UN --> UNp["Printers"]
  UN --> UNo["Other Assets"]
  GR --> GRc["Custom groups<br/>Static / Department / AD / Dynamic"]
  GR --> SG["System Groups"]
  SG --> SGa["Calendar Groups"]
  SG --> SGb["Catalog Groups"]
  SG --> SGc["Self Service Configurations"]
  SG --> SGd["Reinstallation Groups"]
  SG --> SGe["Power Management"]
  VW --> VWx["Reinstall / Utilization / Startup-Logon / Unhealthy Agents"]
The structure of a Configuration Management Point.

Packages, applications, and profiles are created in the root (Development) CMP and promoted to child (Production) CMPs. Before they can be linked to groups or units they must be assigned to a Business Unit — units, groups, and views each belong to a single Business Unit, while packages, applications, and profiles can be shared across several.

In this section

Section titled “In this section”

The Configuration Management Point

Packages and applications

Profiles

Units and printers

Groups

Power management

Views

General concepts and tools

CapaOne integration