Hello if i have a Patch for example July Update Patch and i approve this Patch on August and there will come the August Patch, will this August Patch cancle the approval from July Patch? If yes how can i deactivate this?
If I update an existing script check by uploading a new version of the script with Script Manager, that new version gets (at some point) automatically pushed down to endpoints that were using the check with the previous version. ....or so I thought. This seems to mostly work, but there are definitely times when something goes wrong and a particular endpoint doesn't get the update.
As soon as I find an endpoint that didn't get the update, then I lose faith that it was consistently applied and I end up re-pushing the entire monitoring template to the site...which comes with the potential side benefit of doubling checks even though I checked "replace existing checks". Ugh - is it Friday yet?
Anybody else think the GUI is absolute turtle slow past two days?
Running Patch Scan, Searching PC's, Clearing Filter... etc.. all take several seconds when for years it's been pretty instant.
Hello i have a automatic patch approval rule for some devices and on the targets it shows me No Approval (set) on another filter. What does it exactly mean because its only on 2 Filters and the rest is No Approval (inherited) and the Filter with (set) dont get the patches although i have a seperate Approval rule for this Filter where the patch should be approved in 7days but it never aprrove them.
Coffee thoughts.
Please create an Adlumin native integration for NCentral. Working the same as current EDR, Cove dashboard on All Devices screen.
Recently, we had a meeting with our N-central Solutions Engineer to review our patching setup (as it's a mess so we are trying to bring in some standards), particularly around automatic patch approvals
I raised a support ticket some time ago to check what a previous colleague had set up which for arguments sake was
Definition
Critical
Security
Approved and then a decline rule below those (so the order is approve rules above the decline, everything else)
Support reviewed it and said it was correct, but in the recent meeting with our N-central solutions engineer, he said that was wrong and that the order should be Decline above all the approve rules.
So order wise
Decline All
Approve the following
Does anyone know which is correct?
I can't find the article, but I've tried reading the order of operations article and to be honest, I just find it too confusing XD so just wondering what others have done.
Thanks
I wanted to post this over here to make sure everyone saw it. I emailed my account manager this week but got no response at all.
Has anyone successfully installed and then connected to a remote agent running on Linux (debian)?
I have it installed and running on a test Mint 22.3 system, but from the RMM web console the remote control is greyed out..
This is becoming more of an issue for me due to so many clients moving away from Windows.
Here is a follow-up update to the N-central CVE-2026-18556 & CVE-2026-19557. The full details and post here available at this URL: https://www.n-able.com/blog/n-central-security-update-august-10-2026
The TLDR :
What happened : How we found it :
If you have not yet applied Hotfix 2 (2026.3.1.10), please do so
On July 31, our Adlumin MDR solution detected unusual activity inside a customer environment and identified a threat actor actively exploiting a previously unknown vulnerability in N‑central. We want to be straightforward about this: we detected this ourselves, in real time. That matters, not because we want recognition for it, but because it is evidence that layered, continuous security monitoring works. It is also the reason we were able to respond as quickly as we did.
Once identified, our engineering and security teams mobilized immediately. We published guidance the same day, registered CVE-2026-18556, and released Hotfix 1 (2026.3.1.7) on August 2, and registered CVE-2026-18577. When continued monitoring on August 6 surfaced a related attack path, we released Hotfix 2 (2026.3.1.10) the same day with additional hardening measures that build on and supersede Hotfix 1.
The attack
A threat actor exploited a vulnerability in N‑central that allowed remote administrative access without authentication. Once inside, they used N‑central’s Take Control feature to connect to managed devices, and registered Cloudflare tunnel services on those devices to maintain persistence even after their access to N‑central was revoked. Hotfix 1 addressed the original access point. Continued monitoring identified a related attack path, which Hotfix 2 addresses with additional hardening.
The impact
A limited number of customers have been identified as impacted, and our team has directly engaged with each of them. If you have heard from us, you have a dedicated point of contact and we are with you. Our investigation remains active and ongoing and we are not calling this closed until we are fully confident in that conclusion.
Timeline: what happened
If you delayed upgrading, please read this carefully
Applying Hotfix 2 closes the vulnerability that allowed attackers in, but it does not remove a threat actor who may already be present in your environment. For customers who have waited to patch, it is critical to understand that during that window, attackers have been observed creating new accounts and resetting existing ones to maintain persistence. Upgrading is an essential first step, but it is not the last one. If you applied either hotfix more than a few days after it was released, you should treat your environment as potentially compromised and conduct a thorough review of all user accounts, access privileges, and activity—regardless of what our IOC scanning tool returns. If you find anything unusual or need assistance with that review, please contact our support team immediately at me.n-able.com.
What we ask of you
No software is immune to vulnerabilities. That is the reality of the world we all operate in. What separates organizations that weather these moments from those that don’t is preparation, speed, and the strength of the partnerships around them. We are committed to being that partner for you.
Resources
Hello all,
Does anyone know if N-Centrals Patch Management Engine automatically handles Bitlocker suspension when deploying hardware level/driver updates? If not what are some alternative solutions to handle this and avoid blue screens and/or recovery key events?