Announcing the GA of N-central 2023.7 HF1

N-central 2023.7.0.11

2023.7 HF1 Release Notes (PDF)

Download Now

NEW! Release Video

What’s New in N-able N-central 2023.7 HF1

N-central 2023.7 brings some welcome changes for Patching with Intune, and Device Management for Apple! As always, several bug fixes are included as well. Please review the detailed list of Fixed Items later on in this document for more details!

Device Management for Apple Improvements (NCOD only)!

These changes will come to OnPrem in a future release.

All NCODs will now have the ability to enroll iOS and iPadOS devices into Device Management for Apple. You will no longer be able to enroll Apple or Android devices into our Legacy MDM service.

Apple Business Manager zero touch deployment

We are pleased to announce that you can now enrol your devices via Apple Business Manager. Doing so enrols your ABM purchased device or freshly wiped device into Device Management for Apple and, for your Apple workstations, will also deploy the latest N-central mac agent to your device upon completion of the boot up process.

App Deployment

We are pleased to announce the addition of App Store management to N-central’s Device Management for Apple. Ncentral can now receive a token from an Apple Business Manager or Apple School Manager account and deploy App Store purchases made in those accounts to deploy company-owned apps to Macs, iPhones, iPads, and even AppleTVs enrolled in N-central.

This means that end-users of the devices won’t need to use a personal Apple ID or some other workaround to get the business apps they need on managed devices. You’ll be able to ensure they have all the apps they need, revoke the licenses as needed, and keep the apps up-to-date.

N-central’s Device Management for Apple is multi-tenant, meaning you can set up the tokens for each customer’s own ABM/ASM account in one dashboard.

Devices don’t need to have been enrolled in N-central via ABM/ASM. Purchased apps can be deployed to devices that were manually enrolled also.

OS Update Commands

There are up to 5 options in the command API:

  • Download or install the update, depending on the current state. This lets the OS decide which action it should take based on whether a user is logged in and working or its configuration. This is the safest option and should be considered a default.
  • Download the software update without installing it.
  • Download the latest update and trigger the restart countdown: In iOS and tvOS, this will install a previously downloaded software update. In macOS it will download the software update and trigger the restart countdown notification via Notification Centre.
  • Download the software update and notify the user through the App Store. This option is only available in macOS.
  • Download or install the latest update, force a restart if required: As it says, this will do the default action, but will make a restart mandatory. This could result in data loss from unsaved work. This option is only available in macOS.

Here are some important things to know about these commands:

  • DMA can only send the command to the device. It’s up to the device to obey the command. Sometimes it won’t. We expect that Apple’s APIs and implementation will improve as new OS version are released. It’s already far more reliable on macOS Ventura than it was on previous macOS versions. N-able is only supporting these commands on macOS 13 Ventura and iOS 16 or later.
  • The commands may succeed on previous OS versions, but they will always download and install the latest full OS version. For example, if you run the command on macOS 12 Monterey, it may or may not execute reliably, and if it does it will upgrade the device to macOS 13 Ventura.
  • The behavior of these commands can be modified via Configuration Profiles.
  • A lot also depends on whether the device has been provisioned as Supervised. Supervised devices, including those enrolled in DMA by way of Apple Business Manager/Apple School Manager automatic enrolment are far more likely to behave as desired. Non-Supervised devices will likely require user input to complete the process.

Agent Only Required Apple Updates

Managed Patch

We’ve added third-party patching as a Task or Scheduled Task for your Mac devices.

Managed Patch automatically deploys verified third-party software updates for supported products via Munki client software.

Your task output will show the list of third party apps that were updated. See the full list here.

Remote Command Line/File System

You can now launch a Command Line of File System window from N-central and send commands and Transfer files without the end user being aware of your presence on their device.

Changes to Left Menu!

In N-central 2023.7, you’ll notice a new left hand menu for Cove Data Protection! If you aren’t using Cove Data Protection yet, check out the links to learn more about Cove and start a free trial! If you’ve been using N-able Backup, your submenus have been moved to be under the new Cove menu.

Patching for Intune managed devices!

Earlier in the year devices registered within Intune were struggling to initiate patches from within Intune if they have Ncentral patching enabled. This is due to a change by Microsoft within Intune where it would no longer work if another vendor had set specific registry key values set. These values have always been in use when our patch is enabled and both worked side by side for a long time.

To solve this we have enhanced the enabling patch options to include the choice of native OS patching alongside the existing third-party patching check box.

This functionality will allow you to choose between us controlling or not controlling the OS patching whilst providing third-party patches for devices that are set to have the OS updated by Intune.

Please also be aware that the ‘Enable Native OS Patching’ option is going to be renamed in a future N-central version.

Upgrade paths and notes

IMPORTANT: For those that have a Custom (OpenID Connect) SSO configuration, a change was made in 2023.6 that requires a modification to the configuration when you upgrade. This change could impact your user’s ability to log into N-central! For more information, please read the following KB article.

Upgrade versions

To upgrade to N-able N-central 2023.7 HF1, your N-able N-central server must be running one of the following versions:

View versions:
  • N-able N-central 2022.7.1.44
  • N-able N-central 2023.4.0.32
  • N-able N-central 2023.5.0.12
  • N-able N-central 2023.6.0.9
  • N-able N-central 2023.7.0.10

Notes the following when upgrading N-able N-central.

Tasks may expire if the agent on an associated device is being upgraded when the task is scheduled to be completed. Agent upgrades are normally short in duration but may be delayed if a re-start of the device is pending.

Fixed Issues in N-able N-central

Release 2023.7

2023.7 HF1 GA

CoreProbes Repeatedly Downloading Repository FilesNCCF-142868

2023.7 GA

Core[USABILITY] Azure SSO Not Advancing Session TimeoutNCCF-119293
Core[USABILITY] Azure SSO IDP User Does Not Respect the User Timeout SettingNCCF-99445
CoreResolved an issue not properly restricting user privilegesNCCF-134722
CoreLaunchDarkly Processing Regarding Analytics EventsNCCF-125866
CoreAutomated N-central OS Package Update – August 16, 2023NCCF-123491
CoreN-central does not provider user id / username fields to Azure Resource Manager GetUserToken endpointNCCF-121844
CoreHide Cloud Commander Setup when NOT at SO LevelNCCF-117957
CoreCloud Commander Navigation for Azure Resource ManagerNCCF-117597
CoreIncrease timeout for XMPP startupNCCF-115736
CorePop Up Box Each time you log into a deviceNCCF-113878
CoreAutomated N-central OS Package Update – July 17, 2023NCCF-113077
CoreDevice Overview Active Issues tab does not show all active issuesNCCF-15517
CoreFully Disable Outbound CommunicationNCCF-16757
CoreNAC Recreate an Advanced Scripts pageNCCF-37467
CoreDMA Hide ‘Administration > Certificate Management’ menuNCCF-41139
CoreNAC Version Management Upload upgrade file to server stops showing progressNCCF-42273
CoreNAC Version Management Cancel file upload shows old nacintegration admin pageNCCF-42302
CoreNAC remove the cancel button from all Service Management pagesNCCF-42581
CoreNAC Edit Device Class Does Not Appear to WorkNCCF-48196
CoreProvide access group customer-based user permissions to C2C integrationNCCF-52105
CoreInitial Application of Security Manager Does Not Reflect DatabaseNCCF-58876
CoreJavaScript based Google SSO is being deprecatedNCCF-62750
CoreIncorrect case on “multi-session” Causing System ErrorsNCCF-75605
CoreNAC should only be visible on the System levelNCCF-84572
CoreAgents not upgrading from probesNCCF-87866
CoreDMA Maintenance task to process Unenroll command queueNCCF-90252
Managed Services for AppleAdd Apps & Books Permission to Default Administrator RoleMSAD-3137
Managed Services for ApplePermission Update for DMA UI accessMSAD-3112
Managed Services for AppleAdd new script to Mac Script RepositoryMSAD-2945
Patch Management[FEATURE] Support 3rd party patching on Intune enabled devicesPMCM-2081
Release 2023.6

2023.6 GA

Automation ManagerPendoLog – Scheduled Task on hosts without Engine pointing to C:Program Files (x86)N-able TechnologiesAutomationManagerX.XX.X.XAutomationManager.PendoLogUploader.exeAM-3716
Automation Manager PendoLog exception – Could not find a part of the path ‘C:ProgramDataN-Able TechnologiesAutomationManagerLogs’AM-3715
Automation Manager PendoLog exception – Pendo next schedule check exception. The system cannot find the file specified.AM-3714
Automation ManagerUpdate ActivityObject.ttAM-3698
Automation ManagerPolicyExecutionEngine.dll.config log rotation – 0kb log files presence issueAM-3686
Automation Manageram-runner first release 0.0.1AM-3685
Automation ManagerPendo amend upload procedureAM-3684
Automation ManagerUpdate AM Assembly List On Jenkins And Test NC/RMM UpdatesAM-3469
Automation ManagerIntegrate “PendoManager” Into The Existing AM ArchitectureAM-3468
Automation ManagerCreate Console Application “PendoManager” To Filter And Upload Logs To PendoAM-3467
Automation ManagerCreate Special Module Name “PendoLog” Into The Existing AM LogsAM-3466
Automation ManagerAM policy is crashedAM-3385
Automation ManagerRevise the devices’ Get Capabilities method by removing or adding new PS module installation checksAM-3384
Automation ManagerPolicyExecutionEngine.dll.config log rotation neededAM-3365
Automation ManagerCopy File Object revision – new behavior introduced under
Automation ManagerRun Policy Object Policy Name:* window opens as many times it was clickedAM-3310
Automation ManagerRun Policy Object generates a System.ArgumentNullExceptionAM-3309
Automation ManagerError 201 Failed to stop execution of automation policyAM-3297
Automation ManagerTLS Certificate OCSP and CRL validation requiredAM-3270
Automation ManagerAutomation ManagerAM-3268
Automation ManagerUpdate Links to training videosAM-3161
Automation ManagerAM Object – SetRegistryValue should not display incorrect reason for an errorAM-3069
Automation ManagerPrompts not working from RMM under admin accountAM-3043
Automation ManagerGet Windows Events for Security should show audit success/ failure as entry typeAM-2978
Automation ManagerAdd reset functionality to branding settingsAM-2977
Automation ManagerDNS Zones List / Set DNS Scavenging – Shows Result 1 with no error /explanation messageAM-2693
Automation ManagerAM – Potential ReDos – remove unnecessary regex-like string from logAM-2570
CoreCSR Generation Mixes up “Organization Unit” and “Email”NCCF-126316
CoreCloud Commander Role Permissions Options are DisabledNCCF-108107
CoreDFM files are deleted causing missed records upon Data ExportNCCF-106807
Core“Backup Windows Event Log” Automation Policy generates a System ErrorNCCF-94381
CoreLinux agent installation script stops to go through address list defined in activation key when alien n-central FQDN is met.NCCF-94197
CoreNew Friendly Password Reset Message Does Not Match Password ComplexityNCCF-92397
CoreNew Notification Template Tag: Custom UI PortNCCF-83792
CoreUpdate filtering to include DNSFilter StandaloneNCCF-82415
Core‘envoy_proxy_UI.log’ Not Configured For Log RotationNCCF-81833
CoreAgent Probe Overview Report Showing Wrong Agent Version For MacNCCF-73595
CoreUI Doubling AMP UID JSP PointersNCCF-72129
CoreDeprecated Feature ‘Network’ Still Listed in the UINCCF-68485
CoreHide Custom Services from use on a MacNCCF-66230
CoreFailed Agent installation on 2 Linux serversNCCF-32511
CoreTake Control role permission does not limit the use of Take ControlNCCF-22910
CoreN-central Backup download request are killed after 5 minutesNCCF-17591
CoreCustom Service monitoring evaluation is incorrectNCCF-17319
CoreThe TTL and RTT Values in the Connectivity Service Are Affected When There Is Packet LossNCCF-17318
CoreNavigation Scroll bar is not visible on Firefox 87.0 on new N-central themeNCCF-16148
CoreAllow The Device Name To Be Copied From The Device-Level HeaderNCCF-15072
CoreAttention alert for agent is shown in install wizard for probeNCCF-13246
CoreServices can be added to Service Template with empty ‘Scan Interval’ fieldNCCF-9794
Ecosystem FrameworkAdd Messaging to Avoid Internet Loss when Deactivating DNSFINT-1250
Ecosystem FrameworkWhen a profile is assigned to a device, in Intune there’s no indication that it is assigned to that deviceINTUNE-313
Ecosystem FrameworkIntune should check for setup completed task for the parent, instead of site level setupcompleted.INTUNE-213
Ecosystem FrameworkDnsf sync job does not work properly if any other integrations are activatedINT-1259
Ecosystem FrameworkDnsf cleanup job does not work properly if any other integrations are activatedINT-1258
Ecosystem FrameworkECO_DNSFILTER_SEC missing sometimes from “configtype” tableINT-1166
Ecosystem FrameworkNC agent to uninstall Eco agent based on device UUID (not Publisher)KUIP-4263
Ecosystem FrameworkUpdate N-central Ecosystem Grpc Service to latest versionKUIP-5020
Ecosystem FrameworkIncorrect logging usage, causes excessive logging to journalctlKUIP-3453

Known Limitations

These items for the current version of the N-able N-central software is composed of material issues significantly impacting performance whose cause has been replicated by N-able and where a fix has not yet been released. The list is not exclusive and does not contain items that are under investigation. Any known limitations set forth herein may not impact every customer environment. The N-able N-central software is being provided as it operates today. Any potential modifications, including a specific bug fix or any potential delivery of the same, are not considered part of the current N-able N-central software and are not guaranteed.

Agents and Probes

New Windows Agent installations must have a valid FQDN as the first entry in the server address list in order to install successfully. Upgrades and existing agent communication should continue to work as expected.
Communication issues may be encountered for N-able N-central Probes installed on Windows servers that have multiple NICs. For more information, refer to “KBA20020: Configuring A Server With Multiple NICs” in the online Help.67778
Automation Manager

Running Automation Manager Policies created using Automation Manager 1.6 or earlier may result in Failed to create an EndDate … errors if the Policies are run on a computer using a different date format. This issue does not affect Policies created using Automation Manager 1.7 or later.65712
Custom Services

Custom services may appear as misconfigured when the system locale of the device is not set to English. For example, in Portuguese the default decimal in c#/.net is not a period, “.”, it is a comma, “,”. If you are having this issue, please contact N-able Technical Support.65288
Core Functionality

Installing N-able N-central on Servers that have an Nvidia Video Card
Due to a bug in CentOS 7 with Nvidia’s “Nouveau” driver, installing N-able N-central on servers that have an Nvidia video card may result in the N-able N-central console showing a blank screen, or displaying an Anaconda Installer screen with an error message about the video card driver.
HDM doesn’t not work with the “Last 5 Tickets” widget.NCCF-10855

Modifying a Dashboard that is associated with a large number of services may cause performance issues when using the Firefox browser.70326
PSA Integration

In some instances, tickets closed in PSAs are not being cleared in N-able N-central. This is likely because the ticketing recipient profile in N-able N-central has Do not change the Ticket Status selected (in order to manually configure tickets). Then, when the ticket is removed in the PSA, N-able N-central will not be able to update/resolve the ticket’s status and new tickets
cannot be created for the same issue. Until a solution is available through the UI for this situation, the work around is to set a Return to Normal status and set a non-used status in the ‘updatable statuses’ section or set the same status as the return to normal one. This will cause N-able N-central to add a note to the ticket on return to normal but will not alter the ticket’s
status. This will allow the stale ticket check to remove the ticket from the system.

After re-naming, the Names of files or Registry entries may not be displayed properly in the File System window and the Registry window of the Tools tab when using Internet Explorer.68149
User Access Management

Login window reappears when new tab is loaded.

When already logged into N-central and a user opens a new tab and browses to N-central from this new tab, the login screen reappears yet the user is already logged in. The left hand navigation is functional.

Available Ciphers for Non Agent/Probe Communication with N-central

View ciphers




TLS 1.2:





End of support

The following are being deprecated in a future release of N-able N-central:

Linux Agent SupportDue to declining usage in the field, the N-able N-central Linux agents will stop supporting CentOS 6, Ubuntu 14.04 and the 32- bit version of Ubuntu 16.04, in a future release.
Internet Explorer 11Due to declining usage in the field, a future release of N-able Ncentral will drop support for the Internet Explorer 11 web
AV Defender 5.xAs of next major release for those of you still utilizing the AV5
Bitdefender Antivirus be advised that monitoring from our AV5
agents will no longer continue. As a result this will leave your
environments in a vulnerable state. We encourage you to
review your agents to ensure you are now utilizing our latest
AV6 agents. Reminder that our online help for Security Manager is available for your reference.
Windows 8.1/Windows Server
2012 R2
As older Windows Server and Desktop Operating Systems
transition into Microsoft’s Extended Support Phase and
beyond, they are no longer receiving OS level TLS version and
cipher updates (SCHANNEL). As the .NET Framework relies on
SCHANNEL for TLS based communications, and as newer
vulnerabilities are discovered in the ciphers available to these
older Operating Systems, the available Strong Cipher list for
these devices continues to shrink. We continually review the
ciphers used by N-central’s Modern Security Profile, to ensure
we offer only secure ciphers. At this time, there are only two (2)
secure RSA key based ciphers available to Windows Server 2012
R2/Windows 8.1 and older. N-central will endeavor to support
these two ciphers in our Modern Security profile for as long as
they remain secure, but there may come a time where we will
need to drop Official support for these Windows versions
before the end of their Extended Support Phase. If/when this
does occur, they will still be able to connect if you switch to the
Legacy Security Profile, but this will reduce the security of all
devices connecting to your N-central server.

If you monitor Windows Server 2003/2008/Windows XP/Vista
devices, we would like to advise you that we will be dropping
support for the “TLS_RSA_WITH_3DES_EDE_CBC_SHA” cipher in a future release. Coming changes to the web front end that will support TLS 1.3, have been identified as also disabling “TLS_RSA_WITH_3DES_EDE_CBC_SHA” due to the required version of OpenSSL. Fully patched Windows Server 2008/Vista devices should be able to connect to N-central on the Legacy
Security profile, using one of the newer, but still weak ciphers.
Windows Server 2003/XP will no longer be able to communicate
over TLS/HTTPS at that time (using a site-to-site VPN between
your firewall devices, and connecting over HTTP may still work).
32-bit versions of
the Windows, Linux and macOS
operating systems
The number of 32-bit Operating Systems monitored by Ncentral has continued to drop over the past few years. Windows Agents/Probes have historically been 32-bit, with some 64-bit specific components. In a future release, we intend to convert the Agent and Probe code base to be a native 64-bit application; this will mean a hard deprecation of support for 32-bit Windows versions. N-central’s Linux and macOS agents will follow a similar path.

N-able N-central System requirements

The following requirements are for typical usage patterns, acknowledging that some patterns may require greater system resources for a N-able N-central server than others.

If you have any questions about how your needs affect the system requirements of your N-able N-central server, contact your Channel Sales Specialist or email

ProcessorServer class x86_64 CPUs manufactured by Intel or AMD (i.e. Xeon or EPYC). Please refer to the Red Hat Hardware Ecosystem for further details
You do not need to install a separate Operating System to run N-able N-central. The N-able Ncentral ISO includes a modified version of CentOS 7, based on the upstream Red Hat Enterprise Linux 7.
The physical server used to install N-able N-central in a bare metal environment must be certified to run Red Hat Enterprise Linux 7.7 (x64) by Red Hat, or the hardware vendor, without any additional drivers. Please check the Red Hat Hardware Ecosystem for details.

Server Grade hard drives connected to a RAID controller with a Battery/Capacitor Backed Cache are Required. Examples include 10K+ RPM SCSI or SAS drives, Enterprise Grade SSDs or NVMes for bare metal and virtualized hosts, or a Fibre Channel connected SAN with Enterprise Grade hard drives for virtualized hosts (Fibre Channel cards can be used for bare metal if they are configured in the pre-boot environment and do NOT require vendor-provided drivers).

Although Desktop Hard Drives will work with the Operating System, they do not meet the minimum throughput required for the back-end Database of N-able N-central.

For more details, please refer to the Red Hat Hardware Ecosystem to see if your current hardware will work with our customized version of CentOS 7.

System requirements by number of devices managed

The table below lists the minimum specifications required to manage the number of devices indicated (based on average usage). Performance can be improved by exceeding these requirements. When determining your hardware requirements, consider any growth in managed device count that may occur over time.

View more

Number of devicesCPU CoresMemoryStorage
Up to 1,00024 GB RAM80 GB RAID
Up to 3,00048 GB RAM150 GB RAID
Up to 6,000816 GB RAM300 GB RAID
Up to 9,00001224 GB RAM450 GB RAID
Up to 12,0001632 GB RAM600 GB RAID
Up to 16,0002248 GB RAM800 GB RAID
Up to 20,0002864 GB RAM1 TB RAID
Up to 24,0003480 GB RAM1.2 TB RAID


  1. Server Grade hard drives connected to a RAID controller with a Battery/Capacitor Backed Cache, are required to ensure performance and unexpected power-loss data protection.
  2. In a virtualized environment, hard drives for the N-able N-central server must not be shared with any other applications or VM guests that have significant I/O workloads. For example, Report Manager, SQL Databases, E-Mail Servers, Active Directory Domain Controllers, SharePoint, or similar should not be installed on the same physical hard drive as N-able N-central.
  3. N-able recommends two or more hard drives be placed in a redundant RAID configuration. With two drives, RAID 1 must be used. With more than two drives, RAID 1+0 or RAID 5 are recommended. RAID 6 is an option on servers with less than 1,000 devices (the additional write latency of RAID 6 becomes an issue above 1,000 devices).
  4. N-able recommends more, smaller disks in a RAID array, as opposed to fewer larger disks. Databasebacked applications, like N-able N-central, have better write performance with an increased number of parallel writes (hard drives).
  5. If using Solid State Drives (SSDs), N-able requires Enterprise Grade, SLC based (or better) SSDs with a SAS interface, or Enterprise Grade NVMes. SSD and NVMe drives must have an endurance rating of at least 0.2 DWPD (Drive Writes Per Day), and at least 2 physical disks in a redundant RAID array. On Bare Metal servers, the RAID array must appear to the operating system as a single Block or NVMe Device. Currently, many PCIe and NVMe drives do not meet this last requirement and would only work in a virtualized environment.
  6. Configure the RAID controller to use the default stripe size and a Read/Write cache of 50%/50%.

The underlying customized version of CentOS 7 has certain hardware limits that are consistent with the upstream Red Hat Enterprise Linux 7 distribution. Of note are the following:

Minimum disk space80 GB
Maximum physical disk size (BIOS)2 TB
Maximum physical disk size (UEFI)50 TB
Required minimum memory4GB for 4 or fewer logical CPUs

1GB per logical CPU for more than 4 logical CPUs
Maximum memory12 TB
Maximum logical CPUs768

Due to the ecosystem of different hardware, N-able does not certify specific hardware configurations. Instead we rely on the upstream Red Hat Enterprise Linux and hardware vendor testing and certification.

Examples of servers that have been Red Hat certified include HPE ProLiant DL360 Gen10 and Dell PowerEdge R620.

Please consult with your hardware vendor to ensure that any server to be used for a bare metal installation meets the above requirements, and is Red Hat Enterprise Linux 7.7 certified, without the need for additional

N-able recommends that for any Bare Metal server, two or more SAS 10k or faster hard drives be placed in a RAID array to improve redundancy. RAID 1+0 or RAID 5 are supported (at the hardware RAID BIOS level). RAID 6 is an option on servers with less than 1,000 devices (the additional write latency of RAID 6 becomes an issue above 1,000 devices).

Support for virtualized environments

N-able supports VMware ESX Server 6.0 or newer and Windows Server 2012 R2 Hyper-V or newer LTS versions. N-able recommends use of the latest stable versions of VMware or Hyper-V in order to ensure the best performance, feature set and compatibility with N-able N-central.

View more

Hyper-V on Windows Desktop Operating Systems not Supported.

N-able N-central installed on a virtual machine running on a Desktop Operating System (such as HyperV on Windows 10, Virtual Box, Parallels, VMWare Fusion or similar) is not a supported configuration. If
you are using Windows Hyper-V, it must be installed on a supported server class Windows Operating

Windows Server Semi-Annual Releases are not Supported.

Only Long-Term Support (LTS) versions of the Windows Server Operating System are supported as a
Hyper-V host for N-able N-central. Microsoft currently releases “Semi-Annual Release” versions of
Windows Server as a technology preview for the next LTS version. Due to their technology preview
status, these “Semi-Annual Release” versions of Windows Server are not supported as Hyper-V hosts
for N-able N-central.

About virtualization

Virtualization provides an abstraction layer between the hardware and the Operating System which permits the operation of multiple logical systems on one physical server unit. The table below includes considerations when using this deployment method.

It is impossible to guarantee the scalability or performance of a N-able N-central server deployed on a Virtual Machine due to:
1. Variability in field environments resulting from host server configurations,
2. The number of virtual guests run on the host server, and
3. The performance of the underlying host hardware.
SupportabilityN-able supports N-able N-central software deployed on VMWare ESX/ESXi 6.0 or newer, Windows Server 2012 R2 Hyper-V or newer LTS releases, Microsoft Azure and Amazon AWS EC2 in the same way that we support N-able N-central deployed on Bare Metal. This support is limited to the components (Software and Operating System) shipped with Nable N-central and does not include the troubleshooting of virtualization systems nor of
performance issues related to environmental factors.

N-able recommends reaching out to your hardware or virtualization vendor for support on the underlying virtualization and hardware components. Any assistance provided by Nable Support for virtualization or hardware issues is on a best-effort basis only. In the event of serious performance problems, we might ask you to migrate a virtualized N-able N-central system to a physical hardware deployment.
In Windows Server 2016 Hyper-V or newer deployments, it is recommended to create a new Generation 2 VM. When configuring the VM virtual hardware, if you choose to enable Secure Boot, please select the Microsoft UEFI Certificate Authority template.

For VMWare ESX/ESXi deployments, it is recommended to select the Red Hat Enterprise Linux 7 guest OS template, then under the Boot Options, select the UEFI Firmware.
N-able recommends using the VMXNET3 network card in VMWare. When the VM is configured as Red Hat Enterprise Linux 7, it will use VMXNET3 by default.

Unless you are using Network Interface Bonding, N-able N-central requires only one (1) network adapter added to the VM configuration. Multiple network adapters that are not used in a bonding configuration can cause connectivity and licensing issues.
MAC AddressesBy default, most virtualization environments use a dynamically assigned MAC address for each virtual network card. As your N-able N-central license is generated in part by using the MAC address of its network card, it is required to use a statically assigned MAC address in order to avoid becoming de-licensed.

Recommended configuration for the virtualized server

Although provisioning virtual disks as “thin” or “thick” results in nearly-identical performance, thick
provisioning is recommended, particularly when more than 1,000 devices will be connected to your Nable N-central server.

  • Assign the highest resource access priority to N-able N-central, as compared to other guest VMs.
  • Do not over-provision resources (Memory, CPU, Disk) on the virtualization host. Over-provisioning these resources can causes memory swapping to disk, and other bottlenecks that can impact guest system performance.
  • Ensure that the system has enough RAM and hard drive space to provide permanently allocated resources to the N-able N-central guest.

Supported Software


N-able N-central supports the latest versions of:

  • Microsoft Edge®
  • Mozilla Firefox®
  • Google Chrome®
  • Apple Safari®

    Mobile phone browsers are not supported.
Remote Control

Remote control connections require the following software on the computers that initiate connections:

  • .NET Framework 4.5.2 on Windows devices
  • Oracle Java 1.8 versions that include Java Web Start
Report Manager

To use Report Manager with N-able N-central, ensure the you upgrade to the latest version of Report Manager.

Automation Manager

Automation Manager requires .NET Framework 4.5.2 and PowerShell 3.0 to run AMP-based services with N-able N-central.

SNMP Community String

On HPE ProLiant Generation 9 or older Physical Servers, when monitoring the N-able N-central server using SNMP, the community string used for SNMP queries to the server must use N-central_SNMP, not public. SNMP is only enabled on HPE ProLiant Generation 9 or older Physical Servers. All other installs do not enable SNMP on the N-able N-central server.

Supported Operating Systems

This section describes the supported operating systems for N-able N-central.

Windows Agents
  • Microsoft .NET Framework 4.5.2 (or later)
Windows Server 2022
  • Windows Server 2022 Standard
  • Windows Server 2022 Datacenter
  • Windows Server 2022 Datacenter: Azure
Windows Server 2019
  • Windows Server 2019 Datacenter
  • Windows Server 2019 Standard
Windows Server 2016
  • Windows Server 2016 Datacenter
  • Windows Server 2016 Standard
  • Windows Server 2016 Essentials
  • Windows Storage Server 2016
  • Windows Server 2016 MultiPoint Premium Server
  • Microsoft Hyper-V Server 2016
Windows Server 2012
  • R2 Datacenter
  • R2 Essentials
  • R2 Foundation
  • R2 Standard
  • Datacenter 64-bit Edition
  • Essentials 64-bit Edition
  • Foundation 64-bit Edition
  • Standard 64-bit Edition
  • Microsoft Hyper-V Server 2012
  • Microsoft Hyper-V Server 2012 R2
  • Storage Server 2012 Enterprise 64-bit Edition
  • Storage Server 2012 Express 64-bit Edition
  • Storage Server 2012 Standard 64-bit Edition
  • Storage Server 2012 Workgroup 64-bit Edition
Windows 11
  • Microsoft Windows 11 Enterprise & Professional
  • Microsoft Windows 11 Education editions
  • Microsoft Windows 11 Pro for Workstations
Windows 10
  • Microsoft Windows 10 Enterprise & Professional
  • Microsoft Windows 10 Education editions
  • Windows 10 Pro for Workstations
Windows 8 and 8.1
  • 8.1 Enterprise
  • 8.1 Professional
  • 8 Enterprise
  • 8 Professional
Windows 7
  • Microsoft Windows 7 Enterprise & Professional
  • Microsoft Windows 7 Ultimate
macOS Agents
  • 12.0 (Monterey)
  • 11.0 (Big Sur)
  • 10.15 (Catalina)
  • 10.14 (Mojave)
  • 10.13 (High Sierra)
  • 10.12 (Sierra)
Linux Agents

Independent Agents are required for 32-bit and 64-bit Linux OS installations.

The probe performs an SSH connection a Linux device. To discover a Ubuntu/Debian OS device, the
device must have openssh installed.

  • Red Hat Enterprise Linux/CentOS 8 (64-bit)
  • Red Hat Enterprise Linux/CentOS 7 (x86_64 and i686)
  • Red Hat Enterprise Linux/CentOS 6 (x86_64 and i686)
  • Ubuntu 20.04 LTS (64-bit)
  • Ubuntu 18.04 “Bionic Beaver” (x86_64)
  • Ubuntu 16.04 “Xenial Xerus” (x86_64 and i686)
  • Debian 8.7/Ubuntu 14.04 “Trusty Tahr” (x86_64 and i686)
AV Defender

Workstation Operating Systems

  • Microsoft Windows 11
  • Microsoft Windows 10
  • Microsoft Windows 8, 8.1

Tablet And Embedded Operating Systems

  • Windows 10 IoT Enterprise
  • Windows Embedded 8.1 Industry
  • Windows Embedded 8 Standard
  • Windows Embedded Enterprise 7
  • Windows Embedded POSReady 7
  • Windows Embedded Standard 7
  • Windows Embedded Compact 7

Server Operating Systems

  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2019 Core
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 Core
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012

For Microsoft Windows Embedded Standard 7, TCP/IP, Filter Manager, and Windows Installer must all be

Patch Manager

Workstation Operating Systems

  • Microsoft Windows 11
  • Microsoft Windows 10 version 1607 and later
  • Microsoft Windows 8.1
  • Microsoft Windows 8
  • Microsoft Windows 7

Server Operating Systems

  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

The following operating systems are not supported with N-able N-central patch manager:

  • Microsoft Windows XP
  • Microsoft Windows Vista
  • Microsoft Windows 10 Home Edition
  • Microsoft Windows Server 2003
  • Microsoft Windows Server 2008
  • Microsoft Windows 11 Home Edition (Monitoring status is supported)
Windows Update Agent

The minimum version of the Windows Update Agent (WUA) needs to be greater than 7.6.7600.320. The base NT build version of Windows should be 6.1 or later. Older versions of the base NT build cannot upgrade past version 7.6.7600.256 of the Windows Update Agent.

Automation Manager

Workstation Operating Systems

  • Microsoft Windows 11
  • Microsoft Windows 10 (32/64-bit)
  • Microsoft Windows 8.1 (32/64-bit)
  • Microsoft Windows 8 (32/64-bit)
  • Microsoft Windows 7 (32/64-bit)

Server Operating Systems

  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016 (32/64-bit)
  • Microsoft Windows Server 2012 R2 (32/64-bit)
  • Microsoft Windows Server 2012 (32/64-bit)
Disk Encryption Manager

Hyper-V Server 2012 R2Hyper-V Server 2016
Windows 7 Enterprise Windows 7 Home Premium
Windows 7 Professional Windows 7 Ultimate
Windows 8 Enterprise Windows 8 Pro
Windows 8 Pro with Media Center Windows 8.1 Enterprise
Windows 8.1 Pro Windows 8.1 Pro with Media Center
Windows 10 Education Windows 10 Enterprise
Windows 10 Enterprise 2015 LTSB Windows 10 Enterprise 2016 LTSB
Windows 10 Enterprise for Virtual Desktops Windows 10 Enterprise LTSC 2019
Windows 10 Pro Windows 10 Pro Education
Windows 10 Pro for Workstations
Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Standard Windows Server 2008 R2 Foundation
Windows Server 2012 Datacenter Windows Server 2012 Essentials
Windows Server 2012 Foundation Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation
Windows Server 2012 R2 Standard Windows Server 2012 R2 Standard Evaluation
Windows Server 2012 Standard
Windows Server 2016 Datacenter Windows Server 2016 Datacenter Evaluation
Windows Server 2016 Essentials Windows Server 2016 Standard
Windows Server 2016 Standard Evaluation
Windows Server 2019 Datacenter Windows Server 2019 Essentials
Windows Server 2019 Standard Windows Server 2019 Standard Evaluation
Windows Server Datacenter
Windows Small Business Server 2011
Windows Small Business Server 2011 Standard

Port access requirement

N-central Server

Access must be permitted to the following ports:

Supported operating systems for remote control

The availability of remote control connections will vary depending on the operating systems of both the client and target devices. The table below outlines the operating systems and their compatibility with various remote control types.

Licensing and Customer Support

Agent/Probe Installation Software

N-able N-central 2023.7 uses the 7-Zip file archiver for installing agents and probes. 7-Zip is free software redistributed under the terms of the GNU Lesser General Public License as published by the Free Software Foundation. For more information, see

Customer Support

Contact N-able to activate your N-able N-central server.

Web Page:
Technical Support SelfService Portal:
Phone:Toll Free (U.S./CAN): 1-866-302-4689

International: +800-6225-3000

Local: (613) 592-6676, select option 2 for support

Download release notes

For a PDF version of the latest release notes, or to view historical release notes, please use the following link:

This entry was posted in N-central. Bookmark the permalink.