Comparing, Publishing, and Remediating
Compare local intent with Cisco Spaces, publish approved revisions, and safely remediate external state.
Compare against Spaces #
Comparison evaluates the open draft when one exists, otherwise the current published revision, against the latest Cisco Spaces state. Results identify the observed floor, differences, and recommended actions without modifying either system.
Publish the local draft #
Publish records an approved local revision. It does not push configuration to Cisco Spaces or Pointr.
Only current published per-device rows are exact intent for monitoring and potential automated remediation. An open draft does not affect either behavior.
Automated-remediation safety gate #
Allow automated remediation in IoT Configuration is the deployment's persistent safety gate. Eligibility requires an active deployment with a current published revision. Monitoring-only profile intent is always alert-only and cannot be made remediable.
A manual tenant audit may disable remediation for that run, but it cannot override a disabled deployment gate. There is no separate scheduled-monitoring remediation switch on the location configuration.
External remediation authentication #
Some Cisco Spaces tenants require a sys-token or full Cookie header for remediation. Credentials entered in the page are used for the requested operation and should be handled as sensitive material. Do not place credentials in notes, CSV files, or documentation.
Preview and apply #
- Run comparison and confirm the intended target state.
- Open remediation and select only the external systems that should change.
- Review the preview, including affected devices and rejected or unsupported rows.
- Apply the operation and review its per-device result.
- Reload comparison or analysis data to verify the external state.