To insert a new package:

1. Mark the respective tab and select Insert > Package…
2. If you answer the prompt with Yes, you must enter the path to Setup.inf. If you select No, you must enter the package properties yourself.
3. Modify your settings in the respective tabs.
4. Click Apply and/or OK.
5. After clicking OK you can decide whether you want prepare the package for validation. In this case the data will be stored to the database immediately.

Package Properties – View

Allows users to edit the view of package properties.

• Ready to install

Each newly added package must be released here after successful testing, before the package can be distributed ((Ready to install=1). If this checkbox is not checked (Ready to install=0, package is displayed in brown color), it can only be distributed to computers, where the computer variable READYTOINSTALL_TEST is set to one (1). The installation call is written into the respective DDC file, depending on the computer variable READYTOINSTALL_TEST=0 | 1. This means:

0 = don’t write into the DDC file.

1 = write into the respective DDC file of the computer.

• Name

Specifies the internal name of a package. This name has to be unique within the software depot. No other object must have the same name (tab or package).

• Text

Specifies the text the user will see. This text is arbitrary.

• Icon

Shows the icon which is displayed in the package list.

• Change icon…

Opens a dialog box which permits you to select an icon.

• Docu file

It is possible to provide a documentation (TXT/DOC/HTML/&) for each package, which can be viewed under Manager by right-clicking on a package > Documentation.

• Info file

Specifies the name of the file which contains additional information on the package, for instance, licensing terms and conditions, etc. The user can retrieve this information in the software depot by clicking the Info button. The file can either consist of plain text (as created by the text editor) or rich text format (as created by WordPad).

• Edit icon

Opens the info file to edit it either in the Editor or in WordPad.

• Browse icon (open folder)

Opens a dialog box which allows you to browse for a file name.

Package Properties – Version

Edits the version of a package.

• Version

Specifies the version number as it is shown in the package list as "Version (available)". Provided it is larger than 0, the revision number is inserted after the version number. The first character must be a number. A version number may contain letters after the dot, but not a character string or spaces. Instead of the version number (e.g. "4.0"), a file containing version information can be specified via Version file. From this file, the version information will be read.

• Revision

Specifies the revision number as it is shown in the package list as "Version (available)". Provided it is larger than 0, the revision number will be added to the version number. For the Configurator setup program, an increase of the revision number does not necessitate a re-installation of the entire application. For this reason, the revision number should always be increased after minor changes, such as the replacement of a file. As a revision, only a integer value can be used.

• Version file

Alternatively, you can specify the file from which the version and revision number will be read if the file contains version information (e.g. MSOffice.exe). If a version file is defined, both the Version and Revision field can remain empty. Behind the file name, you can also enter additional flags separated by a comma (several flags are separated by a space):

• Browse icon

Opens a dialog box which allows you to browse for a file name.

• Sequence

Specifies the installation sequence of the selected package and the package(s) defined in the Sequence dialog box. This option allows you, for instance, to define that the full version of a software has to be installed on the computer before the installation of a software update.

• Define

Opens a dialog box which allows you to define the installation sequence. (see Defining an Installation Sequence dialog).

• Dependencies

Lists the package(s) the selected package depends on. If the dependent package is not installed and/or no distribution command has been created for the dependent package, the selected package will not be installed.

Here, you can also define true dependencies. Several package keys have to be entered and connected with logical operators. Please note that you can use parentheses. The operators are:

• & = AND
• | = OR
• ! = NOT

Example: ("Helios\Textpad\4.5" | "Matrix42\EmpInventory\12.1" ) & ! "NicoMak\Winzip"

• Define

Opens a dialog box which allows you to define the dependencies (see Defining Dependencies).

Package Properties – Check

Specifies the name of a file that the UEM agent uses to determine whether the package on the server has changed and needs to be downloaded again. This value can also be addressed as %Check% within the package properties.

UEM agents from version 2510.1.2 onwards use the file "_Matrix42FileInfo.json" contained in the package as a fixed check file, provided that the option "Validate packages before installation" is set in the agent configuration. This ensures that all changes to the package files are always detected, as this file is renewed after each "Preparation for validation".

• Checkfile

Specifies the name of a file or directory for which a user needs read access rights to install the package. If the value is empty, all strings of the command will be checked. If the Command consists of a call with several parameters (file names), it is more convenient to enter a value under Check, since it is not necessary to check all parameters in this case. This value can also be addressed as the variable %Check% within the package properties. If the software depot is started via a file on an FTP server, this parameter specifies the self-extracting file that will execute the installation. In this case, the user also has to have read access rights for this file.

• Browse icon

Opens a dialog box that allows you to browse for the file to be checked.

• Checkval

Specifies a key or value from the registry required for the installation of the application. If a value is defined, it will be checked in addition to the check file.

• Registry icon

Opens a dialog box that allows you to browse for the registration key to be checked.

• Script

Specifies the complete path to the installation description file (Setup.inf) for this package and is required for the new Empirum Agent. From this path the package is transferred into the local cache.

• Command

Specifies the command (command line) that starts the installation. This command normally activates the setup program. A command may contain double inverted commas to call file names with spaces. During the process of activation, the software depot tries to wait until the command is finished before it invokes the next command. In some cases, however, a command starts another command and returns immediately. In that case, the software depot is unable to wait.

• Search icon

Opens a dialog box to search the command if the field under Command is empty.

Package Properties – Registry

Edits the registry properties of a package. The properties specify where the information is stored on the local computer, whether a specific package is installed or not. Since installation programs of other vendors can also be activated in the software depot, the storage place is not defined in the Setup.inf file, as is the case with the Configurator setup.

• Key

Specifies the key in the registry (below HKEY_LOCAL_MACHINE\Software) where the version number of an application is stored. You always have to define the parent key (e.g. Microsoft\Office), where the version number is to be found. If the version number is not indicated within a key, but in a value, the value name (e. g. Novell, CurrentVersion) has to be specified as well. If the key name includes a comma, the whole key has to be included in double inverted commas. Instead of the registry database, you can also use the version number of a file by specifying the version file.

• Version file

Alternatively, you may specify the file from which the version number for the installed file should be read. This option can be used as an alternative to the key. If a version file is specified, you can leave the Key field empty. In that case, however, the file has to contain valid version information. In addition, the destination directory should be specified. If that directory is not specified, the system looks for the file as a DLL. If the file is still not found, the system looks for the appropriate key for EXE files in the registry (HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths) and uses the complete path name from there. Behind the file name, you can use additional flags separated by a comma (several flags are separated by a space). They are identical to the ones on the Version tab > Version file in the Package Properties dialog box.

Example:

ProductFile = Acrd32.exe

• Search icon

Opens a dialog box that allows you to browse for a file name.

Package Properties – Info

Information on the software package is read in from the file Setup.inf. Any changes must be made directly in the respective Setup.inf file. To update this information, select Extras > Check Versions…

• Author

Specifies the author of the software package.

• Creation Date

Indicates the date when the software package was created.

• Inventory ID

Indicates the inventory ID assigned to the software package.

• Description

Gives a description of the software package.

• Method

Specifies the method with which the software package was created, e.g. via a Setup.inf or MSI.

• Tested-OS

Indicates the operating system with which the software package was tested.

• Dependencies

Specifies the dependencies of the software package.

• Command line

Indicates the parameters that have to be called for the installation of the software package.

• Last change

Indicates the date when the software package was changed.

• Build

Specifies a build number assigned to the software package, which can, for instance, be used in order to indicate changes to the software package.

Package Properties – Application Usage Tracking

The Application Usage Tracking (AUT) feature logs the usage of individual software components on the various clients. The captured data can be displayed as a report or in the interface of the Matrix42 Management Console (module Manager > right-click a computer > Properties… > AUT tab). This allows for the efficient planning of software licenses. The reports help the administrator to find out, how much a program (e.g., Microsoft Excel) or a software package (e.g., Microsoft Office) is used on the individual clients to avoid unnecessary license purchases.

AUT records, when a user has used a program for the last time, how long the program has been used overall (runtime) and how long the user has been actively using this program or package, to which the program belongs. Data are captured via so-called Windows hooks, i.e., functions that the system calls up in case of certain events. The functions are defined in the Empaut.dll library and are called up in case a top level window (event message in a shell application) are created or destroyed or a window is activated or deactivated.

• Name

Name of the file (*.exe), whose processor time shall be determined.

• Version

Version information, which is read from the file.

• Size

Size (in Byte) of the specified file, which is entered automatically.

• Add button

Opens a dialog box to search for a file.

• Remove button

Deletes the selected entry/entries.

Package Properties – Variables

Variables can be defined for a package, which are then displayed here for information and assignment purposes. (In a Setup.inf file, these must be defined in the [VarDefInfo] section, otherwise messages will appear during version check.) These variables can be assigned corresponding values directly via the Manager module for groups, computers, or users and used in the package.

• Variable

This is the name of the package variable. It has to be specified in the Setup.inf.

• Type

Specifies the variable type, which may either be a user or a computer variable.

• Allow null values

Here you can find out if this variable may be empty or not.

Package Properties – Conditions

Displays the settings of the conditions for the package to be installed.

• min. Processor Speed (in MHz)

Enter the processor speed (in MHz) that is required as a minimum in order to install the package.

• min. Memory (in MB)

Enter the memory (in MB) that is required as a minimum in order to install the package.

• min. Disk Space on System Drive (in MB)

Enter the disk space on the system drive (in MB) that is required as a minimum in order to install the package.

• min. Disk Space on Application Drive (in MB)

Enter the disk space on the program drive (in MB) that is required as a minimum in order to install the package.

• Advanced...

Here you can define package preconditions and already installed conditions.

These defined conditions are checked by the UEM Agent in every polling on the client. If the conditions are not fulfilled, no download and no installation of the corresponding package takes place. This prevents an unnecessary download of the package to the client. This check also takes place when installing a package from the Software Kiosk.

Detailed information and configuration examples can be found here...

Package Properties – Operating System

Edits the operating system settings of a package.

• Windows

Specifies that the package is visible when the software depot is executed on a computer with a Windows operating system. You have the option to further restrict the visibility of the listed operating systems (Windows 7, Windows 8, Windows 10, Windows 11, Windows Server 2008 R2, Windows Server 2012/R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025) and of the platform (32-bit = x86 and 64-bit = x64).

• Linux

Specifies that the package is visible when the software depot (specific version) is executed on a computer with a Linux operating system. You have the option to further restrict the visibility of the platform (32-bit = x86 and 64-bit = x64).

• Mac OS X

Specifies that the package is visible when the software depot (specific version) is executed on a computer with a Mac OS X operating system. You have the option to further restrict the visibility of the listed operating systems.

Package Properties – Misc

Edits the miscellaneous settings of a package.

• External installation program

Specifies whether the installation program (in most cases Setup.exe), that has to be invoked for the installation, is the Configurator setup. If this is the case, certain parameters may be appended to the setup call in a specific mode, which might not be understood by other setup programs. Such a parameter is used, for example, in the silent setup mode of the software depot. In this case, no interaction with the user takes place. For this purpose, the software depot has to know how the installation program has to be launched. If an external setup program is always used, this box should be checked. The command for the setup program to install the package is specified under Package Properties – Check.

• Call installation program asynchronously

Specifies whether the setup program is to be called asynchronously. In this case, the software depot does not wait for the setup program to terminate, but rather continues immediately with the next installation. That means, however, that the software depot cannot determine whether the installation was successful. This option is only required if the Setup service itself is to be distributed. The service cannot be replaced as long as it is still running, i.e. as long as it is waiting for the termination of the installation.

• Use for distribution only

Indicates that the package is only used for software distribution. It is not visible in the normal software kiosk, regardless of permissions. An exception is when the distribution flag "Optional" is set and the agent template option ""Show optional assigned Packages in Kiosk" is set. In this case, the package is displayed and can be installed by the user.

• Allow uninstallation

Specifies whether the package may be uninstalled. The Uninstall button in the software depot becomes available.

• Discontinue installation of other packages

Specifies that after the installation of this package the installation of additional packages will be discontinued. This may be necessary if a reboot has to be performed in the meantime. This option can be overwritten with the value Reboot=5 / SetReboot 5 within the Setup.inf of a package. Reboot=5 / SetReboot 5 will discontinue the installation sequence and initiate a reboot.

• Install context

Specifies how the software package is to be launched on the client: via software depot as a service or as task.

• Always

The package is always launched.

• After user login only

The package is only launched if a user has logged in.

• Before user login only

The package is only launched if no user has logged in yet.

• Installation duration (in min.)

Specifies the approximate installation duration (determined by you) of the software package in minutes.

• Reboot required

Specifies wether a reboot is required after installation.

• No

No reboot is required after installing the package.

• Yes

A reboot is required after installing the package.

• Possible

A reboot may be required after installing the package.

• Licenses

Specifies the number of licenses existing in the company for the software of the package.

• Sync Bandwidth

Defines the minimum bandwidth required to allow synchronization with the Empirum server.

• Min. Bandwidth (Kbit/s)

Specifies the minimum bandwidth in kbps required to carry out a synchronization.

• Package type

This setting is only used for synchronization with the Matrix42 Workspace Management.

• General

This is the default setting for all existing and all new packages. No template is required for one of these packages.

• Infrastructure

An infrastructure template is required for this package type; it must be synchronized together with this package.

• Advanced Agent

An Advanced Agent template is required for this package type; it must be synchronized together with this package.

• Patch Management

A Patch Management class is required for this package type; it must be synchronized together with this package.