SCCM Tasksequence dependency checker : An SOE administrators magic bullet.

SCCM Tasksequence will fail (Error code similar to 0x80004005) if all the packages referenced in the Tasksequence is not available in atleast one of the distribution points in the clients boundary.
The TSManager will only point out missing packages one package at a time. This makes it hard to distribuite all missing packages in one go.
Runs in both WinPE (Requires ADSI support) and Windows
The attached commandline tool will find and display all missing pacakges.

Command : TSDependencyChecker.exe

Task Sequence could not find package

Related Articles

SCCM task sequence UI – Set computer name and more during an SCCM task sequence deployment

It is always a unique challenge of having to build an OSD experience that includes providing a great user experience during the deployment of a new operating system.

The attached application would allow you to present a front-end to an active end-user who is executing the SCCM task sequence……

Keywords: SCCM tasksequence UI, SCCM Task Sequence User interface, SCCM task sequence Set computer name.


Are you an SCCM administrator?

SCCM Task Sequence deployment orchestrator.

built on best practices, learnings & insights of industry experts.

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.