Task sequence executable

sccmtspsi components

Run the following command line during the following scenarios.

  • It should be the first item of the task sequence (Switch ‘-start’).
  • Before a restart (Without any switches; just to gather logs).
  • After a restart (Without any switches; just to gather logs)..
  • When logs have to be copied to the logging location (Without any switches; just to gather logs)..

Note: Create a package with ‘sccmtspsi-tasksequence.exe’ and also copy into USMT package.

  • After installing the sccmtspsi components (msi) copy the executable ‘sccmtspsi-tasksequence.exe’ (for your architecture) from the following location and create a package.
  • Also copy the executable ‘sccmtspsi-tasksequence.exe’ into the USMT – User state migration tool package root.

After installing the ‘sccmtspsicomponent.msi’, Copy ‘sccmtspsi-tasksequence.exe’ from below location (based on your architecture).

to below location

and to below location (your USMT package directory)

In WinPE – (At the start of the task sequence)

This step initializes the task sequence and should always be the first step of the task sequence.

If the task sequence was initiated from Software center, this step will do the following.

  • Turn off bitlocker.
  • Restart the computer into WinPE.
  • Open the sccmtspsi user interface (Console).

sccmtspsi-tasksequence.exe -start

Anywhere in the task sequence :

just to copy logs to the network location (set in the configuration file)

In Operating System during USMT restore

This step restores the captured USMT data.

sccmtspsi-tasksequence.exe -usmt

In Operating System – Move machine to Active Directory OU

This step moves the system into the specified Active Directory OU  (Only use the DistinguishedName of the OU)

sccmtspsi-tasksequence.exe -movetoadou "OU=Staging,OU=Devices,DC=demodomain,DC=local"

In Operating System at the end of the task sequence

This step generates and emails (Operator and/or administrator) the Build documentation (as set in the configuration file). This step also reports the build completion timing for the operator to sccmtspsi (If allowed in the configuration file).

sccmtspsi-tasksequence.exe -end

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.