Skip to main content

Latest Installed Cumulative Update

Purpose

The solution audits Windows 10 and 11 computers to verify the latest installed Cumulative Update. It includes an Autofix option that automatically attempts to install the latest available CU if no update has been installed within the specified number of days.

Associated Content

Auditing

ContentTypeFunction
Script - Get Latest Installed Cumulative UpdateScriptFetches the data from the machine.
Dataview - Latest Installed Cumulative UpdateDataviewDisplays the data fetched by the script.
Internal Monitor - Execute Script - Get Latest Installed Cumulative UpdateInternal MonitorDetects machines where the script hasn't been executed within the last 7 days.
△ Custom - Execute Script - Get Latest Installed Cumulative UpdateAlert TemplateExecutes the script upon the machines detected by the internal monitor.

Automation

ContentTypeFunction
Internal Monitor - Last Cumulative Update > X Days agoInternal MonitorDetects computers that haven't received a Cumulative Update installation within the past 75(Default) days, excluding End-of-Life (EOL) machines.
Script - Out of Date Cumulative Updates [Autofix]*Autofix ScriptInitiates the installation of the latest available Cumulative Update.
△ Custom - Autofix - Out of Date Cumulative UpdatesAlert TemplateExecutes the Autofix script upon the machines detected by the internal monitor.

Other

ContentTypeFunction
Custom Table - pvl_win_latest_installed_cuCustom TableStores the data fetched by the Script - Get Latest Installed Cumulative Update script.
Script - MySQL - Table - Create (plugin_proval_windows_os_support)ScriptInserts the latest version of the plugin_proval_windows_os_support custom table.
Custom Table - plugin_proval_windows_os_supportCustom TableStores Windows operating systems support end date, build number, and their respective release if any. The table should be updated to the latest version to use this solution at its full potential. The custom table can be updated by the Script - MySQL - Table - Create (plugin_proval_windows_os_support) script.

Implementation

1.

Import the following scripts from the ProSync plugin:

2.

Import the following internal monitors from the ProSync plugin:

3.

Import the Dataview - Latest Installed Cumulative Update dataview from the ProSync plugin.

4.

Import the following alert templates from the ProSync plugin:

  • △ Custom - Execute Script - Get Latest Installed Cumulative Update
  • △ Custom - Autofix - Out of Date Cumulative Updates
  • △ Custom - Autofix - Ticket Creation Computer

5.

Reload the System Cache.

Reload the System Cache

6.

Execute the Get Latest Installed Cumulative Update script against a couple of online Windows 10/11 computers and validate the data in the Latest Installed Cumulative Update dataview.

7.

Configure the Auditing section of the solution as follows:

Autofix

1.

  • Execute the Out of Date Cumulative Updates [Autofix]* script against a Windows computer with the script parameter Set_Environment configured as 1. This action will import the necessary System Properties required for solution management.

Execute Autofix Script

  • Configure the necessary values within the system properties.
    • Out_of_Date_CU-EmailAlerts: Configure this system property to 1 to activate Email Alerts in conjunction with the tickets.
    • Out_of_Date_CU-Autofix_for_Servers: Assign a value of 1 to this system property to enable Autofix for servers; by default, the script will only generate a ticket for servers.
    • Out_of_Date_CU-Disable_Autofix_for_Workstations: Assign a value of 1 to this system property to Disable Autofix for workstations.

2.

Configure the Autofix section of the solution as follows:

Ticket Only

1.

Configure the Autofix section of the solution as follows:

FAQ

Q: The Dataview shows this machine is online currently but has not updated its inventory in well over 10 days, why?
A: The monitor is set up to run only against machines that are not EOL or recently EOL (within 30 days). If the machine is not EOL currently, check to make sure the monitor is set up to run against the group that the machine is in.