Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With ConnectWise Automate
Summary
This article provides information on how to manage or patch Neverfail Continuity Engine clusters through ConnectWise Automate (Web Control Center or Automate Control Center), using Passive Node Management feature.
Prerequisites
ConnectWise Automate active account
An active logon account and valid license is needed for accessing ConnectWise Automate Web Control Center management solution. Here you have access to Agent or Automate Control Center installers.
Note: In the following sections we'll assume that ConnectWise Automate is enabled/configured in your organization.
Enable Passive Node Management
Neverfail Continuity Engine servers should be able to access ConnectWise Automate 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 ConnectWise Automate must be configured on each node, in order to be able to connect to ConnectWise Automate Portal when both in active or passive role.
Managing a Neverfail Engine Cluster
Deploy ConnectWise Automate Agent on Neverfail Continuity Engine Cluster
ConnectWise Automate Agent is a software that should be installed on the managed-to-be servers. This agent connects to the ConnectWise Automate portal providing information related to machine status, etc., as well as means of remote support, patch management, auditing, reporting, scripts scheduling.
A way of deploying the agent on the managed-to-be Engine nodes is to download the Agent from the ConnectWise Automate Web Control Center > System> Installers then to manually install it on each node to be managed.
After the installation, the managed nodes will be visible on the ConnectWise Automate Web Control Center and Automate Control Center: notice the public name ("ag-cw") configured for both the active and passive nodes is used - this is a limitation of how Agent retrieves and broadcasts the Computer Name to the management portal. However, you can differentiate the nodes by their managed IP addresses:
Important:
The Computer Name, displayed on ConnectWise Automate 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. But if you open a Control window for each Engine node, then you'll see the its actual name (new active node will be configured with public name; passive server will be configured with its management name):
Manage Neverfail Continuity Engine Cluster
All the Engine Cluster nodes registered in ConnectWise Automate can be managed or patched no matter if they're active or passive.
Applies to
ConnectWise Automate
Neverfail Continuity Engine 8.5 and later
Related Articles
Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With GFI LanGuard
Summary This article provides information on how to manage or patch Neverfail Continuity Engine clusters through GFI LanGuard, using Passive Node Management feature. Prerequisites GFI LanGuard Server Note: In the following sections we'll assume that ...Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With IBM BigFix
Summary This article provides information on how to manage or patch Neverfail Continuity Engine clusters through IBM BigFix (also known as IBM EndPoint Manager, Tivoli Endpoint Manager), using Passive Node Management feature. Prerequisites An IBM ...Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With Windows Server Update Services (WSUS)
Summary This article provides information on how to manage or patch Neverfail Continuity Engine clusters through Windows Server Update Services, using Passive Node Management feature. Prerequisites WSUS Server A WSUS server must be present and ...Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With Cloud Management Suite
Summary This article provides information on how to manage or patch Neverfail Continuity Engine clusters through Cloud Management Suite, using Passive Node Management feature. Prerequisites Cloud Management Suite active account An active logon ...Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With Kaseya VSA Cloud Portal
Summary This article provides information on how to manage or patch Neverfail Continuity Engine clusters through Kaseya VSA Cloud portal, using Passive Node Management feature. Prerequisites Kaseya VSA active account An active logon account is needed ...