Maintenance Schedule -

XDEVICE – Action1 Endpoint Update Plan

Weekly endpoint updates powered by Action1, with a 4:30 AM readiness reboot and updates scheduled every Thursday at 4:30 PM AEST.

Overview

Timezone: AEST (UTC +10)

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

To simplify the maintenance process and provide a clear, predictable schedule, managed endpoints that are powered on are rebooted every Thursday at 4:30 AM AEST to ensure readiness for endpoint updates, which are then run on a weekly cadence every Thursday at 4:30 PM AEST. This replaces the previous Atera-based update approach and removes reliance on WinGet for software patching.

What this delivers

One update engine: Action1 is the central platform used for endpoint patching and update reporting.
Simple schedule: One consistent Thursday maintenance cadence with a 4:30 AM readiness reboot and a 4:30 PM update window.
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 weekly endpoint update process.
No WinGet dependency: Third-party application patching is handled through Action1 rather than WinGet.
Readiness reboot: Devices that are on at 4:30 AM are rebooted to reduce pending restart issues before the afternoon update window.
Operational clarity: Users and support teams know when updates are expected to run.

Action1 Update Engine

Action1 is used by XSTRA to automate endpoint update workflows. The weekly Action1 policy checks for applicable updates, deploys approved updates during the scheduled window, 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 weekly maintenance process so core XDEVICE components remain current.

XDEVICE Weekly Action1 Update Schedule

The table below shows the simplified operational cadence used by XDEVICE. Times are in AEST.

Cadence	Target Group & Time	Task	Value Provided
Weekly	Powered-On Managed XDEVICE Endpoints Thursday 4:30 AM Pre-update readiness reboot	Scheduled Readiness Reboot Any managed XDEVICE endpoint that is powered on at 4:30 AM AEST on Thursday is rebooted before business hours. This helps clear pending restarts and prepares the device for the Action1 software update window at 4:30 PM AEST on the same day.	Improves update readiness, reduces the chance of incomplete patches caused by pending restarts, and helps endpoints enter the afternoon update window in a cleaner state.
Weekly	All Managed XDEVICE Endpoints Thursday 4:30 PM Powered by Action1	Action1 Patch Deployment Action1 runs the approved weekly endpoint update policy covering Windows, Microsoft, driver, and third-party application updates. Windows / Microsoft update categories: Security Updates Critical – Non-Security Definition Updates Regular Updates Drivers Update Rollups Other Updates XSTRA software updates: XAGENT XPOSE XMESSAGE XPC Third-party application updates: Approved supported third-party application patches through Action1 No WinGet-based application update process Completion actions: Restart prompts or reboots where required to complete installation Failed or incomplete updates flagged for XSTRA review and remediation	Keeps endpoints current with a predictable weekly maintenance window, improves security posture, reduces update drift, and standardises support reporting through Action1.
Weekly	XSTRA Review After Update Run	Action1 Outcome Review & Remediation XSTRA reviews Action1 update outcomes to identify successful installs, failed installs, pending restarts, offline endpoints, and devices requiring follow-up remediation.	Provides visibility of update status, supports proactive remediation, and helps maintain a consistent endpoint baseline.

Update Categories Covered

The following update categories are included in the XDEVICE Action1 weekly update policy.

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

Additional Notes

Purpose of the Weekly Action1 Update Window

Predictable cadence: Powered-on endpoints are rebooted weekly on Thursday at 4:30 AM AEST, with updates run later the same day at 4:30 PM AEST.
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 weekly maintenance process.
Third-party coverage: Approved third-party applications are patched through Action1 rather than WinGet.
Readiness reboot: Devices that are on at 4:30 AM AEST are rebooted before business hours to ensure readiness for the afternoon update window.
Restart handling: Some updates may still require a reboot to finalise installation; users should save work before the scheduled update window.
Remediation: Failed or incomplete updates are reviewed and actioned by XSTRA where required.

Important Change

The previous Atera / WinGet update model has been replaced. XDEVICE endpoint patching is now scheduled and managed through Action1.

Summary of Practices

Daily, pilot, and separate monthly staged update windows have been replaced with a single weekly schedule.
Powered-on managed XDEVICE endpoints are rebooted every Thursday at 4:30 AM AEST to prepare for the afternoon update process.
Updates are run across managed XDEVICE endpoints every Thursday at 4:30 PM AEST.
XSTRA software updates for XAGENT, XPOSE, XMESSAGE, and XPC remain included.
Devices should be left powered on, online, and connected to the internet for the 4:30 AM readiness reboot and the 4:30 PM scheduled update window.
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 weekly schedule when required.

Operational Note

For best outcomes, users should leave devices powered on, online, and connected to the internet each Thursday. Devices that are on at 4:30 AM AEST are rebooted to ensure readiness for the 4:30 PM AEST update window. Action1 will report update outcomes, pending restarts, and any devices requiring XSTRA follow-up. XSTRA software components are also maintained as part of this weekly endpoint update process.

8.7. Maintenance Schedule