2025.2 Release Notes Preview
Build Number: 2025.2.0.10 Last updated: 24/03/2025
Important Notice for OnPrem partners upgrading to 2025.2 from a version that is not 2025.1.
N-central 2025.1 replaced the underlying operating system on N-central from CentOS to AlmaLinux.
If you are upgrading from a version of N-central that is not 2025.1 you will be doing a complete operating system migration. This is a significant upgrade to N-central with new system requirements and the upgrade will take longer than a normal upgrade.
We highly recommend reviewing the updated system requirements and release notes for essential details before proceeding with the upgrade.
We’re introducing exciting new features, enhancements, and critical fixes to improve usability, security, and performance. Here’s a preview of what’s expected in the 2025.2 release.
N-able SSO Login for Mobile App
We’ve enhanced N-central Mobile App login by introducing N-able Login (MSP SSO) support, including Multi-Factor Authentication (MFA) and third-party Identity Providers (IDPs).
What’s New?
-
Support for N-able Login (SSO): Users can now authenticate using MSP SSO, including MFA and third-party IDPs.
-
Seamless Authentication Experience: The app now differentiates between local login and SSO login for a streamlined login process.
How It Works
If Local Login:
-
The app prompts for a password and MFA, then grants access to the product.
If SSO Login:
-
Base N-able Login: The user is forwarded to the N-able Login flow, where they enter their username, password, and MFA (if applicable).
-
N-able Login with a Third-Party IDP: The user is redirected to the third-party provider, follows the external authentication process, and is granted access.
To take advantage of N-able SSO, users must update their installed version of the N-central Mobile App to the latest version that supports this functionality.
See also
N-able Login (with or without Microsoft Entra ID)
User Audit Log Export-Additional Audit Events
In previous releases, we introduced the ability to export user audit records to a Syslog server capturing specific user-initiated auditing events. Building on this foundation, we are now broadening the scope of our auditing capabilities by adding more events to be recorded and exported to provide greater visibility into user actions and security-related events.
-
User Access Group: Creation, cloning, merging, modification, and deletion of groups by customers and devices.
-
Service Template: Creation, modification, and deletion of service templates.
-
Filter: Creation, cloning, importing, modification, and deletion of filters.
-
User Role: Assignment and unassignment of user roles.
To configure Syslog export and take full advantage of these features, see: Configure Syslog Export.
N-central Agent Expanded Linux OS Compatibility
-
The latest update of the N-Central Linux Agent now offers enhanced support for modern Linux environments, ensuring streamlined installation and robust performance across a broad range of distributions.
-
Added support for Linux distributions:
-
AlmaLinux 9
-
CentOS 9
-
RHEL 9
-
Debian 12
-
Ubuntu 24
-
CVSS Auto-Approval for Patches
-
The Approve Patch Rule screen now includes an option to define a CVSS (Common Vulnerability Scoring System) score range for automatic patch approvals.
-
Users can specify a threshold (e.g., 7.0 to 10.0) to ensure patches addressing high-severity vulnerabilities are approved without manual intervention. This enhancement helps streamline the patching process while allowing organizations to align approvals with their security policies and risk tolerance.
Asset Details View
-
Additional "Managed" Column in Asset Views to make it easier for users to track and manage active devices:
-
This column will indicate whether a device is Managed or Unmanaged within the Asset View.
-
When a device is deleted and marked as unmanaged in N-central, the Managed column in Asset View will update to "Unmanaged", and users can filter to hide or show unmanaged devices.
-
If a previously unmanaged device is re-added, its Managed status will change back to "Managed".
-
Users will have the ability to filter out or display "Unmanaged" devices.
-
See also
Assets View documentation Assets View - On-Premises
Getting Started Webinar-Recording
Analytics Data Veracity, Consistency & Performance Enhancements
-
This release introduces major improvements to data reconciliation, monitoring, and performance to ensure greater data accuracy between N-central and Analytics. Also, we have optimized event production processes for better system performance & real-time data accuracy.
Duplicate Device Names Filtering
This feature enhances device management in N-central by introducing a new filtering option for duplicate device names and improving visibility into suspected duplicates.
-
New "Duplicate Names" Filter: Users can now filter out devices with duplicate names for improved data accuracy and streamlined management.
-
Device Details View Update: Suspected duplicates are now clearly indicated when a device name matches another in the System Information widget of the Overview tab
Expanded Export PDF & CSV
-
You can now Export the Discovered device list in PDF & CSV formats from Import Discovered Assets view
-
Following columns are now added in PDF & CSV exports on All Devices view for detailed device information and improved reporting:
-
Device Serial Number
-
Make
-
Model
-
New “Modify” Capability for Patch Maintenance Windows REST API
In version 24.6, we introduced a REST API for Patch Maintenance Windows with Create, Delete, and Retrieve capabilities. With version 25.2, we are enhancing this API by adding the ability to Modify existing maintenance windows.
Upgrade Paths and Notes
To upgrade to N-able N-central 2025.2, your N-able N-central server must be running one of the listed versions.
The following upgrades (non-migrations from Alma to Alma) are permitted:
-
2025.1.0.0 (N-central 2025.1)
-
2025.1.1.0 (N-central 2025.1 Hotfix 1)
-
2025.2.0.0 (N-central 2025.2)
The following migrations (from CentOS to Alma) are permitted:
-
2023.9.0.0 (N-central 2023.9)
-
2023.9.1.0 (N-central 2023.9 Hotfix 1)
-
2024.1.0.0 (N-central 2024.1)
-
2024.2.0.0 (N-central 2024.2)
-
2024.3.0.0 (N-central 2024.3)
-
2024.4.0.0 (N-central 2024.4)
-
2024.6.0.0 (N-central 2024.6)
-
2024.6.1.0 (N-central 2024.6 Hotfix 1)
N-central 2025.1 replaced the underlying operating system on N-central from CentOS 7 with AlmaLinux 9.4.
CentOS to Alma is a complete operating system migration, including system setting changes. It is important to thoroughly review the release notes and follow the below recommendations:
-
Carefully review the system requirements and ensure your system meets these requirements before attempting the migration.
-
Review the Known Issues section.
-
This migration will take longer than normal, and we recommend reviewing these articles to create the best upgrade plan that suits your needs:
-
While we recommend having a recovery plan for all upgrade attempts, due to the size and nature of this upgrade there is increased risk of the upgrade to go wrong. We recommend reviewing the below articles to ensure you have a backup and have a recovery plan prepared:
Bug Fixes
N-central 2025.2 (Build: TBD)
Category | Updated Summary | Issue Key |
---|---|---|
Core | Fixed an issue
where invalid cloud-based requests could prevent DMS from initializing
Issue: DMS wouldn’t start because of incorrect cloud requests, especially when a partner’s ID changed. Fix: Added checks to handle authorization errors properly and allow DMS to start. |
NCCF-508449 |
Core | Improved device
cache performance to resolve slowdown issues
Issue: System performance was slow because of too much load on device cache processing. Fix: Optimized the way data is stored and accessed to improve speed. |
NCCF-487485 |
Core | Fixed incorrect
query behavior causing unnecessary database searches
Issue: Some database searches were returning too many results, slowing things down. Fix: Adjusted query rules to return only relevant results |
NCCF-469705 |
Core | Updated syslog
settings to ensure correct log filtering
Issue: Some system logs weren’t being captured due to an incorrect configuration. Fix: Changed the log filtering method to ensure all necessary logs are collected. |
NCCF-456137 |
Core |
Fixed issue where device names were not reported when executing remote discovery scripts
Issue: Remote discovery scripts were executing but failing to report device names, leading to missing asset data. Fix: Modified the discovery script to ensure device names are captured and reported correctly. |
NCCF-418476 |
Core | Prevented
duplicate device records in Enhanced EDR integration
Issue: Duplicate device records were appearing due to missing validation. Fix: Added a rule to prevent the same device from being added twice. |
NCCF-418089 |
Core | Stopped PSA
export profiles from being accidentally deleted
Issue: Deleting a customer sometimes removed their PSA export profiles. Fix: Adjusted the system to keep export profiles unless specifically removed. |
NCCF-416878 |
Core | Fixed incorrect
formatting in correlated notifications
Issue: Some notifications were incorrectly formatted, making them hard to read. Fix: Ensured notifications are properly formatted for better readability. |
NCCF-347891 |
Core |
Fixed intermittent errors in N-able Backup Product Status reporting
Issue: The backup product status sometimes showed as “Unknown,” even when working. Fix: Improved how status updates are handled to ensure accuracy. |
NCCF-346473 |
Core | Ensured
notifications reach the right PSA ticket recipients
Issue: Some PSA notifications were not going to the correct recipient. Fix: Fixed the way task IDs are mapped so notifications go to the right place. |
NCCF-340770 |
Core |
Fixed issue where "Update Asset Info When Finished" wasn’t saved
Issue: The "Update Asset Info" setting wasn’t being stored properly, preventing updates. Fix: Ensured this setting is correctly passed so assets update as expected. |
NCCF-339624 |
Core | Optimized probe
performance to prevent overload
Issue: Too many tasks were running at once, slowing down the system. Fix: Adjusted task execution to balance workload and improve system stability. |
NCCF-320929 |
Core | Resolved failures
occurring during EDR upgrades after updating to N-central 2024.3
Issue: Some upgrades to EDR failed due to missing settings or dependencies. Fix: Fixed the upgrade process to ensure smooth updates. |
NCCF-297292 |
Core | Fixed missing PSA
customer mapping records until refresh
Issue: Customer mapping records didn’t appear in PSA until manually refreshed. Fix: Adjusted caching so records show up immediately. |
NCCF-215993 |
Core | Stopped Enhanced
EDR data from being accidentally deleted
Issue: If no updates were received, old LWT data was sometimes deleted incorrectly. Fix: Ensured data is kept even when no new updates come in. |
NCCF-204222 |
Core |
Fixed Unexpected EDR Redeployment Issue
Issue: EDR was redeploying unexpectedly by ensuring the LWT execution status updates correctly after uninstalling. Fix: EDR-enabled devices followed the proper installation sequence, while disabled EDR devices correctly updated their status to "Not Installed" after uninstallation. |
NCCF-291534 |
Core | Removed
unnecessary pop-up for Analytics asset inheritance
Issue: Users were getting an unnecessary pop-up when deleting accounts, even when no analytics assets were tied to them. Fix: Removed the pop-up to simplify user management. |
NCCF-175481 |
Core | Fixed error when
deleting modified AMP tasks
Issue: Some scheduled task deletions failed because directories weren’t empty. Fix: Updated the cleanup process to handle non-empty directories correctly. |
NCCF-124635 |
Core | Fixed device name
displays issues due to hidden characters
Issue: Some Mac and Linux devices added hidden characters to names, breaking UI display. Fix: Improved input processing to remove unwanted characters. |
NCCF-37336 |
Core | Fixed agent
installer crashes when checking for duplicate asset tags
Issue: The agent installer crashed if it tried to check for a duplicate asset tag after a failed registration. Fix: Improved error handling to prevent crashes |
NCCF-13307 |
Core |
Fixed Missing M365 Backup Devices in Integrated Cove Backup at SO Level
Issue: Integrated Cove Backup did not display all M365 backup devices at the SO level for end-customers/sites with only M365 devices. Fix: Optimized how M365 devices are displayed, ensuring better coverage for partners with over 400 customers. |
NCCF-478741 |
Managed Services for Apple Devices | Ensured failed
agent install commands retry properly
Issue: If an agent install command failed once, it wouldn’t retry. Fix: Set the system to keep retrying until the installation succeeds. |
MSAD-3254 |
Core | Intermittent Login Errors in N-central via MSP SSO
Issue: Users occasionally experience login failures when accessing N-central through MSP SSO. The two commonly observed issues encountered were "Cannot Sign in MSP SSO User" errors or unexpected "Permission Requested" prompts due to session state handling Fix: Improved token management by renewing it automatically and session persistence to prevent unintended session loss. |
NCCF-508372 |
Patch Management | Fixed agent upgrade resetting Windows Update Registry Keys on devices without Patch Management
Issue: On some devices not using N-able Patch Management an agent upgrade would reset Windows Update Registry Keys Fix: Ensured devices that do not have Patch Management enabled do not have their registry keys reset. |
PMCM-9658 |
Autotask PSA | Fixed: Autotask PSA Integration – Ticket Association Issue in 2025.1.0.57
Issue: Partners using the Autotask PSA integration were previously advised not to upgrade to 2025.1.0.57 due to an issue that caused the removal of the ticket association between Autotask and N-central. This issue prevented tickets from automatically closing when issues were resolved or reopening from N-central. Fix: Partners can safely proceed with the upgrade without affecting Autotask ticket associations. Automatic ticket closure and reopening functionality have been restored. |
NCCF-535280 |
Known Issues
Upgrading from 24.6 and below
When upgrading from a version below 2024.6.0.19 you will need to upload the NSP (N-able Software Platform) upgrade file through the NAC (Network Administration Console) web console, typically accessed at https://<server_address>/admin on port 10000.
Please note, the NAC web console does not support multi-factor authentication (2FA) or single sign-on (SSO) accounts. To access the NAC web console, use the Product Admin account, which has 2FA disabled by default.
The following items are for the current version of the N-able N-central software. They include material issues that significantly impact 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.
Remote Control
Description | Issue |
---|---|
Web SSH, SSH, Custom remote-control options for windows will not dynamically request an updated path when the saved path is not correct and instead provide a terminal error message requesting the user update the remote control settings path | NCCF-506138 |
Web SSH, SSH, Custom remote-control options will not work when launched from a MAC or Linux client | NCCF-414079 |
While calculating the size of the required disk space we look at the size of the last backup on the system, the last system backup on the system must have the "Include Historical Data" option selected in order for the upgrade calculation to be accurate when assessing enough disk space is available. Alternatively downloading then deleting all backups from the system to ensure the backup partition has enough space is an option. Review N-able N-central Backup for details. | - |
You may run into an error "Not enough space on the root (/) volume for the N- central OS upgrade. We need 'X' GB but there is only 'Y' GB free. Not enough space on the root (/) volume for the N-central OS upgrade. We need 'X' GB but there is only 'Y' GB free". See Not enough space in the root (/) volume for the N-central OS upgrade for details. | - |