Skip to content

Upgrade, Reinstall & Replacement

SchemaDock distinguishes between updating an existing enrolled agent and enrolling a replacement host.

Update or reinstall an enrolled Dock

An enrolled Dock already has a persistent identity.

For normal updates:

download newer generic package
    -> update/reinstall
    -> preserve config
    -> preserve identity
    -> restart service
    -> reconnect

A new bootstrap is not required.

Windows

Download the current Windows installer from Install & Health and run it as an update/reinstall.

The validated installation keeps:

C:\ProgramData\SchemaDock\config.json
C:\ProgramData\SchemaDock\identity.json

Linux

Extract the newer package and run:

sudo ./install.sh

The installer detects the existing installation and preserves the enrolled identity under:

/var/lib/schemadock/identity.json

Installed version vs current release

SchemAlign Administration may show both:

Field Meaning
Installed version Version reported by the enrolled agent.
Current release Current SchemaDock release available for download.

When they match, the Dock is up to date.

Replace a host

Do not copy an already-consumed bootstrap to a new host and expect it to enroll as the existing agent.

Treat host replacement as a new enrollment lifecycle:

  1. Register a replacement SchemaDock.
  2. Configure the required owner, availability, and destination policy.
  3. Download a new install bundle with a new one-time bootstrap.
  4. Install and enroll the replacement host.
  5. Confirm it is Online.
  6. Test required Connection Routes.
  7. Update pipelines to use the replacement Dock if the registration changed.
  8. Delete the old Dock after the cutover is complete.

This avoids silently rotating or invalidating an active agent identity during an ordinary software download.

Rollback considerations

Before rolling back an agent version:

  • confirm the older version remains compatible with the current SchemAlign gateway
  • preserve the existing config and identity
  • do not create a new enrollment unless the identity itself must be replaced
  • validate the Dock reconnects and still enforces destination policy