Quick answers
A few things worth knowing.
Practical answers for your first deployments.
Where do I find the delivery report?
After SetupComplete, open %ProgramData%\OSDStage\Results\DeliveryReport.html. The matching DeliveryReport.json sits beside it. Both are generated automatically; no extra staging command or module import is required. Explore the report and a fictional example.
Why can a successful deployment show Attention?
Execution can succeed while a restart or follow-up update scan is still needed. Missing evidence, skipped results or unavailable metadata can also require attention. Read the report summary and checks; Attention does not automatically mean installation failed.
Does the report work offline?
Yes. The HTML is self-contained, with no scripts or remote assets. Open it in a browser on the deployed PC or copy it to a preparation PC. Review identifying names and paths before sharing a real report.
What do catalog, built-in and repository mean?
The Catalog page is the browser for available components. Built-in app integrations and configuration commands are provided by OSDStage. A repository hosts packages you maintain yourself; its catalog.json lists those packages and links to their manifests. Repository packages appear alongside built-in components when you load that file’s URL.
Do I need a repository?
No. Built-in vendor integrations and configuration commands work without one. Use a repository for packages you maintain yourself.
Where do I run the Add commands?
On the target PC in WinPE, after OSDCloud has applied Windows and before its first boot. Sync commands for vendor content run on a full Windows preparation PC.
Does OSDStage replace OSDCloud or Autopilot?
No. OSDCloud applies Windows. OSDStage prepares your chosen software and settings before OOBE, then the normal OOBE and Autopilot flow can continue.
Must I prepare every USB cache first?
No separate cache preparation is needed for online deployments, including Company Portal and CMTrace Open. OSDStage checks for current content and caches it automatically when an OSDCloud volume is present. Without USB, it downloads to the Windows disk. Fully offline deployments require verified content in advance.
Can users change their default apps later?
Yes. File and protocol associations are initial defaults for new users. OSDStage does not enforce or repeatedly restore them.
What if a package fails?
Open the delivery report under ProgramData\OSDStage\Results and inspect the local logs. Independent packages, including the final Windows Update pass, can still run after an individual package failure. The earlier failure stays visible; fatal validation and Windows Update prerequisites still apply. General staging is retained on failure; credential-bearing Wi-Fi configuration is removed after its import attempt. There is no scheduled retry.
Why won’t my repository load in the web catalog?
Use a reachable HTTPS catalog with schema 2. The catalog and linked manifests must allow browser requests from this site through CORS. Browser authentication prompts are not supported. A working PowerShell URL can still be blocked by browser CORS rules.
Does this website install anything?
No. It helps you choose commands and browse metadata. Run the commands yourself in the correct deployment phase. The separate Windows Viewer inspects local staging, cache and logs.