SCCMTSPSI
SCCMTSPSI

Documentation for SCCM task sequence deployment orchestrator

  1. Overview
  2. Realm setup
  3. Active Directory & SCCM setup.
    1. Active directory - Security group
    2. Active directory - Broker account
    3. SCCM - Deployment collection
    4. SCCM - Administrative category for applications
    5. SCCM - Administrative category for office
    6. SCCM - Limiting collection for collections
    7. AD - Parent AD group for AD group list
    8. AD - Staging OU
    9. SCCM - Configuration directory
    10. SCCM - WinPE boot image setup
  4. Configuration tool & File
    1. Realm secret key
    2. Allowed WinPE instances
    3. Network access account
    4. Notification account
    5. Hostname formatting
    6. Automatically identify hostname
    7. Overrides
    8. Active directory staging OU
    9. MBAM Server details
    10. SMTP server details
    11. Notification types
    12. User state migration (USMT)
      1. Data store encryption
      2. Migration types
      3. Free space
      4. Config XML
      5. Migration rules XML
      6. Ignore return error codes
      7. Migrating EFS files
      8. Move domain
      9. Move user
      10. Currupt user profiles
    13. Logs and Profiles location
    14. Disk setup
    15. Content availability check
    16. Error adding collection member
    17. Error adding AD group member
    18. Wait for Bitlocker decryption
    19. Approved hardware
    20. Extension Attributes
  5. Using sccmtspsi (Operator view)
    1. sccmtspsi login window content
    2. sccmtspsi controls
      1. Asset hostname
      2. Unlock bitlocker
      3. Get task sequence deployments
      4. Get operating system images and packages
      5. Get office application
      6. Get SCCM applications
      7. Get SCCM collections
      8. Get AD Groups
      9. sccmtspsi actions
      10. Data migration options
      11. Primary users
      12. AD / SCCM entry
      13. Extension Attributes
  6. Task sequence steps
    1. sccmtspsi-tasksequence.exe
    2. Task sequence variables
    3. Apply operating system image step
  7. Task sequence error codes
  8. sccmtspsi error codes

sccmtspsi-tasksequence.exe

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

« Task sequence stepsTask sequence variables »
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.