Usage guide: Driver compliance

Introduction

This library pack will empower you with the actionable visibility you need to maintain your device landscape’s driver compliance. It will help you avoid compatibility, security, and hardware functionality issues that result in incidents and tickets for your service desk.

Please keep in mind this is a guide and represents just some of the potential insight and actions you can take. There are many use cases and specific troubleshooting scenarios that you might uncover in your environment.

Ensure your library pack is properly configured by following the steps highlighted in its configuration guide:

Configuration guide: Driver compliance

Pack structure

Visibility

The "Driver Compliance - Dell", "Driver Compliance - HP" and "Driver Compliance - Lenovo" live dashboards serve as the initial components of this library pack. They offer insights into the pending driver, firmware, and BIOS updates for HP, Dell and/or Lenovo devices, as reported by the "HP Image Assistant", "Dell Update Package" and/or “Lenovo System Update“ driver management software installed on the devices.

Advanced troubleshooting and remediation

For more in-depth investigations, you can rely on the results of specific data-gathering remote actions.

Get Dell pending BIOS firmware and driver updates : Retrieves the current status of the Dell driver, BIOS, and firmware updates. It identifies the need for an update in any of these three categories and classifies the updates based on their importance as critical, security, recommended, or optional.
Get HP pending BIOS firmware and driver updates: Retrieves the current status of the HP driver, BIOS, and firmware updates. It identifies the need for an update in any of these three categories and classifies the updates based on their importance as critical, recommended, or routine.
Get Lenovo pending BIOS firmware and driver updates: Retrieves the current status of the Lenovo driver, BIOS, and firmware updates. It identifies the need for an update in any of these three categories and classifies the updates based on their importance as critical, recommended, or optional.

These data-gathering remote actions are used to populate the live dashboard and should already be scheduled. You can query the results by investigating KPIs from the Live dashboard or from your own investigations.

When a device needs BIOS or firmware updates, it typically necessitates direct service intervention. For driver updates, the following remote actions should be used:

Invoke install Dell pending driver updates: Automatically install drivers on Dell devices, utilizing the vendor-specific tool to identify the most suitable driver. With this remote action, driver updates can be performed silently, without displaying any utility interface to the employee.
Invoke install HP pending driver updates: Automatically install drivers on HP devices, utilizing the vendor-specific tool to identify the most suitable driver. With this remote action, driver updates can be performed silently, without displaying any utility interface to the employee.
Invoke install Lenovo pending driver updates: Automatically install drivers on Lenovo devices, utilizing the vendor-specific tool to identify the most suitable driver. With this remote action, driver updates can be performed silently, without displaying any utility interface to the employee.

Use Cases

Identify areas of improvement

Each hardware manufacturer has a dedicated dashboard, organized similarly into three parts:

Devices requiring immediate action - highlighting devices that should ideally be addressed without delay.
Devices requiring non-critical updates - where urgency is not immediately required.
Scan status - indicating devices that had a successful scan attempt for updates but completion was not possible.

Update pending drivers - Dell devices

The “Driver compliance - Dell” dashboard identifies Dell devices that require updates for drivers, BIOS, or firmware. In particular, devices that need driver updates can be managed using the “Invoke install Dell pending driver updates” remote action. The following KPI widgets can be utilized to identify and manage devices:

“Devices pending driver critical updates”
“Devices pending driver security updates”
“Devices pending driver recommended updates”
“Devices pending driver optional updates”

Update pending BIOS or firmware - Dell devices

For devices that require BIOS or firmware updates, the relevant KPIs can be used to create a list of these devices. This data can subsequently be utilized to initiate necessary service requests.

Update pending drivers - HP devices

The “Driver compliance - HP” dashboard identifies HP devices that require updates for drivers, BIOS, or firmware. In particular, devices that need driver updates can be managed using the “Invoke install HP pending driver updates” remote action. The following KPI widgets can be utilized to identify and manage devices:

“Devices pending driver critical updates”
“Devices pending driver recommended updates”
“Devices pending driver routine updates”

Update pending BIOS or firmware - HP devices

For devices that require BIOS or firmware updates, the relevant KPIs can be used to create a list of these devices. This data can subsequently be utilized to initiate necessary service requests.

Update pending drivers - Lenovo devices

The “Driver compliance - Lenovo” dashboard identifies Lenovo devices that require updates for drivers, BIOS, or firmware. In particular, devices that need driver updates can be managed using the “Invoke install Lenovo pending driver updates” remote action. The following KPI widgets can be utilized to identify and manage devices:

“Devices pending driver critical updates”
“Devices pending driver recommended updates”
“Devices pending driver optional updates”

Update pending BIOS or firmware - Lenovo devices

For devices that require BIOS or firmware updates, the relevant KPIs can be used to create a list of these devices. This data can subsequently be utilized to initiate necessary service requests.