Documentation for SCCM task sequence deployment orchestrator

Notification types

There are 3 types of notifications.

Login notification : If set to True, notifies the operator about the operators login event. If set to True, notifies the notifications administrator about all login events. Login notification as simplistic; These notifications are used for logging purposes only. Operator information, Architecture information, total run time, system information, Realm name, Domain name etc..

Failure notification : If set to True, notifies the operator about the operators Failure event. If set to True, notifies the notifications administrator about all Failure events.

Success notification : If set to True, notifies the operator about the operators Success event. If set to True, notifies the notifications administrator about all Success events. Success notification are very detailed. The following details or parts of it will appear in success notifications.

  • General information : Operator information, Architecture information, total run time, system information, Realm name, Domain name etc..
  • Task sequences : Available and Selected.
  • Operating system : Available and Selected.
  • Office suites : Available and Selected.
  • Standard applications : Available and Selected.
  • Collections : Available and Selected.
  • Disk and partition : All partitions and Selected partitions.
  • Task sequence variables : All task sequence variables set by sccmtspsi.

Final Build report notification: If set to True, sends the operator a comprehensive build documentation. If set to True, sends the administrator a comprehensive build documentation.

Notifications can be enabled or disabled in the sccmtspsi configuration 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.