Maintenance Schedule -

XDESK – Action1 Endpoint Update Plan

Pilot-to-production endpoint update model powered by Action1.

Overview

Timezone: AEST (UTC +10)

XSTRA uses Action1 as the update engine for managed XDESK endpoints. Action1 is used to identify, schedule, deploy, and report on operating system updates, Microsoft updates, approved drivers, and supported third-party application patches.

XSTRA uses a controlled pilot-to-production update model. The Pilot Group runs first, then XSTRA reviews the pilot results before releasing updates to the Production Group. If pilot results show a material issue, the production run may be paused or deferred until remediation is complete.

What this delivers

One update engine: Action1 is the central platform used for endpoint patching, scheduling, and update reporting.
Pilot-first deployment: The pilot group receives updates first for controlled validation.
Controlled production release: Production endpoints are updated after successful pilot validation.
Broader coverage: Windows update categories, Microsoft updates, approved drivers, supported third-party application updates, and XSTRA software updates.
XSTRA software maintained: XAGENT, XPOSE, XMESSAGE, and XPC remain part of the endpoint update process.
No WinGet dependency: Third-party application patching is handled through Action1 rather than WinGet.

Action1 Update Engine

Action1 is used by XSTRA to automate endpoint update workflows. The Action1 policy checks for applicable updates, deploys approved updates during the scheduled pilot and production windows, records outcomes, and provides visibility for follow-up remediation where an endpoint is offline, requires a restart, or fails to complete an update successfully. XSTRA proprietary endpoint software updates are also retained within the maintenance process so core XSTRA components remain current.

XDESK Action1 Pilot & Production Update Schedule

The table below shows the operational cadence used by XDESK. Times are in AEST. The production run proceeds after the Thursday pilot run has been reviewed and no blocking issue has been identified.

Cadence	Target Group & Time	Task	Value Provided
Weekly	Pilot Group Thursday 1:00 AM Powered by Action1	Pilot Action1 Patch Deployment Action1 runs the approved endpoint update policy against the pilot group first. This validates the update set before it is released to production endpoints. Included update areas: Security Updates, Critical – Non-Security, Definition Updates, Regular Updates, Drivers, Update Rollups, and Other Updates Approved supported third-party application updates through Action1 XSTRA software updates: XAGENT, XPOSE, XMESSAGE, and XPC Restart prompts or reboots where required to complete installation	Provides early validation of updates before broader deployment, reducing risk to the production endpoint fleet.
Weekly	Pilot Review Before Sunday Production	Go / No-Go Validation XSTRA reviews Action1 pilot results, including successful installs, failed installs, pending restarts, offline endpoints, and any adverse outcomes. If the pilot group is acceptable, the Sunday production run proceeds. If a blocking issue is detected, the production run may be paused, deferred, or remediated before proceeding.	Adds a control point between pilot and production so wider deployment only proceeds after review.
Weekly	Production Group Sunday 1:00 AM Subject to successful pilot validation	Production Action1 Patch Deployment Assuming the pilot group is okay, Action1 runs the approved endpoint update policy across the production group on the following Sunday. Included update areas: Windows, Microsoft, driver, and approved update categories Approved supported third-party application updates through Action1 XSTRA software updates: XAGENT, XPOSE, XMESSAGE, and XPC Restart prompts or reboots where required to complete installation	Keeps production endpoints current while reducing risk through a pilot-first validation model.
Weekly	Production Review After Sunday Run	Action1 Outcome Review & Remediation XSTRA reviews production update outcomes to identify successful installs, failed installs, pending restarts, offline endpoints, and devices requiring follow-up remediation.	Provides fleet-wide visibility, supports proactive remediation, and helps maintain a consistent endpoint baseline.

Update Categories Covered

The following update categories are included in the XDESK pilot and production update policies.

✓Security Updates	✓Critical – Non-Security	✓Definition Updates
✓Regular Updates	✓Drivers	✓Update Rollups
✓Other Updates	✓Approved Third-Party Application Updates via Action1
✓XSTRA Software Updates: XAGENT, XPOSE, XMESSAGE, and XPC

Additional Notes

Purpose of the XDESK Action1 Update Model

Pilot-first cadence: Pilot Group updates run first to validate the update set before production release.
Production cadence: Production Group updates proceed after pilot validation.
Controlled release: Production updates proceed when the pilot group is okay. If pilot results show a material issue, production can be paused or deferred.
Centralised patching: Action1 is used as the update engine for Windows, Microsoft, driver, and supported third-party application updates.
XSTRA software updates: XAGENT, XPOSE, XMESSAGE, and XPC continue to be updated as part of the endpoint maintenance process.
Third-party coverage: Approved third-party applications are patched through Action1
Restart handling: Some updates require a reboot to finalise installation; users should save work before the scheduled window.
Remediation: Failed or incomplete updates are reviewed and actioned by XSTRA where required.

Summary of Practices

Pilot Group updates run first for validation.
Production Group updates proceed after successful pilot validation.
Action1 is the update engine for endpoint patching and update reporting.
XSTRA software updates for XAGENT, XPOSE, XMESSAGE, and XPC remain included.
Devices should be left powered on, online, and connected to the internet during scheduled update windows.
Where a device is offline during the update window, missed tasks may be applied at the next available opportunity.
Urgent remediation or critical security response actions may occur outside the standard schedule when required.

Operational Note

For best outcomes, devices should be powered on, online, and connected to the internet before their scheduled update window. Action1 reports update outcomes, pending restarts, and any devices requiring XSTRA follow-up. Production rollout proceeds after successful pilot validation.

9.10. Maintenance Schedule