Create configuration policies and assign them at the Customer, Folder, or Agent levels to ensure compliance across your end-user devices.
Note: Configuration policies are only available in Atera’s new design interface. How do I switch?
This article describes:
To set up your policies, see Set up configuration policies
How configuration policies work
- Admins can create and assign policies to Customers, Folders, and Agents.
- A technician can assign policies to individual Agents only, as long as they have the required permissions for that customer.
- One policy can be assigned per Customer, Folder, or Agent.
- Once created or saved, the policy will be immediately applied to all assigned Customers, Folders, and/or Agents, as per the inheritance and supersession rules explained below.
- If you have disabled 'Windows local updates' within the associated automation profile, the policy will only apply to updates managed via Atera. Otherwise, the policy will apply to all updates.
- To ensure device compliance, the policy will be applied every 12 hours.
- Configuration Policies override the "Reboot if needed" option found in IT Automation profiles. For example, if you have set up a Configuration Policy with "Restart outside of active hours", the agent will reboot only after working hours have ended.
Policy inheritance and supersession
- Policy inheritance applies at the Folder and Agent levels.
- If assigned at the Customer level, all unassigned Folders and Agents under that customer will inherit the policy.
- If assigned at the Folder level, all unassigned Agents under that Folder will inherit the policy.
- Policies assigned at a Folder level will override any assigned to the parent Customer.
- Policies assigned directly to an Agent will override any assigned to the parent Folder and/or Customer. Policy supersession applies at the Folder and Agent levels for all policies applied at any level above.
- Deleted policies will be removed from all associated Agents without reverting the configurations they had previously set. To revert those configurations, we recommend reverting to device settings within your policy's toggled configuration(s) before deleting the policy.
Note: More configurations coming soon! Have any you'd like to see? Let us know
Windows Update Restarts
Configure device restarts after updating the Windows OS.
- Revert to device settings: Select this option to apply the Windows default settings to the devices.
- Disable auto-restart with logged-on users: Select this option to disable device restarts for any currently logged-on user.
Note: The device will not restart if the user logs out after the automation has run.
- Restart outside of active hours: Select this option to set the active hours in which devices will not restart.
- The active hours are based on the local system settings.
- Applies to Windows 10, Windows Server 2022, and above.
- Restart after the selected time period: Select this option to schedule device restarts anywhere from 15–180 minutes after Windows updates are complete.
Note: Applies to Windows 10, Windows Server 2022, and above.