Version 4.0

• Support for the new Empirum Depot Topology feature, introduced with Empirum 26.2. See Depot Sync 4.0 Getting Started.
• The following variables in MX42_UEM_DEPOT_MANAGEMENT will no longer be used:
  • SYNC_PACKAGES_EXCLUDED_FILES and SYNC_PACKAGES_EXCLUDED_FOLDERS by the packages and drivers sync as it would interfere with the tag-based synchronization and hash creation.
  • SERVICEBUS_ENABLED because a working Service Bus connection is always required.
  • SERVICEBUS_DISPLAYNAME because it was never used.

Version 3.6

• Increased minimum required UEM Agent version to 2610.1.2
• The packages sync always starts the user sync beforehand and the OSImageData sync always starts the OSConfigData sync. Previously this was only done when starting those syncs manually. (PRB39570)
• UEM Depot Sync calculates an incorrect hash for packages containing files with 8.3 short file names (SFNs) if Subdepot.ROOTFOLDER differs in letter case from the corresponding directory on the file system. (PRB39506)
• The timestamp for the file “_Matrix42FileInfo.json” was incorrect on the repository servers. Although this did not cause any problems, the issue has now been resolved. (PRB39576)
• The user sync will retry the file transfer several times in case of an error. This may prevent failures due to temporary issues (e.g. blocked files).
• Calculation of hashes has been improved the finish much faster.
• Added tab completion for sync job names in the PowerShell cmdlets.

Version 3.5

• Increased minimum required UEM Agent version to 2604.2.2
• Canceled sync jobs are now stopping quicker.
• Using new Service Bus Adapter and RabbitMQ 4.2
• Reduced memory consumption when the server was running a long time.
• When importing a single driver file (ZIP) from a subfolder within the Drivers directory and running a Sync Job, the ZIP files are now correctly retained on the Depot Server. Previously, these files were deleted when the parent folder was not included in the Drivers import scope.
• If the Drivers.json declaration file cannot be downloaded to the Depot Server, the system no longer assumes a full cleanup. Instead, the entire Drivers directory is preserved on the Depot Server to prevent unintended data loss. (PRB39357)
• The synchronization of drivers are split to a dedicated sync job. (PRB39374)
• Under certain circumstances, it was possible that, after a long period of operation, sync jobs would no longer run automatically. (PRB39383)

Version 3.4

• Changes and fixes
  • Increased minimum required UEM Agent version to 2510.2.2
  • Drivers now synchronize much faster using hashes (requires Empirum 25.4 with December 2025 hotfix or later).
  • Improved synchronization status handling for many changed computer files (DDC, INI). (PRB39188)
  • Values sync is more robust in case that the Service Bus does not respond fast enough.
  • Manual stop of a package sync is now faster.
  • Legacy Depot Server log files are not written when Service Bus is used.
  • Synchronization of files with very long paths has been improved.
  • Improved depot synchronization performance by reducing the number of required PROPFIND calls.
  • The UEM Depot Sync is more robust against unusual time formats. (PRB39015)
  • Folders in the exclude list of the packages sync that start with a backslash are now working and interpreted as relative to the packages folder. (PRB38979)
  • Fixed issue with long running package synchronizations. (PRB39094)
• Note
  • Depot sync now preserves essential folders (like SetupErrorLog) for better stability. Reinstall the "Empirum Subdepot" package on depots to guarantee they are available.

Version 3.3

• Legacy sync jobs are not synchronized with new UEM Depot Sync anymore. (They could be reactivated by changing the app.config file).
• Fixed: In rare cases, the version or revision of a package was determined incorrectly during package synchronization if Agent polling was running at the same time. (PRB38854)
• UEM Depot Sync continues package synchronization even if a package download status can not be found. (PRB38965)
• Fixed proxy usage in combination with Azure Service Bus Service. Requires at least Empirum 25.4.0 with Service Bus Adapter 6.9.1. (PRB38406)

Version 3.2

• UEM Depot Sync provides more detailed error information for failed Patch Management sync jobs. (PRB38458)
• Clients were woken up too often if the WOL ran in "offline service mode" on a depot server. (PRB38315)
• The Power Shell Cmdlet Get-SyncJobs has an optional parameter -Name to filter for one or multiple jobs.

Version 3.1

• Patches with download type "manual" will be downloaded by the UEM Depot from the superordinated depot/master server regardless of option "cloud only" in DBUtil. (PRB38300)
• The patches folder in Patch Management is only created on a subdepot when using the M42 Cloud and the associated variables after cleanup. If it does not yet exist during cleanup, synchronization is aborted. (PRB38427)
• Fixed calculation of the next start time when using timeframes.

Version 3.0

• Added periodic check for existence of the configured queue in Rabbit MQ. (PRB38003)
• A message will be shown in the EMC if the DDS or Package Hashes.json are missing for the packages sync.
• Log files which do not match the current naming schema will be deleted.
• OS boot images were not removed on depot.
• The OS.ini files were synced too often by the values sync. (PRB38315)
• Configuration files can now be distributed to all depot servers without dedicated depot server assignment. This feature requires Empirum v24 Update 2, or v23 Update 3. Please take a look at the Empirum help

Version 2.2

• The installed certificate will be used when transferring the Device Mapping.xml to the depot. (PRB38039)
• Values sync is more robust in case of Service Bus delays.
• Reduced number of messages "Job was not executed at scheduled time, because the last scheduled run was less than..."
• An empty clients list is no longer considered to be an error in the Values sync.
• Added periodic check for existence of the configured queue in Rabbit MQ. (PRB38003)

Version 2.1

• The depot sync is now using AMQP Web Socket binding for Service Bus communication. That means only TCP port 443 is required to be open.

Version 2.0

• Significant changes for the meta data syncs. See here for more information about it.
• Improved performance on sync of user DDC and INI files.