Glossary

access permissions

Permission to perform operations associated with a specific shared resource, such as a file, directory, or printer. Permissions must be granted by the system administrator to individual user accounts or administrative groups. (Microsoft)

administration permissions

DSM allows a flexible access control to the resources: Individual users can be assigned defined access permissions on the various levels of the infrastructure for certain resources (e.g. sites or regions).

application package

Collective term for packages which are used to install software applications.

Application Virtualization

The aim in virtualizing an application is to decouple it from the (host) operating system on which it is installed. Common to the virtualization solutions available on the market is that they generate a virtualization layer which fits between the application and the host operating system. This mirrors to the application the presence of a file system and a registry. DSM supports application virtualization with VMware ThinApp.

assigned configuration

The assigned configuration contains the package and the parameters, which are supposedly installed on the computer, according to the associated policy. The assigned configuration is only installed on the computer if it becomes the desired configuration of the policy instance.

assignment

A package is assigned to an installation target in the DSM Console. An assignment results in a policy.

assignment of a computer to the site

The client is assigned to a site when the managed computer starts (even before accessing the network); the assignment is based on the local configuration database (ICDB) and depends on the site definition and the network status.

associated Distribution Service

Distribution Service that carries out the distribution to the corresponding object of the site structure (writing to this object, reading from parent object).

AutoInsert

AutoInsert is a DSM process that automatically adds computers or users to the organization tree if the Installer is called on the respective computer or in the respective user context.

AutoInstaller

The application with which DSM automatically maintains all managed computers. It is used to automatically install, repair and uninstall packages (software). The DSM Agent usually starts the AutoInstaller.

automatic installation

Either the AutoInstaller (user context) or the Service Installer (computer context) automatically installs a package.

AutoUninstall

The package is uninstalled automatically if the assignment for the package does not apply.

bandwidth-saving

The DSM Client can save bandwidth because the respective client process has the lowest priority. This means that the client process can change the network load dynamically depending on the current network load: If the network load is high the DSM Client can considerably reduce its activity; if the network load is very low, the client process will use the complete bandwidth.

basic inventory

Basic inventory includes gathering a managed computer's most important data. The DSM Client gathers the IP or MAC address, for example, when synchronizing the Client.

BLS authentication

The user account for BLS authentication is required for the installation of the Business Logic Server and access to the web services. The user account is automatically defined as 'Supervisor' in DSM and does not need special file system permissions.

Business Logic Auxiliary Server

HEAT DSM server application on a Management Point which takes over various tasks to relocate processing power from the Business Logic Server to other computers.

Business Logic Server

HEAT DSM server application on a Management Point which provides all central services for accessing the data contained in the DSM Database (DSMDB).

caching

Local buffering and management of data. The DSM Client performs caching for all control data, actively checking whether the stored data is still up-to-date. Installation data is dealt with separately (see: Staging).

catch site

A catch site is used to provide a site to which managed computers can be assigned to (these computers may not be assigned to a site at all). Background: Some sites "fall out" of the site structure or cannot be assigned to a site at all (especially when new sites or locations are integrated)

category

Organization unit of the software library. A category can be used for filtering and searching.

central depot

The DSM infrastructure can only be edited at one central place in the enterprise, i.e. the central depot (master depot of the ORG). During the DSM installation, the computer on which you are installing DSM automatically becomes the central depot. The central depot will at the same time also become the master depot for the first region and the first site.

Central Management Point

Management Point on the site structure's ORG level. Includes the Business Logic Server that controls the access to the DSMDB (see also Management Point)

changeover with date

Staging mode of a standard policy (automatic installation). Is intended for packages that will be installed on all computers on a due date.

Citrix Integration

HEAT DSM extension for the management of Citrix farms. Server application on a Management Point.

client

Computer to which software is to be distributed using DSM; on this computer software packages will be carried out, typically in an automated fashion. Usually, users working on a client computer have "normal" rights, i.e. they do not have administrator rights. A managed computer is a client which is managed by DSM.

client components

DSM programs contain different client components the DSM infrastructure automatically distributes to the managed computers.

Client Manager

Predefined role for managing organizational data in the DSMC. The role owners have the right to create and manage computers, users groups or OUs.

Client Proxy

HEAT DSM server application on a Management Point which provides the communication between the DSM environment and the Universal Clients on Linux computers.

Client Proxy SOAP Interface

Serves as communication interface between the OSD Boot Clients for Windows/Linux and Linux clients with the Client Proxy Service.

client synchronization

All of the control data that is relevant for a managed computer is synchronized automatically with the DSMDB and stored in the DSMDB cache; this procedure is called client synchronization. The client synchronization is performed from the Installer to the managed computer.

command

Component of the eScript. Carries out a certain action during the execution of a package; copies a list of files, for example.

command classification

A command within the package script can be classified depending on the following "properties": A command can either be assigned to the package's user portion or to its computer portion; it can be executed with the rights of a "normal" user account or it requires adminstrative privileges (i.e. it is service-executed). A command is automatically classified when a package script is analyzed. Command classification is required for Traveling User Support and Local Security Handling.

compliance

The compliance of a computer clearly indicates whether a computer has the status that was defined by the existing policies and policy instances. A computer's compliance can be calculated from the associated policy instances. By comparing the desired configuration with the actual installed configuration, the system determines the current compliance status of a policy instance.

compliance status

The compliance status indicates whether a policy has been implemented on an installation target. It can take the following values: compliant, not compliant, compliance pending, not possible, client prerequisites not fulfilled, undefined.

component

A package as a part of a software set is also referred to as component.

computer

All devices that can be managed with HEAT DSM, including servers, Fat Clients, Thin Clients, laptops and mobile devices. HEAT DSM differentiates between managed and unmanaged computers.

computer portion (of an installation)

The portion of the package which is carried out with the help of computer-related commands.

computer prerequisites

Computer prerequisites can be defined for each package and are checked prior to the installation of the package on a managed computer. If the selected prerequisites do not apply, the installation will not be carried out. DSM uses client prerequisites and server prerequisites. Unlike the client prerequisites, server prerequisites are already checked during assignment. These are based on the basic inventory data which every managed computer sends to the DSMDB.

computer type

Categories of computers. For example: desktop, Terminal Server, server, laptop

computer-related

Refers to the classification of a command or to how the package's installation is logged in the registry.

Configuration Package

By using configuration items, this package type makes it easier to prepackage configuration settings for computers.

configuration table

The Configuration Table contains the infrastructure settings stored in the configuration database (ICDB), displayed in table form.

container

Objects with which the DSM organization tree and the software library can be structured hierarchically. Containers include the parent ORG, the software library, the domain, the organizational unit (OU) and the software folder. Depending on the modules used, there are additional objects such as the Citrix zone, Citrix farm or Managed Mobile Devices. These containers specify which action ranges the role keepers have.

context

Location of an object within a structure. For example, the context objects in the site structure determines who is allowed to manage a specific object and which validity the object has (for Management Points, for example)

control data

Control data comprises all data required for the decision whether or not to install a package on a managed computer; control data is represented by the parameters and other settings of packages and installation targets and is stored in the DSMDB.

current site

The site where the depot is located which the client is currently accessing. The current site can be the primary site or a neighboring site.

current state

Description of the actual state of a managed computer. Results from the compliance status of the associated policy instances. See also: installed configuration.

deployment

Deployment refers to software installation, integration, maintenance and uninstallation. The term also includes software distribution to several computers, e.g. over a company network.

depot

A depot provides the storage for the repositories, the Infrastructure Configuration Database (ICDB) and the DSM program files. Every depot is assigned to a specific site within the site structure.

desired configuration

The desired configuration contains the package and the parameters, which are supposedly installed on the computer, according to the valid assignment.

desired state

Description of the desired state of a managed computer. Results from the compliance status of the associated policy instances. See also: desired configuration.

Desktop Virtualization

The desktop virtualization with Virtual Desktop Infrastructure (VDI) provides every user with an individual virtual desktop computer on one host or on several hosts (servers) in the company's computer center.

detail window

The detail window shows the details for the selected object; it is an integral part of the DSM Console's object window.

device

Any piece of equipment that can be attached to a network or computer; for example, a printer, joystick, adapter, or modem card, or any other peripheral equipment. A device requires a device driver to function with Windows. (Microsoft)

device class

To provide a better overview, every device is assigned to a specific device class (e.g. printers or imaging devices). The device class is specified according to different criteria. A device class is not the same as a device type (which Microsoft uses in the Device Manager).

device driver

Software that allows Windows to communicate with a specific hardware device. Before Windows can use any new hardware, a device driver must be installed. (Microsoft)

Device Library

In addition to managing the installation targets, software packages, patches and virtual environments, DSM also manages the devices, which the DSM Client detects on the managed computers, in the Organization view of the DSM Console.

distribution

Distribution in networks refers to the number of the included computers and their distribution to individual subnets. Also, distribution refers to the targeted distribution of software, for example, or components from a central point to computers in the network. As opposed to deployment, distribution does not imply the actual installation. Distribution in HEAT DSM therefore is the delivery of data between depots within the site structure. Directional (descending), cascaded (from node to node) or scheduled (polling intervals). There are different distribution processes for different files. The network load that is caused by distribution and the periods during which the data is scheduled to be distributed with a defined intensity can be controlled (distribution timeframe, polling interval etc.).

Distribution Service

Service that is required for distribution; it is installed as an application on a Management Point and executes the write and read processes on the depots.

distribution target

Distribution targets can be explicitly specified for package distribution, either as objects of the site structure or in the form of site groups.

domain

Part of the organization tree in the DSM Console. The domain can be taken over from an external directory service (Active Directory) or predefined by DSM modules (e.g. "Managed Mobile Devices"). Domains allow also to map superordinated levels of an organization; they can be nested.

driver

A device driver is a program module other programs use to access connected computer components via a standardized software interface. Device drivers help programs handle all kinds of different hardware. DSM differentiates between PnP drivers and mass storage drivers.

Driver Package

Package type that contains a driver installation. Respective packages can be installed during Unattended Installation and when Windows is running.

DSM Agent

The DSM Agent is an active component of the DSM Client which is started at runtime via a login script. The DSM Agent executes the initial installation of the DSM Clients and starts the AutoInstaller. Using a polling interval, the DSM Agent can be activated in regular intervals. Also, it can be used to start DSM applications or to install or uninstall DSM services.

DSM Center

Icon in the Windows task bar which displays and controls DSM Client components.

DSM Classic Patch Management

HEAT DSM extension for the automated patch management of Microsoft patches and patches that can be closed by the Windows Update Agent.

DSM Client

Part of the DSM components are installed locally on each computer which is managed via DSM. These local components make up the DSM Client.

DSM Console

The DSM Console (DSMC) is the standard user interface for the task-oriented administration of Lifecycle Management with HEAT DSM. Here, all DSM modules used for Lifecycle Management are integrated.

DSM Core Services

Part of the DSM Management Services which provide the functionalities required on all managed computers likewise. These are: ICDB access, network status identification, client synchronization, update of local program files etc.

DSM Database

The central configuration database contains all information relevant for the managed computers (desired and current state), for the users, the packages and their interrelations. The desired and current state of the managed computers includes the specified policies along with their compliance status. (Abbr.: DSMDB)

DSM Management Services

The DSM Management Services include all DSM Services based on a common Management Agent Framework; they are part of the DSM Client and the Management Point. These are: DSM Runtime Service, DSM Core Services, and DSM Client Management Service.

DSM NetInstall

DSM NetInstall - the core module of HEAT DSM - sets new standards in software and configuration management. The system is defined by policies, and the compliance-focused infrastructure automatically guarantees that implementation will succeed. At the same time the transparency of your software is enhanced, meaning the compliance status of all systems is clear at any given time.

DSM OS Deployment

HEAT DSM extension for the automated installation of operating systems.

DSM Patch Management

HEAT DSM extension for the automated patch management. HEAT DSM offers two different patch management solutions: DSM Classic Patch Management and DSM PatchLink.

DSM PatchLink

DSM PatchLink uses HEAT Software's own patented Patch-Smart technology for the scan and rollout processes. Like DSM Classic Patch Management, this Patch Management technology supports all Microsoft products and additionally many 3rd party products.

DSM Runtime Service

Part of the DSM Management Services which activates the Service Installer or the Pipe Installer as background process to execute packages (or parts of which) that require local administrator privileges. By using the DSM Runtime Service it is not necessary to assign extended rights to a logged on user.

DSM Shared Infrastructure

Shared infrastructure of the DSM modules. Provides the shared components. These include the DSM Management Services, for example.

DSM Suite

The DSM Suite includes all installed modules in a DSM environment.

DSM Virtualization

HEAT DSM extension for the automated management of virtualized applications, hardware, and desktops.

DSM Web

HEAT DSM extension for the operation of HEAT DSM in a web console. Server application on a Management Point.

DSMDB Cache

Local directory on a managed computer which servers as local cache or client-specific DSMDB data on a managed computer. The DSMDB data include basic inventory data, policy instances, package control data and status data.

dynamic group

A dynamic group is an integral part of the organization tree which allows for an automatic grouping of computers and users depending on their variable properties.

emergency rollout

Staging mode of a standard policy (automatic installation). These policies have the highest download priority and are intended for security-relevant packages which are to be installed immediately.

endpoint

An endpoint is an Internet-capable computer hardware device on a TCP/IP network. The term can refer to desktop computers, laptops, smart phones, tablets, thin clients, printers or other specialized hardware such POS terminals and smart meters. (WhatIs.com)

eScript

An eScript is the command sequence of a package which is saved by default in the include file. The script contains commands the Installer executes when a package is installed, for example: Copy commands which copy the software files; registry extension commands and commands used to create links. The eScript can be edited in the Packaging Workbench.

eScript Package

This basic package type is based on eScripts. Depending on the commands used, this package allows for the automation of various actions, e.g. the installation of software, client management commands etc.

event

This is a system event the Business Logic Server sends to the Event Dispatchers using the Push mechanism. There are three types of events: FastInstall, WakeOnLan (WOL) and OSD Push. Events are sent directly to their recipients. The distribution process is not used in this case.

Event Dispatcher

HEAT DSM server application on a Management Point which processes Push events such as FastInstall, WakeOnLAN or OSD Push sent by the Business Logic Server (BLS).

execution mode

The execution mode of a policy instance specifies which action must be executed for the assigned package by the Installer (e.g. installation or update) in order to achieve compliance. As long as an execution mode is set, the compliance status remains "Compliance pending".

execution settings

Settings that influence how the package is installed; e.g. installation by the service or the user, uninstallation etc.

fail-safe operation

This can be achieved in DSM by: Using several depots per site; definition of neighboring sites.

Fast Install

Immediate execution of a package on a remote computer in the DSMC.

Fat Client

Fat clients (unlike thin clients) are fully equipped and powerful computers with sufficient memory and disc and CD ROM drives as well as powerful graphic cards. In Client Server applications, fat clients provide most of the CPU power in Client Server applications.

group

Installation targets can be arranged individually in groups in the organization tree. Groups can contain users or computers. There are static and dynamic groups.

Hardware Virtualization

Hardware virtualization is one of the three types of virtualization the DSM environment supports. Here, whole computers are virtualized with BIOS,operating system, drivers, applications and user settings.

HEAT Client Management

HEAT Client Management solutions help customers gain control of their complex IT infrastructures by providing a high level of process automation, unified management, and compliance enforcement which form the foundation for efficient and effective IT services and yield improved end-user productivity.

HEAT Cloud Remote

Software for remote controlling clients and servers. With HEAT Cloud Remote, you can execute help desk tasks beyond local networks over the internet and in the LAN; you can remote control not only computers in the local network but practically any computer with an internet connection. And you don't need an RAS connection for computers outside your company network.

HEAT Cloud Remote Integration

HEAT DSM extension for the remote control of clients using the stand-alone application HEAT Cloud Remote.

HEAT Desktop & Server Management

Desktop & Server Management (DSM) is a multi-platform Client Management solution designed to automate IT operational tasks, from installing applications and operating systems to monitoring and maintaining devices over time. HEAT DSM contains all the client management tools necessary to manage and control physical, virtual and mobile devices from a unified, intuitive console.

HEAT Discovery

HEAT Discovery allows to find, audit and continually track every computer and server, every network printer and switch, every major operating system and application on the network; building a comprehensive and dynamically-updated catalog of your complete IT inventory.

HEAT Discovery Integration

HEAT DSM extension for the integration of dynamically updated asset information using the stand-alone application HEAT Discovery. Server application on a Management Point.

HEAT MDM

HEAT Mobile Device Management is a centralized platform designed to manage the mobile device lifecycle through configuration, application update, security monitoring, periodical data backup/restore, to remote troubleshooting.

HEAT Personality Migration

HEAT Personality Migration allows you to fully automate the backup and migration of user states for all users on a computer.

HEAT Service Management Integration

HEAT DSM extension for workflow-driven service management activities using the stand-alone application HEAT Service Management.

HEAT Unified Endpoint Management

HEAT Unified Endpoint Management solutions efficiently manage and secure traditional, virtual, and mobile endpoints across their lifecycle to maximize operational efficiencies, minimize IT costs, and improve service quality.

DSM WebDAV Server

DSM provides an own DSM WebDAV Server for HTTP depots that removes limitations (e.g. no support for big files) of the Microsoft WebDAV implementation.

Helpdesk User

Predefined role for managing organizational data in the DSMC. The role owner has the right to evaluate software and hardware information, to make assignments and to remote-control computers.

infrastructure

DSM environment with its configuration.

Infrastructure Configuration Database

This is the database that contains the infrastructure configuration (i.e. the infrastructure objects, their logical relations and properties). The ICDB consists of the files "NiCfgLcl.ncp" and "NiCfgSrv.ncp"

Infrastructure Package

Package type which contains DSM program files for the distribution to the depots.

install directory

Repository directory on a depot that serves as a source for the installations.

installation data

Mass data required for the actual installation of a package.

installation medium

DSM employs installation media, such as an USB memory stick or a hard drive, to manage computers that are not at all connected to a network or that use a slow connection.

installation mode

During this mode, installations are possible.

installation order

Specifies the installation order of packages for an individual computer if more than one package is to be installed.

installation parameters

An installation parameter is a variable that is defined per package and evaluated during installation. Per assignment (policy), a parameter can have its own value.

installation target

Objects to which you can assign packages. Computers, users, domains, OUs and groups are installation targets in the organization tree.

installation timeframe

Term from the Windows Terminal Server environment (WTS); equivalent to maintenance timeframe.

installed configuration

The installed configuration contains the package and the parameters that are actually installed on the computer.

Installer

DSM module which executes installations on a managed computer. Depending on the selected call parameter, the Installer is started as AutoInstaller, Software Shop or Service Installer.

interactive installation

The logged-on user can install a package interactively with the Software Shop (pull method).

interactive uninstallation

The logged-on user can uninstall a package (interactively) with the Software Shop.

Internet Information Services

(abbr.: IIS) The IIS need to be installed on the server as a prerequisite for the Management Point. The IIS guarantee that the data can be sent via HTTP and displayed in a console.

LAN site

Site in which the managed computers are linked directly to the depot.

load balancing

(a) By using several depots per site, the load can be balanced automatically when installing or logging on to managed computers. (b) By distributing the active server components to several Management Points or servers the load can be balanced optimally. A constant load during package distribution can be achieved by specifying the periods when the packages are distributed with a defined intensity with the help of the distribution timeframe.

local depot

Every depot is a local depot, i.e. it serves as a file server for DSM modules.

local security

Solution of limiting the user access to local resources (files, registry, etc.). Windows with an NTFS file system offers local security. If a user does not have the required privileges, Windows prevents the action from being executed, for example, a program is not installed.

Local Security Handling

Automatic handling of local security (NTFS security) on Windows computers. DSM's answer to software management in the face of local security and limited user rights.

log file

Every DSM module writes log files during execution. The log files contain important information which make troubleshooting easier for you and our Technical Support team in case something does not run as required. The log files are stored on the respective clients in the directory which is set in the configuration table.

long-running task

These are tasks the BLS processes in the background and which can take a very long time. This includes e.g. creating, updating, and deleting policies as well as adding and removing installation targets to and from policies.

MAC address

Media Access Control Address: Globally used term, unique identifier attached to most forms of networking equipment.

maintenance plan

Definition of a timeframe in which computers (esp. Windows Terminal Servers or Citrix Servers) are maintained (e.g. in order to repair or install software).

maintenance timeframe

This is the timeframe when computers (esp. Citrix Servers or Terminal Servers) are not productive and are available for repair or the installation of software. Equivalent to installation timeframe.

managed computer

A computer that is managed with the help of DSM modules.

management applications

Applications within the framework of the HEAT DSM, which use the same server components. Management applications are installed on a Management Point together with their components to provide the functionality of a specific DSM module.

management components

The Management Point contains a series of DSM server components depending on which management applications are installed "under" this Management Point. These components include services, agents, and extensions.

Management Point

A Management Point (MP) is a computer that provides the services of different management applications such as Business Logic Server or OSD Proxy. Every MP provides an infrastructure based on the Management Services allowing a remote installation and configuration of Management applications. MPs are independent site structure objects.

master depot

The DSM infrastructure assigns one depot to the ORG, to every region and to every site as a master depot. The master depots contain a working directory ( \work ) which serves as the source for the distribution to child objects and as the target of the distribution from parent objects.

master repository

Working copy of a repository. Stored in the "work" directory on the master depot of the site structure object in which the repository is located. From here, the repository is distributed to the other depots as read-only copy.

MDM Integration

HEAT DSM extension for the management of mobile devices using the stand-alone application HEAT MDM, or another MDM solution. Server application on a Management Point.

module

A module is an application HEAT Software provides within HEAT DSM. For example DSM OS Deployment and DSM Patch Management.

MSI Package

An MSI package is a package type which contains an MSI based software.

MSI Spy

Used to record changes to an MSI-based software. As a result, an MSI Transform is added to the MSI-based software.

MSI Transform

To customize an MSI-based software to suit your needs, you use transforms. Transforms enable you to customize MSI-based software before installation, for example by adding or changing files, shortcuts or registry keys.

multiple BLS

You can add additional BLS to a Business Logic Server (BLS). This allows you to increase performance and scalability of the DSM environment but it also increases a general failover. In this case, all BLS access the same databases for their operations: the DSM Management Database (DSMDB) and the Infrastructure Configuration Database (ICDB).

navigation window

A window in the DSM Console that provides an overview over the available structure. By selecting an element within the structure the associated objects are displayed in the object window. The navigation window offers Favorites and a Find functionality.

neighboring site

Definable site the managed computer switches to if there is no depot available in its primary site. Serves as fail-safe operation.

NetInstall Monitor

The NetInstall Monitor gives you easy access to the log files and the list of packages executed on the current computer.

NetInstall Spy

Part of the DSMC's software factory that allows for the analysis of software installations according to the differentiation method. An eScript package is the result.

network traffic

Describes the network load. HEAT DSM provides several mechanisms to control the network load.

object

An object is a managed 'unit', for example, a computer or a user. Objects are displayed in the DSM Console's object window.

object ID

Unique designator DSM assigns to of each object in the site structure; used for the internal identification of objects.

object properties

The DSMDB contains predefined or user-defined properties for managed objects: OUs, groups, computers, users and packages. The values of the properties are either automatically set or can be edited. The same properties are available for all objects of a type. User-defined properties are managed in the Schema Manager. The user-defined properties for packages are called installation parameters.

object window

The object window is a window in the DSM Console where the objects are displayed in the selected context.

offline medium

Medium (e.g. CD, DVD, or Memory Stick) replacing a network resource that is used to execute management tasks in offline mode, for example, software installation or repair.

offline site

Site type for managed computers in offline operation (without a network connection to a depot). In offline operation, the repository and the required DSM program files either reside locally on an offline medium.

organization

The 'Organization' object (short: ORG) always represents the uppermost level of the DSM site structure. The ORG level is where you centrally control access to the entire site structure and the licensing. Numerous settings are already made on the ORG level during installation and are passed on to child levels. When you change settings in the configuration table, you can also do this on an enterprise-wide basis on the ORG level and pass the values on generally or specifically. This makes the DSM environment much easier to manage.

organization tree

Central management instrument for the client management in the DSM Console; the organization tree can take over data from other directory services (e.g. Active Directory).

organizational unit

Part of the organization tree in the DSM Console. The organizational unit (OU) can be taken over from an external directory service (Active Directory). OUs allow to map sublevels of an organization; they can be nested.

package

A package contains the data required to install software or to perform other administrative tasks on one installation target or on several installation targets. Depending on the type of package this includes for example, files, scripts and settings for customizing the installation. Package is an umbrella term for specific package types such as automation package, MSI Package, Driver Package or Patch Package. All packages are subject to revisioning.

package directory

Directory on a depot where the package files are stored. The package directory is uniquely identified by means of an automatically assigned package ID.

package distribution

Distribution of the package files. The target and time of the package distribution can be specified in detail.

package files

All files of a package in the repository. This includes the installation files, the script and the registry extension files. Package files can be stored compressed or not compressed in the repositories.

package revision

Specific instance of a package; standard revision is always the highest released revision.

Packaging Manager

Predefined role for managing organizational data in the DSMC. The role owners have the rights to create and customize packages within the software library.

Packaging Workbench

With the Packaging Workbench package contents can be edited. This includes scripts for which there is a very powerful scripting language.

Pipe Installer

The Named Pipe Installer is a component of the Installer the DSM Runtime Service starts during execution of packages in user context (with the AutoInstaller or Software Shop) to execute commands classified as "per Service" in a privileged mode. The commands are forwarded to the Named Pipe Installer via a named pipe which is set up for this purpose.

platform

Package property which specifies the operating systems on which a package can be executed.

policy

A policy is an assignment of a package to an installation target. A policy instance will be created for each individual target (computer). A policy is a valid rule for a specific target.

policy instance

A rule derived from a policy for an individual computer. Depending on the requirements, a policy can be customized individually.

policy type

The policy type specifies the type of execution for a policy. The following types exist: Standard (automatic installation) Shop (interactive installation) Job (recurring or event triggered installation) Deny (Denied installation)

polling interval

During the polling interval an active component checks the status of specific data. The DSM Suite features polling intervals for the Distribution Service or the DSM Agent, for example.

Primary Business Logic Server

Server application of HEAT DSM on the Central Management Point. During runtime, the Primary BLS serves as a 'normal' Management Point. When the DSM environment is updated, this server is updated before all other Management Points. The DSMDB is updated on the Primary BLS and the System Object Import also runs on the Primary BLS. Some ICDB settings can only be specified on the Primary BLS.

primary executable

One of the entry points of a virtual application. Contains the ThinApp runtime.

primary site

The site a managed computer is assigned to due to its site definition at startup. If there is no depot available in the primary site, DSM tries to assign the computer to a neighboring site (if defined).

priority

Specifies the priority of a policy if there are multiple assignments for the same package on a managed computer (highest priotity = lowest number).

private key

For security reasons, passwords which are used on Management Points are encrypted with an AES 256 key that is generated by using a public key. A private key is required for decryption. Both public and private key are generated when configuring the DSM environment and are only valid within this specific environment.

Product Manager

Predefined role for managing organizational data in the DSMC. The role owners have the right to assign packages.

Quality Manager

Predefined role for managing organizational data in the DSMC. The role owners have the right to assign packages that are not yet released for a pilot installation. Also, Quality Managers can release packages that have passed the test.

range of action

Domains, OUs, groups or software folders are also ranges of action for which specific users are assigned to a role. These permissions apply to all subordinate objects of the organization tree.

region

Structural element in the navigation window of the DSM Console, part of the infrastructure (site structure). Regions allow you to display your company's sublevels; they can be nested. Using regions is optional.

registry editor

Specific dialog in the Packaging Workbench where registry files (.REG and .NIR) can be edited.

Relay Proxy

HEAT DSM server application on a Management Point which can be employed as an alternative to a Business Logic Server (BLS). In contrast to a BLS, a Relay Proxy does not require a database. Instead, the Relay Proxy forwards the synchronization requests of the managed computers to the BLS.

release

Releasing finalizes the packaging process; it is the final step before a package (or a specific revision of a package) can be assigned and installed.

release status

Editing status of a package. This property is linked to the individual revision. The following status exist: under construction, released, retired.

remote site

Site type for managed computers which are connected to the depot via a slow network connection (e.g. RAS). The computer typically only accesses a small repository containing, for example, specific customization scripts or updates via the remote site. The packages in these repositories can be provided in a compressed form to reduce the installation time.

repository

Logical storage for packages within the site structure. The physical location is on the depot to which the repository is assigned to in the site structure. See also: master repository

Repository Cache

Local directory on a managed computer where installation data is stored for packages with activated staging.

revision number

Current number of a package's revision.

right

Permission to execute specific tasks on a computer system or domain. Applies generally to the administration of computers in networks and also for the role-based concept of the DSM Console: The right to perform certain tasks in HEAT DSM is assigned individual roles in the framework of the role-based concept. Therefore, a task can only be performed if the DSMC user is the owner of a role to which the right to perform this task is assigned.

role

A role in the DSM Console combines the necessary rights to execute different management tasks. Individual users can be assigned to a role as role owners; they can be defined variably per range of action. In addition to predefined system roles individual new roles can also be created.

role owner

User or user group a specific role has been assigned to.

rollout

In software deployment, rollout refers to the process of publishing and distributing software products to the respective clients.

runtime variables

Variables created automatically by packages which are only valid during a package's runtime (when the package is executed).

sandbox

File that holds the runtime modifications of the virtual application (application settings, user documents.

secondary executable

Secondary executables are entry points of a virtual environment. They can only run together with the primary executable. Secondary and primary executable share a common virtual registry and file system, and can interact with each other.

security key

During the installation of HEAT DSM, you can enter a security key which prevents misuse of the DSM services.

server

DSM employs various infrastructure servers for managing a network (for example, Management Point, database server, depot etc.). These servers usually have a server operating system. At the same time. computers with a server operating system can also be used as managed computers in DSM.

server components

DSM server components are grouped together in the Management Point. See also: Management Point

Service Installation Service

The Service Installation Service (SIS) ensures that the DSM client components are installed reliably; it is installed as an application on a Management Point.

Service Installer

The Service Installer is an instance of the Installer which is running in the background. It is used to pre-install the user-independent computer portion of a package with administrator rights.

service-oriented architecture

Technology standard which ensures an individual and flexible integration of software in existing business processes.

SID

Security Identifier. The SID is unique; it prevents the same SID from existing twice in the same network.

site

Logical group of depots and managed computers. All depots in a site provide identical resources. During the DSM Client's runtime, each managed computer will be assigned to its site and accesses its resources. The criteria for the site membership of the client are, for example, the network address or the computer name (site definition).

site definition

The site definition contains the criteria determining which site a managed computer is assigned to, for example the network address or the computer name.

site group

Group of site objects (regions or sites) which are treated as one unit during the distribution of package files.

site structure

Arrangement of the sites in a hierarchical structure which consists of the ORG (organization) and regions.

site type

DSM provides three site types: LAN site, remote site and offline site. The different site types allow different actions on the managed computer depending on the network status: Depending on whether the client is connected directly with the company network or via RAS, or working offline, the settings of the respective site type become effective and the respective action is executed.

snippet

Snippets are command sequences in the Packaging Workbench that can be inserted in an eScript and can be edited separately. Some snippets automatically come with DSM (System Snippets) and some snippets are user-defined, they are either available to all DSMC users (Common Snippets) or they are only stored in an individual user's profile (My Snippets).

SOAP protocol

The Simple Object Access Protocol is a platform-independent communication protocol. DSM's service-oriented architecture (SOA) is based on this protocol.

software category

Logical group of packages which can be assigned to any number of categories.

software deployment

Software deployment features the installation, integration, maintenance and uninstallation of software. It also includes the distribution of software to several computers over a company network, for example.

Software Factory

The software factory combines all wizards in the DSMC that assist with creating different packages.

software folder

Software folders structurize the software library. A package can only be assigned to one software folder.

software library

The software library is a hierarchical directory structure in the DSMC where all packages and software sets are stored and where they can be edited.

software lifecycle

Process or lifecycle of a software package which includes the following steps, for example: creating, testing and pilot installation of a package. The Software Lifecycle has its own view in the DSMC.

Software Manager

Predefined role for managing organizational data in the DSMC. The role owners have the right to control the software regarding installation, licenses etc.

Software Packaging

Proven NetInstall technology featuring the software factory and packaging workbench with intuitive wizards that facilitate the creation of all types of package ranging from operating systems and applications to system configurations and drivers in no time at all. Processes and best practices are set up just once, and existing software packages are automatically adapted for use in desktop, server, and virtual environments. This ability to build once and then deploy across the entire network allows for consistent, repeatable deployments with essentially a 100% guarantee that every machine will look the same.

Software Set

A software set combines different packages in a set (unit). A software cannot contain other software sets. Specific software sets for OSD or Citrix are called OS installation set or Citrix Installation Set.

software set component

Part of a software set; must be a package.

software set revision

Instance of a software set; the standard revision is the highest released revision.

Software Shop

User interface that allows the end user to self-install and repair software the administrator assigned via shop entry.

Software Virtualization

Software virtualization is one of the three types of virtualization the DSM environment supports. Here, individual applications are virtualized.

staging

Staging comprises the intelligently controlled download of installation data to managed computers and the management of this data, independent of the actual installation. Keeps network load to a minimum.

static group

A group in the organization tree computers and users are statically assigned to.

status data

The current state of an installation target and the respective desired state are stored in the DSMDB. This status data can be used for the Compliance Report (to evaluate the work progress in the DSMC).

status file

Indicates the distribution status of a package. The status file is called 'Project.status' or 'CompProject.status' and is located in the root of the package directory. The status file is created when a package is released for the first time. It is updated during a re-release. The update triggers a new distribution of the program.

Supervisor

Predefined role for managing organizational data in the DSMC. The role owners have the privilege of executing all tasks; this role cannot be changed or deleted.

task

A task is an action within the framework of Lifecycle Management. In the DSM Console, tasks can only be executed with specific rights. This allows administrators to implement role-based permission concepts.

Terminal Server

A computer with a server operating system where the terminal services are running. A Terminal Server provides the user interface and the applications for thin clients (terminals).

Thin Client

In client/server applications, a client designed to be especially small so that the bulk of the data processing occurs on the server.

ThinApp

VMware ThinApp' is used by DSM for the virtualization of applications. The installation of ThinApp is fully integrated into the DSM installation but it requires a separate license.

ThinApp application

Virtual application built by ThinApp.

ThinApp data container

Contains mass data of large virtual applications. Icons and entry points to the data container are attached to a small executable file.

ThinApp Package

Package type that contains source data and executables of a ThinApp virtual application.

ThinApp shortcut

For each entry point of a virtual application a shortcut is configured during the build process which creates a link in the start menu of the host computer at the application's runtime.

Transport Layer

HEAT DSM server application on a Management Point which allows for communication between Management Points in different network segments, in particular when they are protected.

Traveling User Support

Automatic post-installation of software installations when the user switches computers.

uninstall information

By default, the Installer writes uninstall information for all installed packages to the managed computer's registry. This information allows for the uninstallation of packages even if, for example, files are shared by various applications (and are therefore installed several times).

Universal Script Package

Universal script packages are used mainly for the Linux support of HEAT DSM. They basically show the same behavior as the Post OS Action Packages. The main difference is that they have platform settings. Installation targets must have an operating system that matches the package in the Basic Inventory, so that the system can create policy instances after the assignment. USPs do not have user and computer portions.

Universal Software Set

Universal Script Packages can be combined in a Universal Software Set, analogous to the usual Software Sets. They are used mainly for the Linux support of HEAT DSM.

unmanaged computer

A computer that is not managed via HEAT DSM and that does not have any DSM client components; it can be displayed in the DSMC, however.

Update Manager

When updating to a new version of DSM, all of the depots and Management Points must be updated. The Update Manager application manages the entire process.

user

A user in DSM can either be: a) Installation target: The logon accounts of the users that are imported from the Active Directory, for example, or created by AutoInsert; or b) the main user of a computer or a user of DSM modules.

user portion (of an installation)

The portion of the package which is carried out with the help of user-related commands.

user-defined tasks

With user-defined tasks you can include programs and scripts in the DSMC.This extends the functionality of HEAT DSM.For example, this allows you to integrate management consoles from different virtualization providers into the DSM environment.

user-related

Related to the classification of a command or to the logging and installation of the package installation in the registry.

VDI client

With desktop virtualization every user is provided with an individual virtual desktop computer on one or several hosts (servers) in the company's computer center.

Virtual Desktop Infrastructure

A Virtual Desktop Infrastructure (VDI) is a desktop-oriented service that hosts user desktop environments on remote servers and/or blade PCs. (Wikipedia)

virtualization

DSM supports three types of virtualization: Application Virtualization, Hardware Virtualization, and Desktop Virtualization

Web Service

DSM provides different Web Service components on the Management Points. Clients usually send queries to a Web Service, which returns the required information. Web Services are based on the service-oriented architecture (SOA).

Windows Management Instrumentation

Windows Management Instrumentation. Interface for Management Applications, used for reading hardware, software and operating system data from Windows computers.

Windows Script

Script that is executed by the Windows Script Host.

work directory

Directory which serves as the source for distribution and, if necessary, as the target for distribution from the parent object. Every master depot contains a working directory ( \work ), where the copies of the repositories are saved.