Documentation for SCCM task sequence deployment orchestrator


What is sccmtspsi? 

sccmtspsi is an SCCM task sequence deployment orchestrator used by organisations to manage the deployment of operating system task sequences. Reduces use of complex scripts, increases SOE build success, Agile release of task sequence deployments, prevents data loss and creates a repeatable & easily documented SOE environment.

What does it do? 

  • Automatically identify the device name or set a computer name during the Task Sequence. Set computer name prefix, suffix and case.
  • Create and use selection profiles for SCCM applications, SCCM collections, Active Directory groups.
  • Unlock Bitlocker automatically from within the Task Sequence: Active Directory, MBAM, key or password.
  • Select one of the many Task Sequence deployments using the sccmtspsi user interface.
  • Select from a list of Operating System Images and Packages available within the selected Task Sequence.
  • Select your preferred Office Suite Application from a list of Office Suite SCCM Applications.
  • Select one or more SCCM Applications from a list of available SCCM Applications.
  • Add the machine to one or more SCCM Collections from a list of available SCCM Collections.
  • Add the machine to one or more Active Directory Groups from a list of available Active Directory Groups.
  • Select the User State Migration (USMT) method: Hardlink, USB, Network.
  • Format the disk to recommended standards for Legacy and UEFI BIOS.
  • Add data volumes with drive letters to the selected disk.
  • Select one or more primary users for the device.
  • Select from 18 extension attributes with the potential to direct the task sequence in multiple paths.
  • Using the decommission feature to decommission a device securely.
  • Set supported hardware models.

Is it easy to setup?

This page is a comprehensive step-by-step image-led documentation for the orchestrator.

Step 1: Download and install the sccmtspsi components ZIP file. Click here.

Step 2: The free license token is in the above ZIP file.

Step 3 Create a customized WinPE image using the WinPE customizer. Click here.

Step 4: Create a configuration file. Click here.

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.