A patch window that extends beyond the server
N-able’s November 10 security update for N-central assigns a significant part of the rollout to customers who buy the hosted service. N-able handles their servers. The managed service provider or other customer still has to upgrade the agents and probes in the environments it administers. For providers running their own N-central servers, all three parts of the rollout are their responsibility.
What the service desk can lose
The release changes how the agent and probe communicate. N-able says that an older probe remains compatible while agents are being upgraded. Upgrading the probe first can interrupt communication until the agent and patch management engine reach compatible versions. One visible consequence is loss of the offline patch cache. The engine update is delivered separately. A provider tracking completion by the server’s build number alone could therefore close its ticket while a customer site still cannot use a cache it relies on.
The health sector receives its own alert
NHS England’s November 11 advisory lists seven vulnerabilities covered by the release, including two rated critical. Its security operations centre cited observed exploitation attempts and advised affected organisations to take servers offline until they could apply the patch. The alert identifies no compromised healthcare organisation. For a provider serving a health customer, a support handover needs to cover how staff will obtain assistance during the maintenance window. N-able’s release notes say built-in remote control is temporarily disabled in this build, while its separate Take Control tool remains available.
Sources & further reading
- N-able, November 10 HF2 release and compatibility notes ↗
- NHS England, November 11 cyber alert CC-4891 ↗
Our practical suggestions are editorial guidance. Verify applicability against current source and vendor instructions.
