Skip to main content
Matrix42 Self-Service Help Center

UEM Depot Management

General

The new UEM Depot Management offers a new UEM Depot Sync based on the Matrix42 Universal Agent Framework. With this framework, synchronization can now be performed via SMB as well as via HTTP(S).

The final status of the last synchronization can be viewed for each run in the EMC in the tab "Empirum Server Monitor".

Synchronizations, which sometimes have a longer runtime, send an additional information about the start of the sync run. For more information, see Available synchronizations.

Installation

For the initial setup of the UEM Depot Sync the following steps have to be performed:

  • Configure the server as a subdepot
    • Computer properties > Computer role > Empirum Depot Server
  • Installing the UEM Agent
  • Configure variables
    • SUBDEPOT > ROOTPATH
    • SUBDEPOT > USER_1
    • SUBDEPOT > PASSWORD_1
  • Install the current version of the "Empirum Subdepot" package on the server (create the directories and set the access rights)
  • Configuring the Sync Jobs

Configuration

The UEM Depot Sync can be configured using variables. A detailed description of the variables can be found here. The Sync Jobs described below are supported.

It is recommended not to let the agent poll the depots too often, as this will lead to an increased load on the system. It is recommended to set an interval of at least 60 minutes.

Available synchronizations

CLIENTDATA

This Sync job configures the synchronization of the client data directories EmpInv and Log.

CONFIGURATIONDATA

This Sync Job configures the synchronization of the configuration data like DDC, DDS, INI, Configuration/User. Only the DDC and INI files of the computers that are assigned to the Subdepot are synchronized.

OS_CONFIGDATA

This Sync job configures the synchronization of the OS metadata. Only the OS metadata of the computers that are assigned to the Subdepot will be synchronized.

Additionally, the file DeviceMappings.xml is copied to the Values folder.

OS_IMAGEDATA

This Sync job configures the synchronization of the OS images.

The start of the run is transmitted at the beginning.

PACKAGES

This sync job configures the synchronization of the package directory.

The start of the run is transmitted at the beginning.

To speed up the matching of packages from source and target, the sync job uses the PackageHashes.json (see section Validation of packages before installation) During synchronization, the job checks whether a package is listed in the PackageHashes.json and whether the stored hash values of source and target match. If they are identical, no files are copied. If they differ, the package is synchronized. All packages that are not listed in PackageHashes.json are synchronized.

 

If a package listed in the PackageHashes.json is changed in the target directory (e.g. files are deleted or edited), this change will not be detected by the check of the saved hash value and there will be no synchronization to the source directory!

PATCHES

This sync job configures the synchronization of the patch directory.

The start of the run is transmitted at the beginning.

Exclude directories

Using the SYNC_*_EXCLUDED_FOLDERS variable, directories can be excluded from the sync. The syntax rules described below apply here.

The following directory and file structure are assumed for the examples:

ROOT\

Test1.txt

TEMP1\Folder1\Test1.txt

TEMP2\TEMP1\Folder2\Test2.png

TEMP3\TEMP1\Folder1\Test2.txt

Rule 1: Backslash \ for relative paths

If a directory starts with a backslash \ , the excluded path is relative to the Sync Root Folder (see variable ROOTPATH). Otherwise, all folders containing this part of the path are excluded.

Example

  • "\TEMP1\Folder1" will only exclude the folder "ROOT\TEMP1\Folder1" and the "Test1.txt" inside.
  • "TEMP1\Folder1", on the other hand, will exclude all "Folder1" that are located under the root directory "ROOT", but also under all subdirectories and have "TEMP1" as their parent folder.
    • Specifically, the folders "ROOT\TEMP1\Folder1" and "ROOT\TEMP3\TEMP1\Folder1" and the files they contain would be excluded.
Rule 2: Filtering with wildcards * You can use * to specify placeholders for folders.

Example

  • "\*\TEMP1" would exclude the folders "ROOT\TEMP2\TEMP1\Folder2", "ROOT\TEMP3\TEMP1\Folder1" and all files contained in them.
    • Specifically, the folders "ROOT\TEMP1\Folder1" and "ROOT\TEMP3\TEMP1\Folder1" and the files they contain would be excluded.

Exclude files

Files can be excluded from the sync using the SYNC_*_EXCLUDED_FILES variable. The syntax rules described below apply here.

For the examples the directory and file structure of section Exclude directories is assumed.

Rule 1: Backslash \ for relative paths

If a directory or file starts with a backslash \, the excluded path is relative to the Sync Root Folder (see variable ROOTPATH). Otherwise, all files containing this part of the path are excluded.

Example

  • "\Test1.txt" will only exclude the file "Test1.txt" in "ROOT.
  • "\TEMP1\Folder1\Test1.txt" will only exclude the file under "ROOT\TEMP1\Folder1\Test1.txt.
  • "Test1.txt" would exclude all files "Test1.txt" below "ROOT" and its subdirectories. Specifically, the files "ROOT\Test1.txt" and "ROOT\TEMP1\Folder1\Test1.txt" would be excluded.
Rule 2: filtering with wildcards *

You can use * to specify placeholders for files.

Example

  • Using "*.txt" would exclude the files "ROOT\Test1.txt", "ROOT\TEMP1\Folder1\Test1.txt" and "ROOT\TEMP3\TEMP1\Folder1\Test2.txt".
  • Using "Test2.*" would exclude the files "ROOT\TEMP2\TEMP1\Folder2\Test2.png" and "ROOT\TEMP3\TEMP1\Folder1\Test2.txt".

Protocol and Master Server

The protocol and the Master Server are configured by means of an assigned Agent Template: In concrete terms, this means that the agent template of the UEM agent installed on the sub depot is used for the connection to the master server. This also includes the functions of bandwidth throttling and minimum bandwidth.

Open points

The following features are currently not yet supported by UEM Depot Management:

  • Installation time frames are not considered
  • Options in the scheduler:
    • "End after x occurences"
    • "Stop job if the end time is reached"
  • In the log there is always a zero for "Size of target directory".

 

  • Was this article helpful?