Skip to content

Windows Updates ​

Use Windows update rings to approve Microsoft updates for groups of endpoints. Manage rings and repository content under Software > Windows Updates.

Approval makes an exact update revision eligible for a later Install approved Windows updates job. It does not install the update or restart endpoints.

Requirements and limitations ​

Endpoints must report update inventory before you can approve their missing updates. Choose the installation source according to network access and update type:

SourceRequirements and coverage
Windows UpdateEndpoints reach Microsoft Update directly. Supports applicable online update classifications, including drivers and firmware.
Ordyn repositoryA Runner downloads content for delivery through Cache. Requires current offline inventory and supports Security Updates, Service Packs, and Update Rollups.

The offline catalog is not the complete Microsoft Update catalog. Updates omitted by Microsoft require an online source. Approved-update jobs do not install from WSUS. Vendor-specific update tools are outside this workflow.

Offline catalogs older than 45 days are rejected. Download a fresh catalog weekly when using offline inventory or repository installation.

Set up an update ring workflow ​

  1. Configure a Windows Update Policy for the intended endpoints.
  2. Run or schedule Collect Windows update inventory. Choose Microsoft Update for online inventory or Offline catalog for repository deployment.
  3. Create a ring and assign its endpoints.
  4. Review missing revisions and approve them manually or through automatic approval rules.
  5. For repository deployment, prepare the approved content on a Runner.
  6. Run or schedule a job with Install approved Windows updates for the endpoint scope.

Policy assignment and ring membership are independent. Assigning a ring does not change Windows settings.

Configure Windows Update policy ​

To control installation through Ordyn, use a Windows Update Policy profile with automatic updates disabled and the source set to Microsoft Update / Windows Update. Use Remediate to apply settings, or Audit only when Group Policy or MDM manages them.

Set Windows Update user access to Blocked if interactive users must not scan, download, or install updates outside Ordyn. This also applies to administrators. Notification settings affect visibility, not installation or restart timing.

Quality-update deferral can delay online offers for up to 30 days. Leave it unmanaged when another system controls it. The effective deferral also affects online inventory.

Removing a ring assignment does not remove its policy configuration; manage profile assignments separately.

Create a ring ​

Create a ring under Software > Windows Updates and choose its default automatic approval delay. Use folders to organize rings; ring folders do not assign endpoints.

Disable a ring to suspend its approved-update installation. Its configuration and decisions remain available for review.

Assign a ring ​

Assign a ring to a tenant, endpoint folder, endpoint group, or endpoint. Folder assignments include descendants. When several assignments match, the most specific wins:

  1. Endpoint
  2. Endpoint group
  3. Deepest endpoint folder
  4. Tenant

Different rings at the same highest precedence create a conflict. Resolve the assignments before installing approved updates. For example, two groups can conflict if each assigns the same endpoint to a different ring.

Review effective membership on the ring's Endpoints page. Remove an existing direct assignment before assigning the same scope to another ring.

Approve or reject updates ​

Review the ring's missing updates and choose which exact Microsoft Update revisions may install. Decisions are independent between rings; a new revision needs its own decision.

Approve a revision to make it eligible for installation. Reject it to withhold it, including from automatic approval. Clearing a decision makes it eligible for evaluation again, so a matching automatic rule can approve it again.

An Expired decision refers to a revision that effective ring endpoints are not reporting as missing or installed. It does not mean an update was uninstalled.

Configure automatic approval rules ​

Under Automatic approvals, create reusable rules by classification and, if needed, product or update name. Driver rules can also narrow the provider, manufacturer, device model, class, or hardware ID. Preview a rule against discovered revisions before assigning it to a ring.

Values within one matcher group are alternatives; every populated group must match. Update-name matching is a case-insensitive substring, not a regular expression.

Choose immediate approval, a custom delay, or the ring's default delay. The delay starts when Ordyn first discovers the revision on any endpoint, not when the rule is assigned. For example, an inherited rule can approve the same revision immediately in a pilot ring and three days later in a wider ring.

When several rules match, the earliest approval date applies. A ring must have an applicable missing update for the rule to schedule approval. Disabling a ring pauses its schedule; overdue approvals can apply when it is enabled again.

Manual rejections take precedence. Editing or removing a rule does not revoke approvals it already created. Automatic approval does not start endpoint installation or reboot devices.

Block updates on one endpoint ​

Block selected updates under an endpoint's Updates page to withhold them on that device. The blacklist overrides ring approvals and applies to ordinary and approved Windows update jobs, including repository installations. Updates that require a blocked update are skipped too.

A block covers all revisions of the same Microsoft Update ID until removed. Replacement updates with a different ID remain eligible. Blocking a missing update does not make the endpoint compliant.

Review or remove blocks under Updates > Blacklist. Changes affect future tasks; running tasks can finish. Blocks do not prevent installation through Windows or other tools outside Ordyn.

Review the Ordyn repository ​

Use Ordyn repository to inspect imported updates, offline catalogs, Microsoft certificate bundles, and Defender intelligence packages. Content must complete malware verification before it can be downloaded or installed.

Deleting update content leaves inventory, approvals, and history intact. Active jobs protect content they still need. Infrastructure jobs can import deleted content again.

Prepare approved update content ​

For repository deployment, create an infrastructure job with Download offline Windows update catalog, select a suitable Runner pool, and schedule it weekly. Collect offline inventory from endpoints using that catalog.

After approval, run Download approved Windows updates to import missing content. Installation waits until every required file is present and verified as clean. A later online scan does not discard the offline evidence needed by this workflow.

Add a Windows update approved infrastructure automation to prepare content when approvals change. A debounce combines bursts of approvals; a recurring schedule can provide an additional check.

Update Defender on offline endpoints ​

Use the Defender tab under Software > Windows Updates > Ordyn repository to review Microsoft Defender intelligence packages and their included engine versions. This workflow supports x64 Windows 11 and Windows Server 2019, 2022, and 2025.

These packages update security intelligence and the included engine. Defender platform updates are managed separately.

  1. Create an infrastructure job with Download Microsoft Defender updates and select a Windows or Linux Runner pool. The Runner needs HTTPS access to go.microsoft.com and definitionupdates.microsoft.com, plus access to its pool Cache Node.
  2. Run or schedule the job. The package becomes available after malware scanning and Microsoft signature verification finish.
  3. Add Install Microsoft Defender updates to an endpoint job. Endpoints receive the package through Cache and can install it without internet access.

Endpoints need an assigned, reachable Cache Node. Endpoints with current intelligence or missing or disabled Defender are skipped. Defender in passive mode can receive intelligence updates.

Schedule regular downloads to keep intelligence current. The import date does not establish the age of the definitions, and offline verification cannot confirm current certificate revocation status.

Repository retention preserves the newest verified package and versions needed by active jobs. You can manually delete versions that active jobs do not need. Defender intelligence updates do not require an update ring or an offline scan catalog.

Maintain certificates on offline endpoints ​

Use Microsoft certificate bundles to update trusted and disallowed certificates on Windows endpoints without internet access.

  1. Create an infrastructure job with Download Microsoft certificate updates and select a Windows or Linux Runner pool. The Runner needs access to Microsoft's certificate download service at ctldl.windowsupdate.com and its pool Cache Node.
  2. Run the job, then review the bundle under Software > Windows Updates > Ordyn repository > Certificates.
  3. Add Deploy Microsoft certificate updates to an endpoint job to install the latest valid bundle.

Monitor the imported certificate count and total in the job run. After all certificates are imported, scanning and verification must finish before the bundle becomes available for deployment.

Private and administrator-managed roots are preserved.

Schedule the download job to keep bundles current.

Install approved updates with a job ​

Add Install approved Windows updates to an endpoint job and choose Windows Update or Ordyn repository. Optionally filter by classification and product. Values within a filter are alternatives; when both filters are set, both must match.

Empty filters include all supported approved updates for the chosen source. For frequent Defender updates through Windows Update, select the Microsoft Defender Antivirus product.

Each endpoint uses its own effective ring, so one job can cover multiple rings. A missing, disabled, or conflicting ring prevents installation. Windows makes the final applicability decision: a successful task with no installed updates can mean none of the requested revisions apply at execution time.

Repository installation needs an assigned, reachable Cache Node, offline inventory with a catalog no older than 45 days, and verified update content. Ordyn does not automatically switch installation sources after a failure.

Review task results for failed revisions and Windows error codes. Set a timeout long enough for download and installation. Windows servicing already underway can continue after cancellation.

See the task reference for authoring guidance.

Reboot behavior ​

Automatic reboot handling is disabled by default. Updates can remain pending until the user restarts the device or Windows completes its restart handling.

Enable automatic reboot handling only where job-initiated restarts are acceptable. The job can wait for the device to restart and reconnect, check readiness, and rerun the approved updates if configured.

Delivery Optimization and peer sharing ​

Assign a Windows Delivery Optimization profile to use local peers or a private peer group with the Windows Update source. Use the same group ID on devices intended to share content. Repository content uses Cache Nodes.

If Group Policy, MDM, or another provider already manages Delivery Optimization, remediation reports the conflict without changing the policy. See Configuration Profiles.

Access ​

Use Platform Admin to manage rings, approvals, repository content, and endpoint blacklists. Use Job Designer to author installation jobs and Job Operator to run them within the assigned scope. See Access Control.

Troubleshooting ​

For an empty ring, verify effective membership and collect update inventory. Check that the selected inventory source includes the required classifications.

For a ring conflict, review endpoint, group, folder, and tenant assignments and remove the competing assignment.

For missing repository content, refresh the catalog, collect offline inventory again, approve the required revisions, and download approved content. Check malware verification and Cache connectivity.

Use Update Inventory to investigate a device and Windows Update Compliance Reports to follow rollout across the fleet.