Documentation for SCCM task sequence deployment orchestrator

Get SCCM applications

These are SCCM applications that are categorized with the label  “sccmtspsi-applications-XXX” [Where XXX is the Realm name].

Click on the “Get SCCM applications” button to view a list of applications configured for the Realm. Select an Operating system image or package before selecting an application.

Clicking the “Get SCCM applications” button will open the following panel.

Application setup in SCCM should look similar to the below image.

This panel allows multiple selections to be made. Selections can be made in the following ways.

  • Manual selection.
  • Click the “Load selection from SCCM” button to select the current deployment list.
  • Click the “Load selection from file” button to load a profile file.

An application profile file:

A profile file is a text file with ends with a “.sccmapps” extension. The following images will help understand the concept.

Place the profile files in the profiles directory set in the configuration file.

This process will set the below task sequence variables.




……….. etc …………..

For the above listed example screenshots, the task sequence variables will look similar to the below entries.

SCCMTSPSISET1APP01 = Application Example 2

SCCMTSPSISET1APP02 = Application Example 1

The base variable SCCMTSPSISET1APP and/or SCCMTSPSISET2APP and/or SCCMTSPSISET3APP can then be referenced in the task sequence as depicted in the below image.

In addition to the above SCCM variables the following variables are also set; which can then be used during Full media (Stand alone media) builds.

SCCMTSPSI-APP-PACKAGEID-S0100038-ISSET -> This variable defines that a Application with the PackageID S0100038 was selected by the operator.

Suggest Edit

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.