Providing Patch Management With N-central - N-able Technologies

N-central 7.2 Providing Patch Management With N-central
Upgrading Patch Management from N-central 7.0
While N-central 7.0 provided patch management using integration with Microsoft WSUS 3.0, the features
included in N-central 7.0 were quite different in both architecture and scope. Due to these
changes, any existing N-central patch management configuration options will not be upgraded.
To use your existing patch management configuration in N-central 7.2
1. Upgrade your N-central server to 7.2.
2. Uninstall the N-able Connector from the WSUS server.
3. On your domain controller, remove all patch-related group policy settings.
4. Install a 7.2 agent on the WSUS server.
5. Promote the WSUS server to the SO-level.
6. Configure the WSUS options to match the settings that suit your needs and environment.
7. Enable the WSUS server.
8. Create a patch profile at the SO-level:
a. Specify the patch management settings.
b. Set the WSUS server to Best Available. With only one server (at the SO-level) all devices will
use it.
9. Enable Patch Management on all devices for which you want to manage patches. You can use your
folder templates to simplify this task.
This will cause all devices that you have enabled for Patch Management to check into the WSUS server.
N-central will automatically create the groups and manage the devices.
Note: It can take several hours for all of the devices to register with N-central and be displayed.
At this point in time, there will be no approved patches. All existing patches that were installed on
devices will remain but all other patches will be Not Approved so that no changes should take place.
Going forward, you simply have to approve any patches that you wish to have applied.
- 34 -