Documentation for SCCM task sequence deployment orchestrator

Logs and Profiles location

Specify the location to where the logs will be saved and choose the location from where the application & collection profiles will be selected.

Logging location : All logs will be copied to this network location on Failure (within sccmtspsi) , Success (within sccmtspsi) and when the sccmtspsi-copylogstonetwork application is run during the task sequence.

Logging location permissions :

  • Provide the Realm broker account “sccmtspsi-broker-r01” [where r01 is the Realm name] read and write access to the logs location [Share and NTFS].
  • Provide the Network access account read and write access to the logs location [Share and NTFS].
  • Provide administrators read and write access to the logs location [Share and NTFS].

Profiles location : There are two types of profiles. Application profiles and Collection profiles. Create sub-folders for each type.

  • Application profiles – This location contains text files with a “.sccmapps” extension; Each file contain a list of SCCM application names.

  • Collection profilesThis location contains text files with a “.sccmcols” extension; Each file contain a list of SCCM collection names.

Profiles location permissions :

  • Provide the Realm broker account “sccmtspsi-broker-r01” [where r01 is the Realm name] read access to the profiles location [Share and NTFS].
  • Provide administrators read and write access to the profiles location [Share and NTFS].

The profile creation is discussed in detail in another section.

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.