Legacy Windows Policy Builders
The /win/base-policy-builder and /win/supplement-policy-builder pages are focused Windows helpers for teams that need a direct, wizard-driven build path outside the unified Policies catalog.
The /win/base-policy-builder and /win/supplement-policy-builder pages are focused Windows
helpers for teams that need a direct, wizard-driven build path outside the unified Policies
catalog. They remain useful for isolated builds, migration work, and comparison with the unified
policy workflow.
Base builder
Section titled “Base builder”Use the base builder to create a Windows base trust envelope: platform rule options, trust rules and policy identifiers. After the build completes, open the result in Policies for review, approval and group assignment. Do not deploy an artifact directly from a helper page without the normal audit soak.
Supplement builder
Section titled “Supplement builder”
The supplemental builder creates additive trust. Its output is still bound late to the base policy resolved by the target device group. It cannot own deny rules or platform-wide switches.
When to use which surface
Section titled “When to use which surface”| Need | Preferred surface |
|---|---|
| Day-to-day policy lifecycle | Policies |
| Review and approve variants | Policies |
| Build from a focused Windows wizard | /win/*-policy-builder |
| Validate hand-edited XML | Policies → Validate |
| Turn observed files into rules | Discovery Scans |
The helper builds artifacts; the unified catalog owns rollout governance.