OverviewRelease notesUpgrade guideInstallationGetting startedMicrosoft AD CSCisco Catalyst 9800Agents & automationNginx on LinuxHTTPS verificationAdministrationAPI credentialsCertificate profilesAI AssistantMCP integration

Upgrade guide

Plan the release, preserve your data and verify the result before resuming operations.

Dokumentation für 1.0.38. Screenshots zeigen Beispieldaten.

Die Dokumentation ist derzeit auf Englisch verfügbar. Produktoberfläche und integrierte Hilfe sind auf Deutsch verfügbar.

Use the approved release artifact for deployment; a version label alone does not identify the final build.

Before the upgrade

  1. 01Review release notes for every intervening version, connector limitations and any open recovery or uncertain job outcomes.
  2. 02Create and verify a PostgreSQL backup. Preserve the master key, environment/configuration, license and persistent agent state. Keep backups separate from the server being upgraded.
  3. 03Record the current image/build, server health, agent identities and critical device bindings. Test the candidate on an isolated environment and plan the maintenance window.
  4. 04Use the established appliance or server upgrade procedure with the approved artifact. A server image update does not install host helpers, journal services or update every remote agent.

Version-specific changes

1.0.36 — notifications and IIS readiness

Migrations 0091/0092 add notification and destination-management state. Existing notification rules stay unchanged. Inspect uncertain deliveries at the receiver before acknowledging or retrying them: retrying can duplicate a message.

For IIS readiness, update both Windows supervisor and worker to 1.0.36 or newer. Readiness checks inspect configuration; they do not prove certificate installation or service verification.

1.0.37 — certificate profiles

Migration 0093 stores profiles and issuance settings. Existing certificates without a snapshot retain their legacy CA-default template behavior; old custom choices cannot be reconstructed. Profiles and verified WLC pin maintenance require no agent update.

1.0.38 — appearance, MCP and AI Assistant

The release adds migrations 0094/0095 for scoped integration credentials and AI settings/conversations. Preserve the master key. No agent upgrade is required for these features.

MCP requires a separate process/container and deliberately configured access. The AI Assistant is disabled by default and requires provider configuration and data-processing consent. Neither a remote MCP endpoint nor AI provider access is enabled by upgrading.

See MCP setup and AI Assistant setup.

After the upgrade

  • ▸Confirm the server build and successful startup/migrations. Check sign-in, local MFA and directory login, license, inventory, vault access and settings.
  • ▸Confirm each expected agent still has its original ID and a fresh heartbeat. Where updated, check both supervisor and worker versions.
  • ▸Check pending jobs and recovery records before retrying operations. Use a controlled certificate operation to verify the specific connector and service checks you rely on.
  • ▸Check notification history and actual recipient delivery separately. Provider acceptance is not proof of inbox or Teams receipt.
  • ▸If enabling AI or MCP, test the smallest permitted read scope first. Validate the selected provider/client and review data exposure before enabling reviewed AI actions.

Recovery and rollback

Migrations are forward-only. Reverting the image does not restore the previous database, device trust or configuration. Assess compatibility, writes made after upgrade and pending operations before restoring the matching backup and master key.

For installations predating 1.0.35, also review the earlier upgrade boundaries and agent upgrade guide.