Skip to main content

Patch Management

1.0 Introduction

Naverisk simplifies patch management across your client's devices, allowing you to view availability and missing Windows, Mac and Linux patches for an individual device, or across one or all of your clients. Patches can be installed on-demand basic or automated for a re-occurring schedule.

This guide covers managing and scheduling your patching as well as understanding the patch reports.

1.1 Disabling Microsoft Windows Auto-Updates

By default, Naverisk does not change any existing Windows update settings. Devices that were configured to automatically download and install updates (Windows 10+ default setting) will continue to do so after the agent is installed. This ensures that devices will continue to receive updates until you start actively managing the patching.

It is possible to use patch management without disabling Windows auto-update. Devices will have updates installed when they are pushed out by Microsoft, with Naverisk being used to check for devices that have not received updates and triggering the installation of any required patches.

Disabling automatic updates will allow you to have full control over the patching process. You can prevent users from installing patches and feature updates themselves, and gives you control over which updates are installed and when. This allows you, for example, to test new patches for compatibility with key applications before deploying them across all devices.

If you are managing domain-joined devices, you should use a domain GPO to disable windows updates. This is because any settings made locally on a device will be overwritten by the policies configured on the Domain Controller.

A script pack and device role are available in the Routine Store to allow you to easily disable Windows auto-updates on non-domain computers. From the store, download the Disable Windows Updates script pack and the Disable Windows Updates Daily device role. Import the script pack and device role into Naverisk.

The script pack will disable auto-updates, and also block the user from manually installing updates. This can be run as required on the desired device(s).

The Disable Windows Updates Daily device role can be applied to individual devices or multiple devices by applying to one or more device types. This device role automatically runs the Disable Windows Update script each day. This ensures that the automatic updates remain disabled if a user (or Microsoft) changes the settings). If you prefer to run the script less frequently, for example, weekly, you can edit the script pack to specify a different frequency.

2.0 Patching

2.1 Patch Management Module

For each device that an agent is installed onto, a daily scan will automatically run to check for new OS updates. The results of these scans can be located for an individual device from Devices > Device Details > Patch Management, which indicates which OS Updates are missing from this Device. It will show a list of Updates that could be installed but are not.

This scan will run automatically once a day, but can also be manually triggered to run by clicking the Retrieve Information button in the top left corner, or the scan may be scheduled to run on demand via a scheduled job or automation rule.

When manually triggered, this scan can take some time; on clicking the Retrieve Information button, be prepared to wait for several minutes or to come back to this package Tab later to view the results.

2.2 OS Patches Tab

The OS Patches tab shows all patches and software updates missing from the selected client. This is an aggregated list of all the patches reported from all of the devices for that client. A combined list of patches can include patches reported by sub-client devices by ticking the appropriate checkbox.

You can view available patches for all devices, or create a targeted list using the available filters, for example, show only Windows 10 patches or show Ubuntu patches.

2.3 Manual Patching

Manually Applying Patches to just One Device

  1. Navigate to the Device which you would like to Patch.

  2. Select Patch Management (one of the buttons underneath Device Details).

  3. Select which updates you would like to install from the list of available Updates.
    (If no Updates are listed, click 'Retrieve Information' to refresh the list of available Updates.)

  4. From the ‘Select a Task’ dropdown menu. click ‘Install Selected Updates’

  5. In the confirmation window, click ‘OK’ to have the device install these updates immediately.

Manually Applying Patches to all applicable Devices

Please be aware that this will install the patch across all devices requesting this patch for the selected client, and may include sub-client devices if the appropriate checkbox has been ticked

  1. Navigate to the OS Patches tab

  2. Select which updates you would like to install from the list of available Updates.

  3. From the ‘Select a Task’ dropdown menu. click ‘Install Selected Updates’

  4. In the confirmation window, click ‘OK’ to have the device install these updates immediately.

2.4 Scheduled/Automated Patching

Automating the patching process is a two-step process, consisting of the scheduled job which is responsible for the actual installation of the patch, and an approval/authorisation process which determines what patches the system is permitted to install via that scheduled job.

2.4.1 Creating a Scheduled Job for patch installation

NOTE: A scheduled job can only install patches that have been previously authorised for installation. If there are available patches, that have not been authorised when the job runs, then nothing will be installed.

  1. Click the +NEW button and select Scheduled Job to create a new job

  2. On the General tab, please add an appropriate Job Name and Description, and ensure that the Enabled checkbox has been selected

  3. Select the desired schedule and runtime for the job to start

  4. Click Select Device Filter to select the specific Devices on which you would like to install Patches. It is at this stage you can choose to Apply Updates to entire Client Groups or subsets of them (such as particular Device Types or specific machines in that Client Group).

    Leaving the Device Filter option to the default values will have the scheduled job run across all devices under that client.

  5. Across the top of the pop up window, select the Action tab

  6. In the Action section, found in the middle of this page, select the Install OS Patches option

  7. On the left you will have a Patch Age field. This is to specify a minimum length of time that a patch must be released for, before it can meet the criteria to be installed by this scheduled job. Setting it to 3 days would mean that a patch needs to have been released for at least 72 hours, (allowing time for a bad patch to be withdrawn and rereleased), where as a value of 0 will result in patches qualifying for scheduled installation as soon as they are detected by the application.

  8. On the right there's a box for selecting what update categories you would like this scheduled job to update. This allows you to potentially run different patches on different cycles. For example, the Definition Updates category patches are frequently and irregularly released, but do not require restarting the device. A daily scheduled job could be created to install these as they become available. Where as the Updates category patches often do require a full device restart to complete the update installation. So a weekly or monthly scheduled job could be used to install these patches and restart the device outside of business hours.

  9. The Pre Action and Post Action segments contain a few other options that may be useful for automated patching:

    Queue Job while Device is Off-line – This may help capture laptops and devices which may frequently be powered off during the intended patch installation window

    Maintenance Mode – Patch installation may increase CPU or RAM temporarily beyond normal monitored thresholds, so enabling Maintenance Mode – Performance during the patch installation may be beneficial. Similarly, if a reboot has been included, then setting Maintenance Mode will suppress the notifications from the planned restart.

    Restart if Required – This will automatically restart the device should the patch installation require a device restart to complete the install.

  10. In the below image you will find our recommended configuration of the scheduled patch job, this configuration has been found to work the best:

  11. After you press Save, the job will be Scheduled and Updates will run at the selected time.

2.4.2 Authorising Patches for Scheduled Installation

NOTE: Authorising patches is a process of flagging the patch for automatic installation. A scheduled job can only install patches that have been previously authorised for installation. If there are available patches, that have not been authorised when the job runs, then nothing will be installed.

Patches can be Authorised or Excluded for automatic installation at three different levels.

Specific Patch Categories:
When updates are released, the provider will flag the patch with a specific category such as Drivers, Definition Update, SQL Server or Security Update. An entire patch category can be automatically granted authorisation (or exclusion) for all patches released for that category.

  1. Navigate to the Settings page (OS Patches) to configure Patch Category rules for each client

  2. Click the Category Authorisations or Category Exceptions button

  3. In the new pop up window, select the desired patch categories and click OK

  4. Once the window has closed, finalise the change by clicking Save at the bottom of the page.

Specific Patch:
As mentioned previously the OS Patches tab shows all patches and software updates missing from the selected client. This is an aggregated list of all the patches reported from all of the devices for that client. Here, we can authorise or exclude specific patches for the client.
NOTE: This will override any Patch Category settings for the individual patch.

  1. Navigate to the OS Patches tab of the Device main page to configure Patch rules for a specific patch of a Client(s).

  2. Select a patch and click the Add Authorisations option in the Task dropdown to authorise a patch for an entire client, (or multiple clients if the Show Sub-clients is enabled)

Specific Device:
Navigating to the device detailed patch management page will provide access to the list of patches available for that specific device. Here, we can authorise or exclude specific patches for that specific device.
NOTE: This will override any Patch Category or Specific Patch settings for the patch of this device.

  1. Navigate to the Patch Management tab of the Device to configure Patch rules for a specific patch of that specific Device.

  2. Select a patch and click the Add Authorisations option in the Task dropdown to authorise the patch on the device.

3.0 Alerts: Outstanding Patches against a Client

The location for the OS patch tab is under the settings page as below. Here you can Configure OS Patch settings, SLA-based alerting, and Patch Category rules.

Based on the Thresholds you select, Naverisk will raise Tickets with the appropriate SLA statuses for any Devices in that Client Group with outstanding Updates after the Threshold period has passed.

By using the Offline Threshold setting, any devices that have been continuously offline beyond the configured threshold, will be excluded from the monitoring and will not generate a patching alert Ticket.

The tickets that are raised as a result of these SLA Status Thresholds are special. They contain an extra button ‘Report Devices’ which opens an embedded report displaying missing patches which do not belong to any exception categories.

4.0 Clients Reports - Patching

As it is often important to provide your Clients with a summary of their organization’s Patching status, we have created a report called the Patch Summary Report (Reports > Client Facing > Patch Summary). This Report can graphically and numerically represent the outstanding Patches for a server or workstation respectively.

While you can run this Report manually, it is recommended that you automate this Report to be sent to you following Scheduled Patch installations. That way you can keep a running record of the Patching status for a company and easily present this to your clients to show the value of your service.

If you’re planning to schedule the report to be sent out within 24 hours of the patch job, it is recommended to set up another scheduled job before this to run the Windows update scan on these devices. This is to ensure the report is completely accurate with what patches have been installed/are still available.

To Schedule, this, create a New Scheduled Job and time it to happen after your Scheduled Patches (and Device Reboot task if applicable).

Example below:

To Schedule, the report, create a New Scheduled Job and time it to happen after your Scheduled Package Scan.

Note that you need to specify which Devices you would like this Report to cover (using Device Filter) and the recipient of the Report (with Recipient Email).Example below:

4.1 Other Reports - instead of the Patch Summary

Patch Management - This Report is useful for displaying missing Updates for selected Devices and Clients.

Software Changes – this report can be used for displaying recently installed updates as well as application changes on selected devices and clients.

5.0 Troubleshooting

If you find that Patches are failing to install on Devices or Naverisk is reporting that a Patch has failed in the Scheduler, the first point of call is to check your Scheduled Job configuration. Using the recommended Scheduled Job configuration highlighted in an earlier section, you should not encounter a configuration issue and it would be down to the Device itself.

For a bit more detail, the Naverisk agent does not install updates. For Windows devices, the agent communicates with the Microsoft Windows Update Agent and tells it what updates to install. On Linux devices, the agent issues the appropriate shell commands to download and install the updates eg apt-get update.

Any patching-related issues are caused by an issue with the Microsoft Windows Update Agent encountering issues and failing to check or install updates. To verify this, check the Windowsupdate.log file located in the C:\Windows directory. These errors can then be searched to find a resolution.

As an example, here is an excerpt from the Microsoft generated Windowsupdate.log file:

Running a search on this error has brought up the below Microsoft Technet link:

This error indicates an issue with the Windows Update Agent not being able to communicate with the Microsoft servers to retrieve a list of Windows Updates. In the particular example above it was found that the machine had a proxy set on the Device which caused an issue with communication.

5.1 Installed updated information in Windows 10

Windows 10 displays the patching in two locations. The Installed update information is displayed in the Software tab and the update history information is displayed in the Patch management tab. These two are not always the same.

If you continue to experience issues after resolving the issues found in the Windowsupdate.log file and checking your Scheduled Job, please contact support@naverisk.com for further assistance.

Did this answer your question?