Managing And Patching Neverfail Continuity Engine Clusters Using Passive Node Management Feature With Ivanti Endpoint Manager

Summary

This article provides information on how to manage or patch Neverfail Continuity Engine clusters through Ivanti Endpoint Manager, using Passive Node Management feature.

Prerequisites

Ivanti Endpoint Manager

Note: In the following sections we'll assume that Ivanti Endpoint Manager is enabled/configured in your organization.

Enable Passive Node Management through Identity

Neverfail Continuity Engine servers should be able to access Ivanti Endpoint Manager 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 Ivanti Endpoint Manager must be configured on each node, in order to be able to connect to Ivanti Endpoint Manager when both in active or passive role. The DNS name resolution option needs to be configured for the management IP address from Server Configuration Wizard.

Ivanti Endpoint Manager Agent Configuration

Using Ivanti Management Console configure the agent intended to be deployed on the Engine nodes to use Ivanti Endpoint Manager Server's IP address rather than fully qualified domain name in Client Connectivity settings > Core address.

Managing a Neverfail Engine Cluster

Deploy Ivanti Endpoint Manager Agent on Neverfail Continuity Engine Cluster

Ivanti Endpoint Manager Agent is a software that should be installed on the managed-to-be servers. This agent connects to the Ivanti Endpoint Manager Server providing information related to machine status, etc., as well as means of remote support, security and patch, auditing, reports, etc. 

From Tools → Configuration → Unmanaged Device Discovery, do a network scan by Public IP address and Management IP address for both Active and Passive.

From Tools → Configuration → Agent Configuration, do a Schedule agent deployment.

For this step, configure the task, add Active server by Public name and Passive server by Management Name as shown in example:

Note: If Agent fails to be deployed via Ivanti Manager scheduled task, then use the other options of installing it (self-contained MSI, Advance Agent..).

Manage Neverfail Continuity Engine from Ivanti Management Console

All the Engine Cluster nodes registered in Ivanti Management Console can be managed or patched no matter if they're active or passive.

Performing a Neverfail Engine switchover 

Note: After switchover, in Ivanti Management Console, there will be a delay of few minutes until the Device name is updated.

Here's an example of expected behavior when Neverfail Engine clusters changes the active server (switchover):

Management Identity configuration: 

Physical Hardware Identity	Management Name	Public Name
Primary	ag-ivanti-p	AG-Ivanti
Secondary	ag-ivanti-s	AG-Ivanti

Assets before switchover displayed in Ivanti Management Console:

Assets after switchover displayed in Ivanti Management Console:

Applies to

Ivanti Endpoint Manager 2020.1

Neverfail Engine CE 2021 Management Service (V9.0) and later

• Related Articles

• Managing And Patching Engine Clusters Using Passive Node Management Feature With SolarWindws Patch Manager

  Summary This article provides information on how to manage or patch Neverfail Continuity Engine clusters through SolarWindws Patch Manager, using Passive Node Management feature. SolarWindws Patch Manager requirements Prerequisite: SolarWindws Patch ...

• 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 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 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 ...

• 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 ...