Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With Kaseya VSA Cloud Portal

Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With Kaseya VSA Cloud Portal


This article provides information on how to manage or patch Neverfail Continuity Engine clusters through Kaseya VSA Cloud portal, using Passive Node Management feature.


Kaseya VSA active account

An active logon account is needed for accessing Kaseya VSA Cloud portal management solution.

Enable Passive Node Management

Neverfail Continuity Engine servers should be able to access Kaseya VSA Cloud in order to be managed remotely from there.

  • On the active server this can be achieved through the Public IP address or through a Management IP Address. 
  • On the passive server, this can be achieved only through a Management Name and IP Address.

Thus, a Management Name and IP Address with access to Kaseya VSA must be configured on each node, in order to be able to connect to Kaseya VSA Portal when both in active or passive role.

Managing a Neverfail Engine Cluster

Create Kaseya VSA Agent

Kaseya Agent is a software that should be installed on the managed-to-be servers. This agent connects to the cloud portal providing information related to machine status, etc., as well as means of remote support, patch management, auditing, reporting, scripts scheduling. 

To create an Agent, on Kaseya VSA Portal:

  1. Go to Agent
  2. Press Packages
  3. Press Manage Packages
  4. Press Create

Agent creation wizard offers the option of specifying machine Id and group Id naming rules convention - for example, in the picture below, Computer Name and Domain Name are selected as naming rules convention.


Deploy Kaseya VSA Agent on Neverfail Continuity Engine Cluster

After its creation, the Kaseya VSA Agent should be deployed on the managed-to-be devices, i.e. Engine cluster nodes. After the installation, the managed nodes will be visible on the management portal> Agent -> Agents: notice the public name ("ag-kaseyatest") configured for the active node and the Engine management name ("ag-k-s") configured for the passive server:



The Machine id, displayed on the Kaseya VSA portal, remains always the same and won't change when an Engine switchover occurs. This is an expected behavior as the Agent remains registered with its configured name rule - in this case based on Computer Name and Domain Name.  But if you run an audit from: Audit -> Collect Data -> Run Audit  you can see the Computer Name changes accordingly in Audit -> View Group Data -> Audit Summary for each Engine node according with its actual name (new active node will be configured with public name; passive server will be configured with its management name):

Assets before switchover:



Assets after switchover:



To avoid any potential confusions, the Kaseya Agent may be configured with Prompt User - asks user to enter Machine Id during its creation, hence when installed one may enter ServerName-Primary; ServerName-Secondary; ServerName-Tertiary.

Manage Neverfail Continuity Engine Cluster

All the Engine Cluster nodes registered in Kaseya VSA Cloud Portal can be managed or patched no matter if they're active or passive.


Applies to

Kaseya VSA Cloud Portal

Neverfail Continuity Engine 8.5 and later