Deployment History

Deployment History provides a way to view the status of recent deployment operations to your devices. One of the biggest benefits of Deployment History is that it allows you to zero in on exceptions that may have occurred during patch deployments and quickly troubleshoot any issues. This is extremely important, as it enables you to quickly identify potential problems before they become major issues in your environment.

Deployment History is accessed from the main menu by selecting Patch Management > Deployment History.

Device Summary

The grid contains a list of all patches that have been deployed by the Ivanti Neurons Cloud or by an on-premise solution. Information within the grid is kept for six months before being automatically deleted. The Column Chooser icon Column set button (located just to the left of the Search box) enables you to specify which of the following columns appear in the grid:

  • Id and Advisory name: The id and name of the advisory. You can click the Id or advisory name to view the patch details page in Patch Intelligence.
  • Patch name: The name of the patch deployed to the device. You can click the patch name to view the patch information page in Patch Intelligence.
  • Platform: The type of operating system used on the device. Supported operating systems are Windows, macOS, and Linux.
  • Device name: The name of the device. You can click the name to view the Device Details page.
  • Policy: The agent policy to which the device is currently assigned. You can click the name to view the policy configuration.
  • Status: Shows the last reported state of the deployment. Possible values are:

    Use the Status column to locate problems and take prioritized action.

    • Not Started: The patch deployment operation has not yet started.
    • In Progress: The patch deployment operation is currently in progress.
    • Pending Reboot: The patch has been deployed, but a reboot of the device is still needed to complete the operation.
    • Success: The patch has been successfully deployed to the device.
    • Failed: The patch deployment operation has failed.
  • Patch result: Provides additional context to the deployment status. You can click on a code value to learn more about the code. Common return codes include:
    • Access Denied: Access is denied.
    • Error Disk Full: There is not enough space on the disk.
    • File Not Found: The system cannot find the specified file.
    • Install Failure: Fatal error during installation.
    • Install Language Unsupported: The language of the installation package is not supported by your system.
    • Open Failed: The system cannot open the device or specified file.
    • Patch Target Not Found: The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
    • Success: The operation successfully completed.
    • Success, Reboot Required: The requested operation is successful. Changes will not be effective until the system is rebooted.
  • Deployment date: The date and time the patch deployment began on the device.
  • Elapsed time: The time it took for the patch to be deployed to the device.
  • KB number: The knowledge base number. You can click the number to view the patch details page in Patch Intelligence.
  • Patch release date: The date the patch was released.
  • Deployment configuration: The patch configuration that was assigned when deployment happened. You can click the name to view the Patch configuration page.

Filter, Sort, Search and Export

Toggles on and off the Smart Filters area directly above the table. Enables you to see the filters that are currently applied to the table.

Information displayed within the table can be easily filtered to narrow the focus to only those deployment entries of interest. One way to do this is by using the Smart Filter. The Smart Filter contains several default filters. You can also define your own custom filters.

Default Filters

The Smart Filter contains several default filters. Default filters cannot be modified or deleted. The default filters include the following:

  • In Progress More Than 1 Day: Only those patches whose deployments were started more than one day ago are displayed.

Custom Filters

You can create your own custom filters. This is a powerful tool that enables you to specify exactly which entries you want displayed. Each custom filter is comprised of one or more rules. You can define as many rules in a filter as needed.

To create a new filter:

  1. Click Filters.
    The Smart Filter definition area is displayed above the table.
  2. Filter the table to a defined set of devices.
    Do this using the column filters and any existing Smart Filters.
  3. Select Smart filters > Add new smart filter from current.
    The new filter is created based on the filtering criteria used in the current table.
  4. Type a descriptive name for the filter.
  5. Click Add filter.

To delete a smart filter select Smart filters, from the drop-down menu select Delete existing smart filter, from the list select the filter you want to delete. On the confirmation dialog select Delete to remove the filter from the saved list.

Select the sort iconup arrow and down arrow to indicate the sort optionin any column header to sort into ascending (Ascending icon) or descending (Descending icon) order. To remove the sorting, right-click the column header and select Clear Sorting from the context menu.

Use the Search field to enter a keyword; the list will then only show patches that contain the keyword. The keyword is matched to any case-insensitive text found from within all of the patches, for example; CVE numbers, patch names, blue screen, and so on.

Example search use cases:

  • As a security engineer, I want to supply a CVE to understand what patch I need to have my IT Ops team apply to mitigate the vulnerability. The searching functionality can be an asset to both the Security and Ops teams by allowing them to search for CVEs and see which patches are required.
  • As a support technician, I want to know whether a patch is available to fix an issue with PST corruption in Outlook 2016 occurring in conjunction with error 0x80040119. The ability to search benefits the support staff who can search for symptoms or issues around a particular patch.

To remove a search filter, click the clear filters iconfunnel with a cross to indicate clear any applied filters.

Enables you to export the contents of the table to a CSV file. You can choose to export all items in the table or just selected items.

The CSV file is created using ISO standards and is stored in your local Downloads folder. If you use Excel to view the file, the data can be converted to the locale of the device so that it can be viewed in a more human-readable format.

Any sorting or filtering applied to the patches will be retained in the exported output. All columns will be included regardless of what has been selected in the Column Chooser.

Select the first column check box for the patches you want to export. Alternatively, select the check box in the header cell to select all patches.

Click Export to create the CSV file.

Related topics

Patch Management Overview

Endpoint Vulnerability

Patch Intelligence

Patch Settings