Step by setp video: https://www.youtube.com/watch?v=a5lSbSbq2pY

Does have some back-and-forth config for Huon, the list below is in the ‘ideal’ order.

Pre-Checks:

1) **Ensure Group Policy doesn’t conflict with NABLE**

2) All servers and workstations REQUIRE Nable Agent for Patch management to work

Configured once per client:

Configuration>Patch Management > Caching – Configure the location for the storage + ensure appropriate disk space.

————————————————————————————————————————————————————————–

BELOW: I recommend you create each group you require all at once to save going back and forward.

————————————————————————————————————————————————————————–

Configured per Server/Workstation Group:

Configuration>Filters> Create Sever Groups + Workstation group – clone if applicable from MCAA or NBRS

NB: Specify the Client as the first rule to ensure you do not impact any other client with the same server name

eg. More than 1 client could have a server called ‘MX1’ . That would bring other clients into this patching group.

Configuration>Patch Management> Create Profiles, you CANNOT enable ‘download before install’ until you configure a schedule. So do that then go back to the general tab.

-Set the check for updates 5-10mins apart between server groups (group 1- 06:00, group 2 – 06:10, etc)

-Set the Patch schedule 90mins apart between groups (group 1 – 00:00, group 2 – 01:30, etc)

NB – Associated rules have not been created at this point, but auto configure after the below step is completed.

Configuration> Monitoring> Rules>

-Maintenance Windows are added in this section also.

-Create you maintenance window to match your patch time

Finally – Configuration>Patch Management>Automatic Approvals> Critical + Security Updates + set products, then Set targets.

Then Create Wake on Lan for desktops…

WOL is required for after-hours patching of workstation