Skip to main content
Matrix42 Self-Service Help Center


Change from v.7.3.1! The OS Deployments section has been completely reworked.

The "OSD" window displays all OSDs created in the EM.

The first step of creating a new OS deployment is to select on which computers the deployment shall be applied, which OSD configuration shall be used (OSD configurations are created in  EM under Packages - OSD).

As of version 7.3.1, the time limitation and the start mode are no longer applicable.


In the second step you can optionally add one or more EM rollout plans. These are executed directly after the rollout plans that are part of the OSD configuration.

Step three determines when the packages used by the task sequence are downloaded before or for execution.

In the fourth and last step you must specify who is allowed to view the OSD in the EM console.

The task is saved in the background after pressing "OK" in the user interface. For this, a hash is calculated, which consists of the ID of the task sequence and the parameter Download (see Step 3). This value will later be used to create the collection and the advertisement. 

Non-existent computer objects are created both in EM and in SCCM with the corresponding MAC or UUID address. In addition, the PXE flag is removed from the SCCM computer object if one exists. The variables that are additionally stored in the EM are stored in SCCM directly on the computer object.

A collection is then created in SCCM (unless it already exists). The computer object is then added as a Direct Membership Rule.

SCCM Collection.JPG

The SCCM Advertisement is only created if it is not already available.

A collection with a hash value is created when there is a new Task Sequence or another download mode. These two factors are responsible for creating a collection with a hash value. 

As of version 7.3.2, the check mark "Use incremental updates for this collection" is no longer set by default in the SCCM Collection. However, it can be set manually, depending on the customer's needs!

Collection Properties.jpg

This has the following effect on the creation of an EM OSD order:

  • The SQL database is not unnecessarily annoyed with queries per job
  • Computer objects already known in SCCM are automatically included in the collection
  • Unknown / new computer objects are only added to the collection after manual update (Update membership). If the check mark is set, this also happens automatically!

An EM Task is only optionally created if EM rollout plans are available through the OSD configuration or through the selection in Step 2. In addition to a better overview and determination, the SCCM Collection ID and Advertisement ID are displayed.

OSD Task Status.JPG

Status Calculation

First, the status of the SCCM job for the existing computer objects is determined.  This is done via a database query on the view <<Sitecode>>_ClientAdvertisementStatus . The status values are read out and converted into an EM format.

EM Status.JPG

Succeed = Successful and the computer object is removed from the SCCM collection (collection remains in place).

Failed = Incorrect and the computer object is removed from the SCCM Collection (Collection remains unchanged).

Waiting, Running, Retrying and Rebbot pending = Deployment is running and the computer object remains in the SCCM Collection.


Then the EM Task status is queried when the computer object is finished with the SCCM Task (Task Sequence).

If both tasks are completed successfully, the computer object will be displayed as Successful in the OSD Task. If a task of both is faulty, it will be categorized as faulty.

  • Was this article helpful?