Neverfail Engine Advanced Management Client (Portable) Requirements

Neverfail Engine Advanced Management Client (Portable) Requirements

Neverfail Engine Advanced Management Client (Portable) Requirements

Last Updated: April 1, 2026

Article ID: KB-2026-AMC-01

Product: Neverfail Engine

Version: All Supported Versions

Summary

To facilitate remote administration of Neverfail Engine clusters without a local installation footprint, the Engine Advanced Management Client (AMC) Portable edition may be utilized. This article outlines the environment and configuration requirements necessary to ensure secure and stable communication between the Portable AMC and the Managed Engine.

Requirements

1. Deployment and Directory Selection (Client Machine)

Before utilizing the portable binaries, the following staging requirements must be met:

  • Download Source: The Advanced Management Client - x64 - Portable package must be obtained via the Neverfail Engine Download page.

  • Extraction Location: The package must be extracted to a stable, root-level directory (e.g., C:\EngineClient\).

  • Note: Execution from "Special" Windows folders (e.g., Downloads, Desktop, or Temp) is strictly discouraged. Utilizing a dedicated root path avoids legacy Windows path-variable limitations and ensures consistent Firewall rule enforcement.

2. Managed Engine Configuration

To permit remote administrative access via TCP, the following configurations must be applied to the Engine environment:

  • Trusted Client Authorization (Engine Level):

    Authorization must be granted on each Managed Engine intended for control. Run the following command from the binaries directory to register the Client Machine IP:

    cd "C:\Program Files\Neverfail\R2\bin"

    nfcmd localhost addTrustedClient [Client_Machine_IP] [Username] administrator

  • Node Firewall Configuration (Cluster Level):

    This requirement must be fulfilled on every individual node within the Managed Engine cluster. An Inbound Rule must be created to allow TCP traffic for the management service:

    • Protocol: TCP

    • Program Path: %ProgramFiles%\Neverfail\R2\bin\NFServerR2.exe

    • Action: Allow Connection

3. Client-Side Firewall Configuration (Client Machine)

To facilitate inbound TCP communication from the Managed Engine, the Client Machine must satisfy one of the following firewall requirements:

MethodRequirement Detail
Option A (Application Specific)Inbound Rule (TCP) for the specific GUI executable: [Path_To_Portable_Folder]\bin\nfgui.exe
Option B (Network Specific)Inbound Rule allowing TCP traffic originating from the specific Managed Engine IP address(es).

4. Connectivity Validation

To verify the requirements have been met:

  • Launch the Portable AMC (nfgui.exe) from the designated directory.

  • Add the connection to the remote server using the Managed Engine Public IP address.

  • The connection must be configured with a valid username and password.

Technical Support

For further assistance regarding the configuration of the Portable AMC, please contact Neverfail Support via the Support Portal.

Applies To

Neverfail Engine - all supported versions