Empirum works based on the "desired state" model, which means that the administrator uses configuration and assignment groups to define the target state of each system or user regarding the objects managed via Empirum, for instance, software packages and operating systems. General definitions are specified only once through the hierarchical inheritance construct; only exceptions are specified individually. These definitions are made by linking systems or users to the software packages and templates in the groups, mostly through drag & drop or copy & paste.

All changes to these definitions must be activated explicitly before they are activated for devices. Exceptions include the deletion of software; in such case, software is deleted directly after the confirmation request and activated accordingly, or the package is set to "Uninstall".

Activation writes the changes into the files used for the systems and users, for instance, to allow the Empirum Agent to analyze these files and install software at the correct date and time. If third-party systems such as vSphere ESX Hypervisor, to which the computer system is connected, are affected, the changes will only become effective on these systems after activation.

Key data that are updated during activation include the following:

• DDC: The control file is written for every system and user and contains assigned software packages with the respective software installation instructions for the Empirum Agent. It is mostly stored under Empirum\Configurator\Values\MachineValues\Domain\computername.ddc and Empirum\ Configurator\Values\UserValues\Domain\username.ddc.
• OS.INI: This file contains the configuration file that has been generated for the system based on the assigned operating system template. It is used during operating system installation and is mostly stored under Empirum\EmpInst\Wizard\OS\Auto\MacAddress\os.ini.
• INI: The file with the name of the system or user contains variables used to initiate software package and operating system installations. It is updated in case changes have been made to the variables or a new assignment of the system or user has occurred. It is mostly stored under Empirum\ Configurator\Values\MachineValues\Domain\computername.ini and Empirum\ Configurator\Values\UserValues\Domain\username.ini.

Activation can be done for multiple objects and with multiple options. There a two activation options available: local or global activation.

Assignment and activation rules can be found under Assignment and Activation Rules.

Local or Global Activation

If a system or user is activated, either directly or via a group, there is the option to select local or global activation. For groups, this setting applies for all objects below that group. This distinction has been made to allow for selective modifications, which can be reset to the defined target state later via global activation. You should always try to set up a consistent system with consistent, globally activated computers and users.

Global activation – Empirum analyses all assignments of the respective object in the configuration and assignment groups and applies the activation rules accordingly. The result of such activation is independent of the point of activation.

Local activation – Local activation – Empirum analyzes only the assignments within the hierarchy where activation is performed and only addresses software packages available in this hierarchy; the activation rule for distribution options is always applied globally to avoid inconsistencies.

Common cases include the following:

• Activation of a configuration or assignment group: This affects all objects in this group as well as all subordinate groups. Depending on the selection, the corresponding files will be updated.
• Activation of a computer or user: Only this object will be activated.
• Push activation of software or a software class: Only the "push" option is available. This method does not use the DDC control file and sends an installation job directly to the selected computers. Important note: This method will only work if the computer is switched on and the Empirum server can connect to this computer via the network. It is mainly used to provide instant assistance when a user has problems or in emergencies where a security patch must be distributed immediately to active systems.
• Reinstallation on a computer: This action can be performed on a computer for one or several software packages and will always be activated immediately.
• Reinstallation in a software package: This action can be performed in a software package for one or several computers and will always be activated immediately.