Continuity Engine - New Upgrade Method
Summary
This knowledgebase article provides an alternative procedure of upgrading Continuity Engine which should be used on those deployments which, for some reasons, are not managed via Engine Management Service console.
Note: Each Engine node is upgraded individually using the engine-cli-setup tool. Console access is required on each of the Engine active and passive nodes.
Procedure
This step is only for customers running Neverfail Engine versions older then v11.
If C:\ProgramData\Neverfail-Protected folder doesn't exist on your Active server please create it manually and then open Neverfail Advanced Management Client, go to its Data\File Filters section and use the Add Inclusion Filter button to add an Inclusion Filter from this folder with the following syntax: C:\ProgramData\Neverfail-Protected\**

On the machine running Engine Management Service console (EMS), download the latest Engine kit from https://support.neverfail.com/portal/en/kb/articles/neverfail-continuity-engine.
Note: EMS machine is not a Primary or Secondary node running our core product Continuity Engine. EMS web console is always installed on a separate machine than Primary and Secondary nodes.
On the machine running the Neverfail EMS web console, run the downloaded MSI installer to perform an in-place upgrade of your EMS web console.
Note: Step 4 below is necessary only for EMS consoles versions older then v22. In v22 EMS automatically copies the Catalog folder to the Active server in the cluster which then replicated to the Passive(s) node(s).
Also on the machine running the EMS web console, go to C:\ProgramData\Neverfail\VAD and locate catalog folder which contains the cli-setup.exe for upgrading Engine locally on each server node. Copy that catalog folder from the EMS console machine to the C:\ProgramData\Neverfail-Protected folder of Active node. This will assure the cli-tools will get replicated by Engine to all of the Passive 
Start the upgrade process on the Passive server by performing the steps below.
Open a CMD prompt under 'Run As Administrator'
Set the path to C:\ProgramData\Neverfail-Protected\Catalog
Run the command engine-cli-setup.exe upgrade

- Repeat steps a to c on the Active server
Applies To
Neverfail Continuity Engine
Related Articles
Welcome to Continuity Engine 19 - What's New
Continuity Engine 19 This release supersedes Continuity Engine v18. What's New Windows Server 2025 Support Supported deployment of Continuity Engine components: EMS Web Console, Engine, Scope, Cli, Utilities. Support for System Plugin, IIS Server ...
Welcome to Continuity Engine 18 - What's New
Continuity Engine 18 This release supersedes Continuity Engine v17. What's New In-Product Notification Streamlined communication between customer's Engine Management Service and Neverfail's Notification Services. Easy-to-absorb messages fed directly ...
Welcome to Continuity Engine 17 - What's New
Continuity Engine 17 This release supersedes Continuity Engine v16. What's New Licensing Service Access only for Supported Versions Important: Engine Management Services (EMS) upgrade to v17 is required for maintaining access to Licensing Services. ...
Welcome to Continuity Engine 13 - What's New
Continuity Engine 13 This point release supersedes Continuity Engine v12.1. What's New Better User Experience Subscription's Payment Status Exposed in EMS UI Starting Continuity Engine 13, EMS UI is showing the payment status of the software ...
Welcome to Continuity Engine 12 - What's New
Neverfail Continuity Engine 12 What's New Automated Split-Brain Avoidance Configuration Improvements Split-Brain Avoidance auto-configuration task will execute only if automated failover is enabled. Continuity Engine 12 monitors the management ...