Up Next: What to Expect in the
2025.3 Release
Last updated: 05/23/2025 Expected Release date: Middle of July
This is an early preview of the release notes; the features and details may change as we move closer to the final release.
Expect further updates in upcoming release notes. The final release notes, including the build number and upgrade details, will be shared as part of the actual release notes that will be published around July.
We’re introducing exciting new features, enhancements, and critical fixes to improve usability, security, and performance. Here’s what’s in the 2025.3 release:
What's New in 2025.3
Applying Asset Tags in Asset View
Easily categorize and organize devices with greater precision using the new Asset Tag capabilities in N-central. This enhancement brings more flexibility and control to how partners manage and track devices across distributed environments.
-
Apply custom tags to devices across all levels: Partner, SO, Customer, and Site.
-
Assign tags directly from the Asset View to enable consistent device labeling to support filtering, reporting, and workflow automation.
-
Manage Tags-Create, edit, and delete tags via the new Tag Management screen (admin-only access).
-
Tag visibility and usage are controlled through a combination of feature flags, user role permissions, and organizational hierarchy.
See also
Script Repository (Preview)
A modern, centralized scripting experience for cross-platform environments is now available in preview for selected partners. This new experience sets the foundation for powerful and scalable automation workflows in future N-central versions.
-
Introducing the new Script Repository for seamless script management across Windows, Mac, and Linux.
-
Users can create, edit, delete, clone, and organize scripts in a dedicated and intuitive UI.
-
Built-in code editor, file upload support, and advanced search & filtering tools enhance usability.
-
Operates independently from the legacy scripting feature, offering a fresh, streamlined experience.
Preview access only via feature flag, progressively rolled out to interested partners and feedback from preview participants will guide improvements ahead of the full release
User Audit Log Export – Additional Audit Events
In past releases 24.6 and 25.2, we introduced the ability to export user audit logs to a Syslog server, capturing key user-initiated events. This functionality continues to expand and i this release, we’ve added auditing for the following new actions:
-
Creation of Discovery Jobs
-
Editing of Discovery Jobs To configure Syslog export and take full advantage of these features, see: Configure Syslog Export
Session Enforcement Improvements
Invalidate Sessions When Linking to new SSO IDP provider
When a user is linked to a new IDP provider (e.g., Microsoft Azure), their current session is automatically invalidated and is redirected to login again using your new or updated credentials.
Session Invalidation After SSO Provider Removal
If an SSO provider is removed (manually or via backend constraint), all sessions for linked users are invalidated and are redirected to login.
This ONLY applies to Azure and Generic SSO configurations as N-able SSO cannot be unlinked.
Agent UI Improvements
Device Import – Warning Message on Import for Devices Failing Discovery Pre-Checks
A new warning message has been added to the device import workflow to alert users when devices selected for import have discovery pre-check issues related to core services such as WMI, SNMP, NetBIOS, SSH, Registry Query, or Admin Share. The users will see the following warning message:
You have at least one device without access to some services. This may result in device inaccessibility and/or mapping issues. Are you sure you want to continue? For more detail, check the help article.
New UI for Identifying and Excluding Duplicate MAC Addresses in Discovery Defaults
A new capability has been added to the Discovery Defaults page to help partners identify and manage devices with duplicate MAC addresses by allowing administrators to exclude such devices from the asset import process and preventing false positives due to hardware with shared or reused MAC addresses.
-
A dynamically generated table highlights MAC addresses assigned to multiple distinct devices with the following columns:
-
Selection Checkbox
-
Customer / Site Name
-
MAC Address
-
Device Count
-
-
Users can select one or more entries and click the new "Exclude" button to move those excluded MAC addresses to the existing "MAC Addresses to Exclude" list with the ability to remove them and MACs already on the exclusion list are automatically hidden from the duplicate table.
-
Devices with excluded MAC addresses will be filtered out from future discovery scans and will not appear in the Discovered Assets view.
-
Settings are propagated across all applicable levels: Partner, SO, and Customer.
Continued Development on CMMC-Compliant Version of N-central for On-Premises Partners
We are continuing development on the CMMC-compliant version of N-central, specifically designed for on-premises partner-hosted instances. This work is part of our broader initiative to ensure CMMC Level 2 compliance, supporting partners managing environments aligned with U.S. Department of Defense (DoD) cybersecurity requirements.
Ongoing Improvements to Analytics
We continue to invest in scalable analytics to help partners make data-informed decisions across their environments by adding further improvements to lay the groundwork for more actionable insights and future analytics-driven features.
Native PSA and Autotask REST API Support
The following two integration features will now generally be available to all partners as of this release:
-
HaloPSA Native Integration.
-
Autotask REST API Support.
These features were previously made available only through controlled rollout but are now open for full partner adoption to support improved service workflows and API flexibility. For detailed information on setup and capabilities, see: 2025.2.1 Release Notes
Bug Fixes
A range of high-impact bugs have been resolved in this release. Be sure to review the full list included below for more details.
Category |
Updated Summary |
Issue Key |
---|---|---|
Most Impacted |
||
Core |
Blocked Reports Due to Envoy Restrictions
Issue: Some reports failed to load because updated Envoy configurations blocked access to the /reportAction.do endpoint. Fix: Updated Envoy routing rules to restore access to all affected reports. |
NCCF-663428 |
Core |
Stale Service Monitoring from Probes
Issue: Monitoring data appeared outdated because of interrupted probe communication. Fix: Corrected probe-side handling to ensure continuous and accurate service monitoring. |
NCCF-626897
|
Core |
GSuite Login Redirect Restored
Issue: After upgrading to 2025.2.1.8, users logging in via GSuite were not redirected to the Google SSO page as expected. Fix: We corrected the redirect logic to ensure GSuite users are seamlessly routed to Google SSO after entering their email without needing to manually click a “Sign in with Google” button. |
NCCF-661120 |
Performance & UI Fixes |
||
Core |
Analytics Reporting – NCOD Instance
Issue: Some hosted environments lacked analytics data, which prevented users from accessing dashboards and reports. Fix: Enabled analytics data capture and availability for this instance. |
NCCF-649734 |
Core |
Slow Device Deletion Performance
Issue: Deleting a large number of devices caused performance slowdowns due to database locking. Fix: Optimized the deletion process to reduce database contention. |
NCCF-546488 |
Core |
Launch Darkly Crash on Legacy Customers
Issue: The Launch Darkly client crashed due to missing timestamps for older customers. Fix: Added fallback logic to handle missing creation time. |
NCCF-546103 |
Core |
All Devices View Filtering Incorrectly
Issue: The All-Devices view did not respect Service Organization (SO) boundaries during filtering. Fix: Corrected the filter logic to properly account for SO segregation. |
NCCF-538809
|
Core |
UI Performance – All Devices page slow performance
Issue: The "All Devices" page became slow when using the “More Devices” filter option. Fix: Improved page performance by optimizing how the filter interacts with large datasets. |
NCCF-566023 |
Core |
Take Control reinstalls triggered Too Early
Issue: Some devices were flagged for reinstall prematurely due to recovery logic errors. Fix: Improved recovery checks to avoid unnecessary reinstalls. |
NCCF-533915 |
Core |
Device Selection UX in Custom Property Updates
Issue: Device selections remained active after custom property edits, leading to UI confusion. Fix: UI now clears selections properly after applying custom property changes. |
NCCF-459877 |
Integration & Experience Fixes |
||
Core |
Autotask: Ticket closures issues
Issue: Tickets failed to close automatically during maintenance events. Fix: Updated closure logic to ensure consistent handling with Autotask integration. |
NCCF-535280 |
Core |
System Error When Creating Customers with Correlated Notifications
Issue: When trying to create a new customer while setting up correlated notifications, the system would show an error and fail to complete the setup. This happened because the system was incorrectly looking for a "profile ID" that didn’t exist, instead of using the correct "correlated profile ID". Fix: The system now properly uses the correlated profile ID when setting up correlated notifications, preventing the error and allowing customers to be created successfully. |
NCCF-674670
|
Core |
PSA Integration Stability (ConnectWise / Autotask)
Issue: PSA export profile was unintentionally deleted after customer removal from ConnectWise or Autotask. Fix: Adjusted deletion logic to retain export profiles when associated customers are removed. |
NCCF-652816 |
Core |
Data Type Handling in ConnectWise Exports
Issue: Exports to ConnectWise did not honor distinctions between “Text” and “Number” fields. Fix: Field export logic now correctly respects data type definitions. |
NCCF-559109 |
Core |
Asset Scans not running according to schedule
Issue: Scheduled asset scans were not triggering at expected intervals. Fix: Fixed internal scheduling mechanisms to restore consistent scan execution. |
NCCF-638003 |
Core |
User Access Control / Permissions
Issue: Misconfigured permission logic allowed users unauthorized access to privileged pages. Fix: Applied proper permission restrictions to prevent escalated access. |
NCCF-606073 |
Core |
LDAP to SSO Account Migration Logic
Issue: Standard LDAP accounts were incorrectly migrated to MSP SSO, causing login and account management issues. Fix: Refined account migration rules to exclude standard LDAP users from MSP SSO transitions. |
NCCF-600010 |
Core |
Endpoint Detection and Response (EDR) Service Assignment
Issue: EDR monitoring services were not automatically assigned to newly onboarded devices. Fix: Ensured automatic assignment of EDR services during device provisioning. |
NCCF-555283 |
Core |
Server Connectivity – EDS Communication
Issue: N-central server experienced periodic disconnections from the External Data Store (EDS). Fix: Improved connection stability and retry mechanisms to maintain persistent communication. |
NCCF-541976 |
Core |
SNMP Parsing – Linux Custom Types
Issue: SNMP failed to correctly parse custom entries of type "String" on Linux systems. Fix: Fixed string-type handling logic in SNMP implementations. |
NCCF-125587 |
Ecoverse |
LDAP User Login Name Validation Appears Incorrectly After Import
Issue: LDAP user accounts displayed a validation error on the Login Name field when editing, despite this field being non-editable for LDAP users. This prevented any updates to the account. Fix: The Login Name field for imported LDAP accounts is now correctly disabled, and the erroneous validation error has been removed. |
FSN-11683 |
Ecoverse/ Core |
Device Provisioning & Remote Access (Tools / Take Control)
Issue: After upgrading to 2024.6, devices failed to receive configuration, causing tools and Take Control to stop working. This was due to missing or unavailable Ecoverse URLs. Fix: Introduced fallback logic and improved error handling to ensure devices can still be provisioned even when Ecoverse URLs are missing, restoring functionality for tools and Take Control. |
NCCF-530680 |
How to Prepare for 25.3 in Advance
If you would like to participate in the public preview to test the new 2025.3 version in a non-production environment before rolling it out fully, the Public Preview of 2025.3 will be available around mid-July.
Stay Tuned
Be on the lookout for the official N-central – 2025.3 release in July 2025. We look forward to delivering these exciting updates—stay tuned for the full release package!