A new addition to Endpoint Remediation, joining our Mac and Linux engines. Available today for on-demand patching.
We’re excited to announce a brand-new Windows OS patching engine, now available in both N-sight and N-central.
It’s part of Endpoint Remediation and joins the Mac and Linux engines you may already use, as well as 3rd Party Patch. It’s built on the same modern architecture, so Windows patching now follows the same consistent approach as the rest of your estate.
Available today: New Windows on-demand patching (Preview)
You can use the new Windows OS engine on demand from today. Run patching against selected devices whenever you choose and see the results straight away.
Policies for the new engine are in their final stages. We expect to launch them in the next couple of weeks. With policies you’ll be able to automate approvals, schedules and reboot behaviour, using tags to target groups of devices.
A new engine, fully independent of PME
This is a new engine, separate from the existing Patch Management Engine (PME) you use in N-sight and N-central today.
- PME is not affected. Your existing PME setup keeps running exactly as it does now.
- No PME settings are reused. The new engine doesn’t read or use any approvals, schedules or profiles you’ve set up in PME. It starts fresh.
- Both can run side by side. You don’t have to switch anything off to try the new engine.
Take care with timing: because the two engines run independently, don’t schedule patching with both the new engine and PME for the same time window on the same devices. If both try to install updates or reboot at once, you may get conflicts and cause one or both attempts to fail.
Our recommendation: start with test devices
Now is a great time to get familiar with the new engine:
- Pick a small group of test devices. Non-critical machines are ideal.
- Run on-demand patching with the new engine from Endpoint Remediation.
- Review the results and get comfortable with the workflow.
- Make sure PME isn’t scheduled to patch those devices at the same time.
When policies launch in the coming weeks, you’ll be able to automate patching on the new engine, control the OS access, leverage end user interactive pop-ups etc. By then you’ll have the confidence to deploy out to a larger number of assets
What’s coming next
- Policies, expected in the next couple of weeks
- Registry controls and wake device to patch
- Reports
- Approval Delays and much more