Preserve SuperOps configuration: scripts, policies and custom fields

At a glance

SuperOps does not document a single complete configuration export in the official sources cited here. Preserve the script source and files you maintain, and document policy assignments, variable overrides and custom-field definitions separately. Asset reports alone do not establish configuration coverage. RMMBackup provides read-only SuperOps snapshots, record history, and ZIP exports for supported collections.

Document SuperOps script dependencies and policy overrides without assuming reports or community sharing are a configuration backup.

Published Updated

On this page

Preserve script source and execution context

SuperOps documents scripts with variables, attached files, execution settings and scheduled use. Its scripting guide also explains that community publishing omits attached files and custom-field placeholder values. Community sharing therefore should not be used as a private backup mechanism.

Keep your original script files in a controlled repository and compare them with the deployed version. Save dependencies, language, timeout, execution account and variable definitions beside the source.

Document policy overrides and targeting

The scripting guide describes runtime-variable overrides at client, site and asset levels. Record those separately from the base script. For example, a common cleanup script may have a different threshold for one client; preserving the source alone does not preserve that exception.

For group-based policy setups, record the asset-group filter and associated policy sets. The asset grouping guide describes filters and policy associations. It does not establish that an asset CSV reproduces those rules.

Keep definitions separate from current values

For every custom field used by an automation, document its name, type, scope and intended meaning. Capture current values through a verified report or official API field where available. A value in an asset record does not prove its full field definition or policy relationship was exported.

For an MDM custom payload you authored, keep the original configuration file and variable mapping. SuperOps documents uploading or pasting payload XML and mapping variables in custom payload guidance. Keep that source file so you can review and reuse your settings later.

Verify any future automated capture

Before using an API collector, verify the official query for each policy or definition you need; inventory API access is insufficient evidence. Keep credentials in a secret store and record references rather than secret values in configuration notes. This package supports review and reconstruction planning, not guaranteed automated restore into SuperOps.

Official source

Using scripts in SuperOps

Related SuperOps integration

Review current SuperOps backup coverage and availability.