Patch Management Engine (PME) 2.13.15 – Release Candidate

A new Release Candidate (RC) version of the Patch Management Engine is being made available to N-central assets configured to use the RC channel. This release focuses on improving patch reliability, cache handling, End-of-Support filtering accuracy, security posture, and overall resilience of patch detection and installation workflows.

Improvements Included

  • Improved Extended Security Update (ESU) handling for Windows devices: Improves End-of-Support filtering so that Extended Security Update (ESU) licensing is consistently recognised across supported Windows operating systems, ensuring eligible devices continue to receive applicable updates. (PMCM-11363)
  • Improved cache integrity validation for patch distribution: Enhances CRC validation when patches are moved between cache locations, improving resilience and reducing the likelihood of patch corruption or transfer inconsistencies. (PMCM-11448)
  • Improved patch reporting accuracy for browser updates: Resolves an issue where certain browser patches could display incorrect installation timeline information, improving reporting consistency and avoiding impossible installation dates. (PMCM-11495)
  • Improved security posture of Third-Party Patch components: Removes bundled 7-Zip binaries from Third-Party Patch components, reducing security exposure and improving the overall security posture of the patching stack. (PMCM-11496)
  • Improved .NET patch uninstall handling: Resolves an issue where certain .NET patches using newer Microsoft naming conventions could fail during uninstall operations when processed via DISM. (PMCM-11521)
Continue reading
Posted in N-central | Comments Off on Patch Management Engine (PME) 2.13.15 – Release Candidate

Risk Intelligence 16.1

We’re pleased to announce an upcoming release for N-able Risk Intelligence, scheduled for delivery starting on Tuesday, May 26th, 2026.

This release is focused on upgrades to our back-end systems addressing several security related improvements, and infrastructure enhancements.

Continue reading
Posted in N-sight, Risk Intelligence | Tagged , | Comments Off on Risk Intelligence 16.1

Release Take Control – Standalone Mac Console/End-User Viewer 6.00.72

Fixes

  • Resolved an issue where remote sessions launched from the Admin Area could fail to start on macOS due to protocol handler handling in specific browser / installation scenarios.
  • Session launches initiated directly from the technician console were not affected.

This update improves reliability and consistency when launching remote sessions from the Admin interface.

Posted in Take Control | Comments Off on Release Take Control – Standalone Mac Console/End-User Viewer 6.00.72

Announcing the Release of Report Manager 5.0 SP9

Report Manager 5.0 SP9 (5.0.9.12)

Detailed Release Notes

Download link (login required)

Report Manager 5.0 SP9 includes backend improvements that enhance report accuracy, performance, and system reliability.

The service pack should be applied to your Report Manager server and does not require an upgrade to your N-central server version.

For full details, including the complete list of fixed issues and download information, please refer to the detailed release notes link above.

Posted in N-central | Comments Off on Announcing the Release of Report Manager 5.0 SP9

N-central & N-sight: Improvements to Linux Reboot Status, New Reboot Workflow Enhancement, More Dynamic Tagging Filtering Options 

Updates are now available across Assets and Device Workflows. These improve visibility into device state, expand the asset data available for tagging and automation, and streamline common navigation and reboot actions. Details are outlined below. 

‘Reboot required’ status now available for Linux 

The ‘Reboot required’ asset status is now available for Linux devices in the Assets View. This brings Linux in line with other platforms and makes it easier to identify devices that need a restart to complete updates or configuration changes. 

The following Linux distributions are supported: 

  • Debian 11 and 12 
  • Ubuntu 20.04, 22.04, and 24.04 (LTS) 
  • RHEL / CentOS 7, 8, and 9, and AlmaLinux 9 
  • openSUSE 15 
  • Amazon Linux 2 

To learn more about how this status is calculated and how it can be used operationally, see our earlier post: https://status.n-able.com/2026/03/10/new-reboot-required-and-system-shutdown-activities-for-n-central-n-sight/ 

More asset data available for dynamic tags 

Make dynamic tags more actionable with security and reboot signals. When creating dynamic tags, you can now filter on additional asset data. The following data points are now supported: 

  • Secure Boot status 
  • BitLocker status 
  • OS feature release 
  • Reboot required 

To create and manage tags, go to Tag Management in the left‑hand navigation. 

Continue reading
Posted in N-sight | Comments Off on N-central & N-sight: Improvements to Linux Reboot Status, New Reboot Workflow Enhancement, More Dynamic Tagging Filtering Options 

Release Take Control – Integrated Mac Viewer 6.00.71

This release focuses on session reliability, stability, and security improvements across the macOS Console/Viewer.

Improvements

  • Added option to enforce TLS-only connections for improved security.

Fixes

  • Fixed issues preventing sessions between macOS devices and remote connections from working correctly.
  • Resolved multiple Viewer crashes across different features (copy/paste, system info, connection details).
  • Fixed issues with some session recordings not uploading as expected.

Posted in Take Control | Comments Off on Release Take Control – Integrated Mac Viewer 6.00.71

macOS Patching – Public Preview for N-sight and N-central

We are pleased to announce the Public Preview of macOS Patching, bringing Apple macOS devices into our new unified, cross‑platform patching experience. This release will be rolling out over the next 24–48 hours.

This release extends the same modern patching platform and workflows already available for Linux, while introducing macOS‑specific capabilities required to meet Apple’s security and operating system requirements.


What’s Included in the Public Preview

macOS Patching uses the same core detection and execution workflows as our existing Linux OS patching, providing a consistent experience across operating systems.

Core Capabilities

  • Detection and installation of macOS operating system updates
  • Asset‑level and patch‑level views
  • Consistent patching workflows aligned with Linux patching
  • Centralised visibility within the new patching experience

Key macOS‑Specific Functionality

In addition to the shared capabilities, macOS Patching introduces workflows designed specifically for Apple Silicon and user‑centric macOS environments.


End User Interactive Reboot Pop‑ups

macOS updates are applied during a system restart. To support user‑driven environments, macOS Patching includes end user interactive reboot notifications.

What this provides

  • Clear communication to end users when a restart is required
  • On‑screen prompts that explain why the reboot is needed
  • The ability for end users to:
    • Restart immediately, or
    • Defer the restart to a more convenient time

Why this matters

This workflow balances security and usability by ensuring updates are completed while minimising user disruption. It supports environments where devices are actively used and restart timing must be communicated clearly.


Volume Ownership for OS Update Authorisation

Apple requires additional authorisation to install operating system updates on Apple Silicon–based Macs. This is enforced through volume ownership.

macOS Patching includes a secure workflow that allows technicians to provide the required credentials to authorise OS updates.

How it works

  • A one‑time setup command is run to provide volume owner credentials to the patching engine
  • Credentials are:
    • Fully encrypted
    • Stored securely
    • Used only to authorise macOS operating system updates

Once provided, the engine gains the necessary permissions to perform OS updates on the device.

If volume owner credentials are not supplied, macOS will reject the update and the patch will fail with an Invalid Credentials status and the error message within the failed patches view will contain a link to a knowledge article to help your technicians diagnose.

Step by step documentation is also available:

N-sight:https://documentation.n-able.com/remote-management/userguide/Content/patching/manage-apple-patches.htm
N-central: https://documentation.n-able.com/N-central/userguide/Content/patching/manage-apple-patches.htm

Important notes

  • This setup is typically required once per device
  • Credentials only need to be updated if the volume owner changes on the device
  • This workflow aligns with Apple’s platform security requirements
  • How to’s are available within our documentation and knowledge base

You can read more about volume ownership and authorisation in Apple’s documentation: https://support.apple.com/en-gb/guide/deployment/dep24dbdcf9e/web

Coming Soon

The following capabilities are in active development and will be introduced as the macOS and Linux patching experience continues to evolve:

Apple third‑party application patching
Support for detecting and deploying updates for commonly used third‑party applications on macOS devices.

Linux third‑party application patching
Extension of the existing Linux patching experience to include third‑party application updates alongside OS updates.

Linux and Apple Patch Policies
Unified, policy‑driven patch management for both Apple macOS and Linux, enabling greater automation, control, and consistency across platforms.

Windows OS and third‑party application patching
New support for Windows operating system and third‑party application updates as part of the unified, cross‑platform patching experience.


Summary

The macOS Patching Public Preview brings macOS devices into a single, modern patching experience, reducing operational complexity while respecting Apple’s unique security and user requirements. It enables teams to apply consistent patching practices across platforms while meeting macOS security constraints and keeping end users productive.

As a Public Preview, functionality and workflows may evolve based on customer feedback prior to general availability.

Posted in N-central, N-sight | Comments Off on macOS Patching – Public Preview for N-sight and N-central

N‑sight Update: Web Protection default behaviour

We have recently made changes as part of the N‑sight release, and you may notice that the Web Protection feature is not visible or enabled in your account by default.

What’s changed

Web Protection is now disabled by default for:

  • New N‑sight customers, and
  • Existing customers who have not previously enabled Web Protection.

Customers who are already using Web Protection will continue to have access to the feature, with no change to current functionality.

Disabling the feature by default helps ensure a more consistent experience and avoids unnecessary configuration for customers who are not currently using Web Protection.

What this means for you

  • If you are not using Web Protection, no action is required.
  • While we address the defect, customers seeking web security solutions can consider using DNSFilter as an alternative option.

We’ll share further updates as improvements and fixes are rolled out in upcoming N‑sight releases.

Posted in N-sight, Web Protection | Comments Off on N‑sight Update: Web Protection default behaviour

SentinelOne Windows Agent Installer Update: Installation Method Change

Starting with SentinelOne Windows Agent 25.2 SP1 / 25.2.5.437, the standard EXE installer no longer supports the previous double-click GUI flow for entering the site token.

Previously, admins could double-click the EXE installer and paste the token into a prompt. Going forward, the EXE installer must be run using command-line parameters or deployed through a software distribution platform.

Why this changed

This update is part of SentinelOne’s Guardian installer / SentinelInstallerDriversecurity hardening. It improves protection around installer and upgrade workflows and helps reduce exposure to Bring Your Own Installer (BYOI)bypass attacks.

Supported installation methods

EXE installer via elevated Command Prompt
SentinelOneInstaller.exe -t <SITE_TOKEN>

MSI installer via command line or deployment tool
msiexec /i SentinelOneInstaller.msi SITE_TOKEN=<SITE_TOKEN>

The MSI package can also be deployed through tools such as:

  • RMM platforms
  • MDM platforms
  • Microsoft Intune
  • Microsoft SCCM
  • Other software distribution tools

What remains unchanged

The installed SentinelOne agent is functionally the same. This change only affects how the installer is launched and authorized.

Important notes

  • The double-click GUI token prompt will not be reintroduced for this installer line.
  • EXE upgrades run silently by default.
  • The -q parameter is no longer required.
  • Tokens must be provided using -t.
  • The MSI installer is unchanged.

Recommended action

Update any deployment scripts, internal documentation, and support guidance that reference the old double-click GUI installation flow. Administrators should now use command-line installation or standard deployment tools for SentinelOne Windows Agent installations.

Posted in EDR, N-central, N-sight | Comments Off on SentinelOne Windows Agent Installer Update: Installation Method Change

Release Take Control – Standalone Mac Console/End-User Viewer 6.00.71

This release focuses on session reliability, stability, and security improvements across the macOS Console/Viewer.

Improvements

  • Added option to enforce TLS-only connections for improved security.
  • Improved display of technician identity by supporting technician name aliases.
Continue reading
Posted in Take Control | Comments Off on Release Take Control – Standalone Mac Console/End-User Viewer 6.00.71