Tiaris guide
Versions and compatibility
Understand Console, Nest, workstation-runtime, and Blueprint versions before approving changes.
Several version numbers describe different parts of a managed computer. Keeping them separate helps you understand a deployment prerequisite and give support useful evidence.
The four parts
Section titled “The four parts”| Part | What it describes | Where to look |
|---|---|---|
| Tiaris management service | The Console and API serving your organization. | Product version information and support details available in your Console. |
| Nest appliance | The local installation, preparation, and delivery service. | Home > Open Nest > Appliance. |
| Workstation runtime | The signed Agent, apply helpers, updater, and managed runtime components installed on a computer. | The computer’s Diagnostics and reported version information. |
| Blueprint version | An immutable desired configuration composed with pinned Policy and App List revisions. | The Blueprint’s version history and the computer’s assigned/reported configuration. |
The running Agent version and installed runtime version are distinct observations. A missing report means Not reported or unavailable evidence, not an assumed version.
Read the plan before approving
Section titled “Read the plan before approving”A new Blueprint capability may require a newer Nest, a newer workstation runtime, or both. Deploy shows current and required versions, which targets need changes, and the reason for each prerequisite.
Approval authorizes only the exact reviewed work. Compatible computers remain unchanged when they do not need an update. Tiaris verifies prerequisites before applying the Blueprint.
For example, custom wallpaper delivery uses the capability blueprint_wallpaper_v1. The plan must establish that Nest can prepare the wallpaper and the targeted runtime can apply it. Desktop-app curation and workstation diagnostics have their own runtime requirements.
A Console update is not a workstation update
Section titled “A Console update is not a workstation update”Publishing a new management service does not install new helpers on computers. A workstation feature is available only when its separately signed runtime has been released, installed, and reported by the computer. Nest similarly needs its applicable appliance release.
Use the versions and capability requirements shown in your plan as the authority. Do not infer availability from a screenshot, a development deployment, or a newer Console alone.
Offline and older computers
Section titled “Offline and older computers”An offline target keeps its current system and waits safely. After it reconnects, Check again and resume rechecks current identity, health, versions, and capabilities.
One-time bootstrap required identifies a supported protected transition. The older runtime must support both apply_blueprint and restart_agent. Reinstall required means the existing system cannot make that protected transition; follow reinstallation with current signed media.
A legacy Nest without a protected compatible updater requires the current signed appliance ISO and its recovery/installation process.
What rollback restores
Section titled “What rollback restores”A Blueprint rollback restores the stored previous configuration on computers changed by the approved deployment. It is not a generic downgrade of every component. A local runtime or Nest activation failure uses that component’s protected recovery path.
Record the original failure and any rollback failure separately. See Deploy updates for history, retries, and recovery controls.