Ask questions | sccmtspsi | SCCM task sequence orchestrator.

SCCM Task Sequence deployment Orchestrator is used by organizations to manage the deployment of Operating System Task Sequences effectively. It is a utility built on best practices, learnings & insights of industry experts.

The orchestrator helps IT Managers and SCCM administrators implement an Agile approach to SOE design and management. SCCM SOE engineers can move from Development, Test through to Production all within the same window and with the same set of Task Sequence variables and parameters.

The SCCM task sequence deployment orchestrator sets the stage for the deployment before the SCCM Task Sequence starts. Such an approach protects important user data saved on the computer from inadvertently getting deleted.

Got any questions. Ask in the comment area below.


  1. Thanks team for the wonderful product. I’ve got a question though. we have a few Acorn RISC Machines based on ARM64 architecture. Does the orchestrator support ARM64 architecture or just x86 and amd64?

    1. Thanks for your question Denver and I am happy you find the orchestrator useful. The SCCM task sequence orchestrator application only works for AMD64 and X86 architectures.
      Although ARM64 architecture is in the development roadmap.

      As always, If you like it share it 😉

    1. @mikeb Since March 2020, the software has been made available for free for public downloads and use. Short answer; the software is full and free for use forever.

      Support not included in the free license. Please contact us if you wish to purchase support.

  2. Will the Orchestrator task sequence work through the CMG? Or will it work through a vpn connection (work from home state)? If so how fast is a task sequence completion over a vpn connection on avg.

    1. @jp12 Thanks for your question and watch this space. This feature is a work in progress and is tentatively set for q4 2021.

      There are a few security and technical hurdles we are working through.

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.