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

SCCM - WinPE boot image setup

This step walks you through the process of customizing your Windows PE image (Windows Assessment and Deployment Kit) with the sccmtspsi orchestration components.

The Windows PE customizer is one of the 4 elements of the sccmtspsi component package. Download here.

Open the “Windows PE customizer” application (requires administrative access).

add adsi support to WinPE

Browse to the folder that contains the content of the Windows Assessment and Deployment Kit. The toolkit folder must contain the following subfolders.

  • Deployment Tools
  • User State Migration Tool
  • Windows Preinstallation Environment

Note: During the installation of the Windows Assessment and Deployment Kit, select the above-listed components. Windows Pre-execution environment is a separate download to the rest of the Windows Assessment and Deployment Kit components.

SCCMTSPI is updated regulary. So try and keep the version number of ADK WinPE Addon and the version number of “sccmtspsi components” in sync. See images below for more clarity.

If the prerequisite is met, you will be moved to the next screen.

Based on your system architecture, click either on the “Generate WinPE image for AMD64 architecture” or the “Generate WinPE image for X86 architecture” button.

The application will do the following.

  • Extract the Windows PE image from the Windows Assessment and Deployment Kit.
  • Customize it with advanced orchestration features.
  • Place the customized Windows PE image into a directory of your choice (as seen in the image below).

Wait for the process to complete. After the successful completion of the customization process, you’ll be able to retrieve the customized Windows PE image from the location you had chosen in the previous step.

Import the customized Windows PE image into SCCM.

Make the following changes to the imported boot image, after the sccmtspsi customized boot image has been imported into SCCM.

sccmtspsi.exe -realmname r01 -instancename yourinstancename -logindomain yourdomain.com -sccmserver sccmserver.yourdomain.com
 -adservername yourdomaincontroller.yourdomain.com -adconnectiontype adws -sccmsitecode S01
 -timeserver yourtimeserver.yourdomain.com -timezone "New Zealand Standard Time" -dnsserverip xxx.xxx.xxx.xxx

Note: Always copy and paste into a basic text editor and check if the command line is readable and in a single line.

Note : All of the below parameters are required.

realmname : It is the 3 character Realm name.

instancename : The name of the WINPE instance. Edit the name (issue a new name) to rein in old USB and Full media. All allowed instances are set in the configuration file.

logindomain : This is your authenticating domain [Should be 2008 R2 or greater].

sccmserver : The fully qualified domain name of your SCCM management point server.

adservername : The fully qualified domain name of the domain controller wherein Active Directory Web Services is installed.  [Should be 2008 R2 or greater].

adconnectiontype : adsi [Active Directory Service Interface] or adws [Active Directory Web Services].

sccmsitecode : The SCCM site to which the clients will be assigned to.

dnsserverip : The IP address of your DNS server.

timeserver : The fully qualified domain name of the time server from which sccmtspsi will synchronize the time & date. In a standard domain setup, the root domain controller will have the time service running on it.

timezone : Your time zone. Run the following Power Shell command to find your time zone.

« SCCM - Configuration directoryConfiguration tool & File »
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.