UEM Depot Management_OLD

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.

CLIENTDATA

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

PACKAGES

This sync job configures the synchronization of the package directory.

The start time of the run is visible in the log in the Empirum Management Console.

In order 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.

In order to force a complete new hash calculation at the next run, you can set the registry value RenewPackagesHashesOnce:

REG ADD HKLM\SOFTWARE\MATRIX42\ Platform\Service\Extension\ObjectStore\Data 
/v RenewPackagesHashesOnce /t REG_DWORD /d 1 /f

The following folders from the packages folder will not be synchronized:

• Matrix42\EndMessage
• Matrix42\OS-Message
• Matrix42\LinuxAgent
• Matrix42\EmpirumAgent_for_Mac
• Matrix42\InventoryMacOSX
• PatchManagement (Part of the sync Job "Patches")

The following files from the packages folder will not be synchronized:

• Matrix42\SyncJobs\SyncTemplate.inf

PATCHES

This sync job configures the synchronization of the patch directory.

The start of the run is transmitted at the beginning.

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 mass data.

The start time of the run is visible in the log in the Empirum Management Console.
Hashsums will be calculated for operating system mass data. The hashsums are stored in the file "OsProperties.json" in the "\Empirum\EmpInst" folder. They are used for a quicker synchronization and are required for the job to run.
For imported operating systems the (re-)generation of the hashsums can be started from the context menu.

REG ADD HKLM\SOFTWARE\MATRIX42\ Platform\Service\Extension\ObjectStore\Data 
/v RenewOsHashesOnce /t REG_DWORD /d 1 /f

QUICKSYNC

This sync job synchronizes specifically the changed INI (computer/OS) and DDC files which are relevant for a depot and the computers assigned to it.
It can be executed in significantly shorter intervals than CONFIGURATIONDATA and OS_CONFIGDATA, since it is much more performant and resource-saving.

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.

Example for regional depots

Normally, all packages from the software depot are synchronized to all connected depots. If you want to limit the distribution (e.g. programs must not always be available in all languages on all depots worldwide), you can achieve this with the variable SYNC_PACKAGES_EXCLUDED_FOLDERS and a restructuring of the software depot.

Using the example of the program AwesomeTool, it is shown how it can be distributed to subfolders and how the variable should be set for the 3 depots used. Thus only the desired packages are synchronized on the respective depot.

Folder structure
\Server\...\Packages\RegionAfrica\Zimbabwe\Matrix42\AwesomeTool ZW\1.0.42
\Server\...\Packages\RegionEurope\Germany\Matrix42\AwesomeTool DE\1.0.42
\\Server\...\Packages\RegionWorld\Matrix42\AwesomeTool EN\1.0.42

Variable SYNC_PACKAGES_EXCLUDED_FOLDERS
Depot Africa\Zimbabwe: "RegionEurope\Germany | RegionWorld".
Depot Europe\Germany: "RegionAfrica\Zimbabwe | RegionWorld
Depot Worldwide: "RegionAfrica | RegionEurope"

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".