CMTrace Open
WORKFLOW 03 · FIELD INVESTIGATION

Software deployment.

Connect package-engine output with wrapper and bootstrapper activity to isolate deployment failures.

INVESTIGATION START

Start with the exact package attempt.

Begin with the deployment version, command line, execution context, and the first observed failure time. Identify which layer actually returned the result before changing detection logic, retrying the wrapper, or blaming the package engine.

  1. EVIDENCE 01

    MSI verbose logs

    Exposes Windows Installer actions, property changes, source resolution, return values, and rollback inside the MSI transaction.

  2. EVIDENCE 02

    PSADT logs

    Explains wrapper decisions, prerequisites, process handling, user-session behavior, and the command sent to the installer.

  3. EVIDENCE 03

    WiX Burn bundles

    Tracks bootstrapper planning, package-chain application, cached payloads, and the bundle result around one or more installers.

WHAT CMTRACE OPEN CONNECTS

Trace the wrapper into the package engine.

CMTrace Open aligns PSADT orchestration and WiX Burn chain activity with MSI action records, revealing whether the failure began in wrapper logic, bootstrapper planning, payload acquisition, or the underlying installer transaction.

Open stable downloads