Who can use this feature?
đ€ Organization Owners, Admins, Group Admins, and custom roles with the "Configure OS Updates" permission can configure this setting directly on a group or ungrouped device, and can assign an existing OS Updates preset. Creating or editing an OS Updates preset is an organization-level action: Organization Owners and Admins can do this by default, and custom organization roles can be granted Create and Edit permissions for OS Updates presets under Settings â Roles â Configuration Presets.
đ© Available on the Essential, Classroom Pro, Classroom Ultimate, and Enterprise Plans.
Overview
Postponing Meta OS updates postpones the installation of system updates for 30 days. After the 30-day period has ended, the OS will automatically update.
The system limits each update to one 30-day postponement. The period begins when the system first postpones the update and setting new postponement policies wonât extend the period.
Postponing OTA updates can prevent devices from receiving critical updates. For this reason Meta might choose to exempt important security updates from a postponement policy. The system resets the 30-day postponement timer if a different update becomes available during the periodâgiving IT admins a chance to try the combined system updates. Once 30 days have passed without a new update, the OS will automatically update. Later, when a new system update becomes available, the 30-day period begins again.
đĄ Meta only allows for postponement of automatic updates by 30 days, not disabling of OS updates altogether. Further, Meta could force an update through if they deem necessary (e.g. a security patch), even if automatic updates are postponed by 30 days.
Postponing Meta Quest OS updates is part of the Operating System Updates settings of a group or ungrouped device. The default is Not Managed by ArborXR, which leaves OS updates to run automatically.
There are two ways to configure it:
Option 1 (recommended): with an OS Updates Configuration Preset. You define the settings once in the preset, then assign the preset to as many groups and ungrouped devices as you like. When you update the preset, the change applies immediately everywhere it's assigned.
Option 2: directly on an individual ungrouped device or device group.
Option 1: Configure with an OS Updates Preset (Recommended)
đĄ Why we recommend Configuration Presets. Configuring a group or ungrouped device directly means repeating the same clicks for every group and device, and repeating them again each time the setting needs to change. With a preset you configure the setting once, assign it to up to 100 groups or ungrouped devices in a single operation, and any later change to the preset applies immediately everywhere it's assigned. Over the life of a fleet this saves a significant amount of time and removes the risk of groups drifting out of sync.
Step 1: Create the preset
Navigate to Configuration Presets in the left sidebar.
Click Create Configuration Preset in the top right corner and choose OS Updates.
Enter a Name for the preset and click Create.
Set the Meta OS Update Policy setting to Postpone for 30 Days.
Click Save.
Step 2: Assign the preset
Assign the preset from the Configuration Presets library. You can assign it to up to 100 groups or ungrouped devices in a single operation.
Navigate to Configuration Presets in the left sidebar.
Select the checkbox next to the OS Updates preset you want to assign.
Click Assign.
Choose either Assign to Groups or Assign to Ungrouped Devices.
Select the target groups or ungrouped devices, then click Assign.
Option 2: Configure Directly on a Group or Device
đĄ If your organization has Require Configuration Presets enabled, direct configuration is disabled and the Operating System Updates section must be configured with a preset.
Navigate to the ungrouped device or configuration group in question.
Click Settings.
Click Operating System Updates to expand the section.
Set the Meta Quest OS Update Policy setting to Postpone for 30 Days.
Click Save.