Install N-able N-central on a physical server

Before you begin the install, ensure your install media is set up and ready. For more information, see Prepare installation media.

  1. Configure the server RAID array using the following settings:

    HP Server

    Cache Options

    Set to 50% Read and 50% Write.

    Disk RAID 1+0

    Configure the RAID controller to use the default stripe size.

    Lenovo Server

    Cache Options

    Use the default settings.

    Disk RAID 1+0

    Configure the RAID controller to use the default stripe size.

    Dell Server

    Cache Options

    Set Write Policy to Write-back and Read Policy to Adaptive.

    Disk RAID 1+0

    Configure the RAID controller to use the default stripe size.

    Intel Server

    Cache Options

    Set Write Policy to Write-back and Read Policy to Adaptive.

    Disk RAID 1+0

    Configure the RAID controller to use the default stripe size.

  2. Enter the Server Hardware Level Configuration Utility (BIOS) and enable the UEFI Firmware booting.
  3. Insert the installation disc or USB Flash drive and restart the server.
  4. If using a USB drive, use the BIOS/UEFI Boot Menu to select the USB Flash Drive as your boot device.
  5. If the Press the <ENTER> key to install N-central prompt displays, click Enter.
  6. This will not display if you have Secure Boot enabled.

  7. Click Enter to Install N-able N-central unless you want to test the physical media or need to install in text only mode (usually if you are using a serial console). Otherwise select the desired boot option and click Enter.

    After a few moments, you should be prompted to provide the N-able N-central network settings. If you are not prompted to provide the network settings, N-able N-central was unable to locate a suitable network card. Turn off the server and verify the network card before re-trying the N-able N-central installation.

  8. Select which IP stack/s you need to enable (IPv4 only, or both IPv4 and IPv6). Click Tab to highlight OK and click Enter.
  9. Select your IPv4 network configuration. N-able recommends using a Static IPv4 Address. Tab to OK and click Enter.
  10. If you selected to use a dual stack configuration, select your IPv6 network configuration. N-able recommends using a Static IPv6 Address. Tab to OK and click Enter.
  11. If you selected a Static IPv4 Address configuration, enter the IP Address, Netmask, Gateway and Nameservers (CloudFlare’s 1.1.1.1 has been pre-populated by default). Tab to OK and click Enter.
  12. If you selected a Static IPv6 Address configuration, on the next screen enter the IP Address, Prefix Length (/64 is the most common), Gateway, and Nameservers (CloudFlare’s 1.1.1.1 has been pre-populated by default). Select OK and click Enter.
  13. On the next page, select your desired Time Zone. Tab to OK and click Enter.

    Be sure to Adjust the Time Zone to match your desired location. If you are restoring a N-able N-central Backup, the Time Zone must be an exact match to the server from which you are restoring the Backup.

    If your location is not listed, be sure to select a location that is in the same time zone as you are.

  14. The Operating System Installer will now be launch. No further input is required on the server console. When the install completes, please go to the indicated web URL to continue configuring N-able N-central.

Ensure you remove the DVD/USB Flash Drive once the Green complete screen appears to ensure that the server does not boot from the DVD/USB Flash Drive at a later time.

HPE ProLiant Generation 9 and older servers will have the HPE monitoring drivers installed and SNMP enabled on the N-able N-central server. You must use the Community String N-CENTRAL_SNMP to monitor your N-able N-central server.

HPE ProLiant Generation 10 or newer servers no longer use the Operating System drivers to monitor the hardware. Hardware monitoring is handled through the iLO port.

Dell PowerEdge servers may be monitored through the iDRAC port depending on the server feature set and licensing.

Lenovo servers may be monitored through the IMM port depending on the server feature set and licensing.

What's next?

With N-able N-central installed: