Announcing the GA of N-central 2022.7 HF1

N-central 2022.7.1.44

2022.7 HF1 Release Notes (PDF)

Download Now

Please be aware that the known issue KUIP-4432 still exists in N-central 2022.7 HF1. If you had the code drop applied for this already or use EDR integrated with N-central, please contact Support before upgrading to this release.

See the 2022.7 Release Notes for requirements and support details.

IMPORTANT – Security Improvements

N-central 2022.7 HF1 provides a major security enhancement which requires additional attention to your N-central network and client environments. Now, the N-central server will require a valid SSL/TLS certificate to be applied. This will include any certificate where the whole chain is validated to a root CA within the system trust store. To support these changes, there are updates to a few screens in the UI, such as the Network Setup page, as well as the Generate and Download certificate page. We also have modified the upgrade process so that if you don’t have a valid certificate in place before attempting this upgrade, you will receive an error message before any database changes are made. As a result, you can try the upgrade again without needing Support to remove a flag.

Agent and probe behavior is also part of the security enhancement in N-central 2022.7 HF1. Agents and probes will not attempt to upgrade to 2022.7 HF1 and beyond unless the operating system of that device recognizes N-central’s certificate as valid. We are also adding the FQDN from the Network Setup page to the top of the Server Address list on the Communication Settings page. This list is still fully editable for individual devices and in the defaults if you desire to make changes afterward.

For new installations of N-central 2022.7 HF1, you will need to provide the FQDN for this N-central server on the initial login wizard page.

Before upgrading to 2022.7 HF1, we strongly recommend reviewing the following KB article to help prepare you for this upgrade. Checklist for upgrading your N-able N-central Server to 2022.7 HF1.

What’s new in N-central 2022.7

N-central 2022.7 is jam-packed with both fixes and new features! Please see below for more information on our new features, and the fixed items list for a list of bug fixes!

Device Management for Apple

N-central 2022.7 is the first to include N-able’s Device Management for Apple solution.

This is a new service to N-central is for Mac workstations only.  The existing N-central MDM for iPhones and iPads is similar technology but a different back-end.  The two services will co-exist for some time.

Here’s what Device Management for Apple includes in the 2022.7 release:

User-approved manual enrollment: To bring Mac workstations under management properly, Apple requires that enrollment into Device Management be approved by the user of the device.  This cannot be scripted.

Enrollment Helper: to assist with manual enrollment, N-central provides an app that presents your brand – or a friendly name of your choosing – to users and asks them to initiate the process of installing the Enrollment Profile.  This can be enabled/disabled across your entire fleet, or on a client by client basis, or one device at a time.

Multi-tenant push certificates: To get started with Device Management, N-central admins must send a CSR from N-central to the Apple Push Certificate portal to get a push cert.  N-central includes support for creating a push cert for only specific customers, or globally for all devices.  Enrollment Helper can be enabled/disabled with each cert.  (Note: this is the same technology as the existing APNS cert in N-central’s MDM for iPads and iPhones – but it is being setup with a different back-end service.)

PPPC profiles for N-able products: once a Mac is enrolled in Device Management, our service automatically pushes Configuration Profiles that grant macOS Security & Privacy permissions for the N-central Mac Agent, Take Control, EDR, Backup and more.  (The only one we can’t push is Screen Recording for Take Control because Apple doesn’t allow that permission to be controlled by any MDM, not just ours.)  This further streamlines the installation process for new Macs because you don’t need to jump through all the hoops to grant Full Disk Access, Notifications, etc.

Custom Configuration Profiles: Once you have a push cert setup, and devices enrolled, you can upload thousands of configuration profiles – many samples are available in the N-able Automation Cookbook – and push those over the air to your Mac workstations.  The configuration possibilities are virtually limitless.

As powerful as this is, it is a first release.  Device Management for Apple has capacity for support for MDM Commands (like lock and wipe), support for iPads, iPhones, AppleTVs in addition to Macs, and support for Apple Business Manager and Apple School Manager automatic zero-touch enrollment.  Future builds will round out a complete Device Management service for Apple devices.  Those features are on their way to N-central in future releases.

In addition to Device Management, work continues on surfacing the benefits of our new Mac Agent.  N-central 2022.7 includes a real-time Processes widget in the Overview tab of Mac workstations.  And for the first time ever, Mac workstations get a Tools tab – it’s currently only populated with the same Processes table, but will be built out in future N-central releases.

Automation Manager 2.50

Automation Manager 2.50 is now available and included in N-central 2022.7. This version of Automation Manager focuses on bugfixes, including fixes that should help with certain errors in AMP-Based monitoring services in N-central once your agents have upgraded.

In the Designer, we’ve clarified the help articles to indicate SSHv2 is supported for Network Management objects, and we’ve adjusted the branding to match N-central’s default branding. Prompts from Automation Manager will now always be in the foreground, and appear in the center of the screen.

Upgrade paths and notes

After the upgrade to N-central version 2022.7, an additional restart of the Windows Agent Service, Windows Agent Maintenance Service, and Windows Software Probe Service (Manually or Scheduled Task) or a full device reboot (not hibernate or sleep) may be required on Windows devices with misconfigured AMP based services in order for them to go back to Normal state.

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

View versions:
  • N-able N-central 2021.1.0.32
  • N-able N-central 2021.2.0.140+
  • N-able N-central 2021.3.0.79+
  • N-able N-central 2022.1.0.47+
  • N-able N-central 2022.2.0.77+
  • N-able N-central 2022.3.0.46+
  • N-able N-central 2022.4.0.6+
  • N-able N-central 2022.5.0.6+
  • N-able N-central 2022.5.1.33
  • N-able N-central 2022.5.2.35
  • N-able N-central 2022.6.0.20+
  • N-able N-central 2022.7.0.22+

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

Scheduled 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 restart of the device is pending.


If you are a Partner running N-central in Azure, review the following article to avoid any potential issues with the upgrade to this release. We have identified an issue that impacts our Azure hosted N-central partners. Fortunately, our team has steps to resolve the issue. Before upgrading your N-central server to any supported version, review the following article: How to Identify a Legacy Azure N-central Instance.

Fixed Issues in N-able N-central

Release 2022.7 HF1
Automation ManagerAutomation Manager Validate TLS CertificatesAM-3330
CoreNaupdater downloaded to wrong location during upgrade, causing upgrade failureNCCF-101688
CoreUbuntu 16/18 Agent incorrectly reporting endpoint as part of SubmitCurrentlyLoggedInUserNCCF-97372
CoreCannot find softwareType to upgrade applianceType [Agent] with osid [ubuntu20_64] when attempting to upgrade agentNCCF-96011
CoreUpdate N-central to Add Certificate VerificationNCCF-77020
CoreProbe MSI upgrade no longer functional due to lack of credentialsNCCF-15093
Release 2022.7
Automation ManagerAM Object: “Backup Registry”Input Parameters mistake in descriptionAM-2316
Automation ManagerPolicyExecutionEngine logging to agent.log instead of PolicyExecutionEngine.logAM-2669
Automation ManagerInput Prompt object doesn’t allow to link inputAM-2677
Automation ManagerInstall Software from FTP doesn’t allow SFTP connectionsAM-2730
Automation ManagerAdd FluentFTP assembly to NC Win Agent and Probe installersAM-2745
Automation ManagerPre-Fill The AMP Name When Closing Automation ManagerAM-2749
Automation ManagerGet Events object not returning results for operational logs (e.g Setup)AM-2808
Automation ManagerScript check failing with error “Exception encountered System.Runtime.Serialization.SerializationException” then automatically resolves itself next check-inAM-2809
Automation ManagerMake AM able to work when FIPS mode is enabledAM-2822
Automation ManagerAutomationManager.log displays N-central agent version as 0.0AM-2826
Automation ManagerRedesign the “Policy List” WindowAM-2830
Automation ManagerUpdate The Colors In the Automation Manager DesignerAM-2832
Automation ManagerCreate AD user module in Automation ManagerAM-2833
Automation ManagerMap network printerAM-2836
Automation ManagerGet OS Architecture AMP abnormal resultsAM-2840
Automation ManagerSet different AM log level from NC dashboardAM-2843
Automation ManagerUpdate the “Close Connection” Object To Support SSHv2AM-2846
Automation ManagerUpdate the “Command Set” Object To Support SSHv2AM-2847
Automation ManagerUpdate the “Enable (Cisco)” Object To Support SSHv2AM-2848
Automation ManagerUpdate the “Get Connection Details” Object To Support SSHv2AM-2849
Automation ManagerUpdate the “Open Session” Object To Support SSHv2AM-2850
Automation ManagerUpdate the “Send Commands and Receive Response” Object To Support SSHv2AM-2851
Automation ManagerUpdate the “Set Terminal Length” Object To Support SSHv2AM-2852
Automation ManagerLarge Number of Probe Log Files AutomationManager.ScriptRunner64-p[XXXX].logAM-2853
Automation ManagerM365 automations Failed execution on remote deviceAM-2855
Automation ManagerAM object – Get Environment Variable shows error message but it returns correct infoAM-2858
Automation ManagerAM Run PowerShell Script object throws “Exception: Requested registry access is not allowed”AM-2859
Automation ManagerImprove AM PolicyExecutionEngine-p[%processid].logAM-2880
Automation ManagerAM prompts open at the top left of the screenAM-2883
Automation ManagerAutomation Manager Agent Service crash when scheduled task run as logged on userAM-2890
Automation ManagerFix AM initialization after Shutdown RPC callAM-2898
Automation ManagerReboot Prompt Not working when Branding is usedAM-2912
Automation ManagerPrompt improvements: Add check for prompt to always be on foregroundAM-2914
Automation ManagerScript Check failing with Unknown Error (Exception encountered System.InvalidOperationException: There is an error in XML document (0, 0)….)AM-2915
Automation ManagerIncorrect status for UAC serviceAM-2917
Automation ManagerAM RPC server issue: No protocol sequences have been registeredAM-2923
Automation ManagerAutomation Manager Object: Reboot Prompt, Exceeded delay time but did not initiate rebootAM-2927
Automation ManagerIntroduce RPC server’s fallback address functionalityAM-2960
Automation ManagerLog cleanup: delete empty log files when log level is ERROR or FATALAM-2965
Automation ManagerAM assemblies to 2.50 on NC 2022.7AM-2969
Automation ManagerFix ConfigurationSettings.xml file for thirdparty dll nameAM-2970
Integrated AVSoft-deleted records are not hard-deleted for a long timeIAV-1052
IntegrationsThe user having ‘Read Only’ or ‘None’ permissions over DNS Filtering Integration can still deploy or remove the Roaming Client or select a profile in the deployment processINT-1005
IntegrationsEmpty profile name allowedINT-657
IntegrationsThe DNS Filtering Status remains reported as an active issue in N-central even after RC’s uninstallation (validated after 7 days of RC uninstallation from the client’s machine)INT-849
IntegrationsDNS Filter Trial ExperienceINT-854
IntegrationsNewly created profiles under NC System levels (SO / Customer / Site) cannot be edited (Content Filters / Block Pages selections)INT-864
IntegrationsAdd the DNSF service into Monitoring tab when the device is in Essential ModeINT-941
Ecosystem FrameworkMS Intune integration icon shows enabled even when not being used – Dev WorkKUIP-2898
Ecosystem FrameworkSentinel One agent is not being uninstalled when a Device with EDR enabled is being removed from N-CentralKUIP-2985
CoreThe agent version is displayed instead of the server versionCALM-1419 references a option that does not existNCCF-14033
Core[FEATURE] Device Management for AppleNCCF-14253
CoreSystem Error When The System Is Out Of Licenses, And A Licensed Feature Is Added To The DeviceNCCF-14388
CoreDeprecate Support For Unsupported Versions of Linux and 32-bit Linux InstallersNCCF-14459
CoreThe UserAdd API Returns a “-1” When Password That Doesn’t Meet The Complexity Requirements Is Specified, Instead Of An Actionable Error MessageNCCF-14470
CoreDomain User Management Re-Did A Global Password Reset For A CustomerNCCF-15022
CoreLarge amount of temp file in AM temp location cause agent startup delayNCCF-15125
CoreDeleting a probe does not delete record from device’s “discovering_wsp”NCCF-15560
CoreShow caps lock on for login password, instead of sending password in reverse case.NCCF-15595
CoreLocking the “MFA Not Required” Option Isn’t Being SavedNCCF-15617
CoreDropdown Custom Property will remain on error state after two empty valuesNCCF-16055
CoreThe Linux/Mac code sometimes returns 32-bit for 64-bit OSsNCCF-16219
CoreIncorrect repository capacity is being displayedNCCF-16323
CoreUser cannot create reinstall agent task because probe not assignedNCCF-16666
CoreProbe HTTPS service: 1. Change X509ChainPolicy.RevocationFlag 2. Change validation logic ignoring error when global error ChainStatus is used for certificate validationNCCF-17007
CoreCustom Service (SNMP): change Service Identifier and/or Identifier options saves unexpected configuration.NCCF-17038
CoreCustom Service (SNMP): System ErrorNCCF-17040
CoreSettings not retained for Connectivity Service Details when SNMP enabledNCCF-21344
CoreImprove logging for all Google actions if missingNCCF-21483
CoreGoogle IdP Provider: remove the client-id from the error text displayed when NC is accessed by IPNCCF-22664
CoreStop Building the Unsupported Agent InstallersNCCF-22822
CoreRemove unsupported Installers From N-centralNCCF-22823
CoreEnsure Existing Deprecated Agent Installers cannot be used to register and activate new appliancesNCCF-22825
CoreSetting Up More than Two Services in a Template, The Service identifier is Not Transferred CorrectlyNCCF-24478
CoreCreate sysaudit script to collect non-IdP user metricsNCCF-24846
CoreSSO Providers Google G-Suite – Robot Framework Test Suite Integration: N-centralNCCF-24907
CoreN-Central DMfA Navigation UXNCCF-26127
CoreAllow sorting by SSO ColumnNCCF-27272
Core64 bit processes not showing DLLs usedNCCF-28092
CoreDefault Filter Created on Site Creation Causes System ErrorsNCCF-28386
CoreN-central – Send list of clients to Device Management for Apple (DMfA) UI in iframeNCCF-29749
CoreUpdate Permission Definitions and UI for DMfANCCF-29750
CoreCreate Release request for N-central DMfA for 22.7NCCF-29751
CoreSend permission to DMfA for jwtNCCF-29997
CoreRF5 Fails on evaluation of python os.gettempdirNCCF-30087
CoreAdd missed statistics for event acknowledgement timeNCCF-30801
CoreN-central – Inconsistent ApplicationDeviceId when requesting an DMfA profileNCCF-30926
CorePending events are not cleared out from queue when system gets into a throttle blocking state and eventing is turned offNCCF-30977
CoreFix ROLES page when appledevicemanagement Flag is offNCCF-31011
CoreScraping: Records are being dropped due to mandatory date fields that cannot be parsedNCCF-31201
CoreThe assigned Variable in is causing disruption to the URLNCCF-31456
CoreDatabase scraping has an issue where concurrent table processing happens and events overlapNCCF-31458
CoreLogging | Include protobuf event typeNCCF-31573
CoreXMPP related issuesNCCF-32110
CoreUI | Eventproduction | Only sys adminNCCF-32195
CoreUI | Analytics Splash Message RemovalNCCF-32474
CoreSessionUtils.refreshExpiryForAppliance Triggering Against Eventing When It Does Not Need ToNCCF-32749
CoreIR Stable Main – Devices – Verify System Warranty Service is Added – FailsNCCF-32957
CoreIR Stable Main: Devices – Verify Log File Is Not Accessible For User With Low Level Access – FailsNCCF-32958
CoreElementClickInterceptedException caused by ‘Device Permissions’ Dialog warning “You do not have permission to configure devices. Please contact your administrator.”NCCF-32980
CoreGoogle SSO Provider – Create Google SSO Provider page is brokenNCCF-33150
CoreEvent controller should reset pending counts on restartNCCF-33243
CoreAcknowledgement controller should reset pending counts on restartNCCF-33244
CoreCatastrophic failure of event buffer termination should resetbuffer state and turn off eventing.NCCF-33245
CoreBatch sender not started errorNCCF-33483
CoreAdvancedReportingUser is getting dropped due to missing role or customer groupNCCF-33484
CoreLive eventing should not stop when backups occurNCCF-33536
CoreRecords are being removed from bufferingEnabledTables variable and causing events to be permanently droppedNCCF-33765
CoreEventBufferController Can Cause High Garbage CollectionNCCF-33812
CoreUpgrade certificates with proper clientId for NCOD to support DMfANCCF-33990
CoreLeft-hand menu for “Analytics” needs to show we are Beta.NCCF-35263
CoreMemory consumption is too high when buffering eventsNCCF-35840
CoreEnsure time series tables are not processed for scraping unless within 24hNCCF-35851
CoreInterrupt exception can cause event processing and/or acknowledgement processing to stop permanently and needs a watchdogNCCF-36410
CoreNULL pointer error while saving Device settingsNCCF-37224
CoreAgent download labels incorrectNCCF-38026
Core Agent installation failsNCCF-38236
CoreParent level view – Permission evaluation is not performed for lower levelsNCCF-39485
CoreScriptDownloadURI’ Version Not Updating After Upgrading of N-centralNCCF-40053
Patch Management CMInclude re-branded PME in the latest N-centralPMCM-715

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.

Active Issues

When exporting a large list of Active Issues items to PDF format at either the System or Service Organization level, the server may fail. Exporting to CSV format does not cause this problem.62860
Agents and Probes

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
AV Defender and Backup Manager – D2D

The About Backup Manager dialog box no longer indicates if the Backup Manager software is licensed.68226
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
Warranty information might be inaccurate when determining the warranty expiry dates of devices that are not located in the USA.NCCF-3649
URL with embedded username and password prompts for Java upgrade, logging in manually does not prompt.NCCF-2415
Chrome 42.x does not support NPAPI plugins which means that Java and Direct Connect will not function with that browser version. When attempting to open remote control connections in Chrome 42.x, users will be repeatedly prompted to install either Java or the NTRglobal plugin with no successful connections made. To resolve this issue, perform the following:

1. In the Chrome address bar, type chrome://flags/.
2. Under Enable NPAPI, click Enable.
3. Restart Chrome.
NCCF- 73359

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
The main N-central login page will fail to load when accessed from the Safari web browser. To work around this issue, please use a supported browser, such as Chrome, Edge or Firefox, or access N-central via https:///login.NCCF-19768
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.

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.