Skip to main content
Matrix42 Self-Service Help Center

HowTo: Subdepot and OS Deployment with Client Management (Empirum) SaaS


To use the OS Deployment with Client Management (Empirum) SaaS, a subdepot is required in the customer network. This document describes the necessary steps to set up and configure a subdepot for successful communication with the SaaS service and the current limitations of the OS deployment.

Deploy the Subdepot

Install the latest UEM Agent on the Subdepot server. A step-by-step description can be found here. The Subdepot server must be assigned to a configuration group, which must also be assigned at least the following software packages and objects:

  • Empirum Subdepot
  • Empirum Subdepot PXE Service (if OS deployment is required)
  • Matrix42 UEM Agent Windows
  • the correct Agent Template to communicate with the SaaS Environment

Configure the Variables (Variable Configurations)

  • SUBDEPOT_SERVICES (if OS deployment is required)

Your configuration group will look something like this:

For a detailed description of UEM Agent-based subdepot sync functionality, see the UEM Agent documentation.

Activate and install the software packages.

Preparation of OS Sources and Boot-images

OS Sources

In the Empirum Packaging Center you will find a button called Prepackged OS Wizard. You can install the Empirum Packaging Center on any computer and start the Prepackged OS Wizard without connecting to the Empirum server, database or Internet. Start the wizard to save operating system sources and importable language packages (Empirum software package format) locally. Then the Empirum-compliant format can be imported via the SDK or the created ZIP file can uploaded via the UUX Package upload wizard.

Currently it is not possible to upload and import sources for the Windows Feature Update packages. Please open a ticket in our Support Portal or send an email to The support team will provide you with an upload link where you can send the sources, then the support team will import the sources into your SaaS environment.


The Windows Assessment and Deployment Kit (WADK) is already installed (and imported) on the Master server. You can start configuring and creating the Boot Configuration directly.

Offline Boot Media creation is possible only for ISO file creation.
"Enable Self Provisioning" is possible only when the API server is added in the boot image.

If the boot-image requires custom drivers, they can be uploaded to using the WebDAV protocol. The process is identical to uploading Software packages.

The Matrix42 WinPE Driver Assistant can be accessed via the Matrix42 Management Console (EMC). You can find the Driver Assistant for Windows drivers as a button under Configuration on the left side.


  • Was this article helpful?