> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/library-packs/security-and-compliance/driver-compliance/usage-guide_-driver-compliance.md). # Usage guide: Driver compliance {% hint style="warning" %} This page outlines various ways to use the pack, including use case examples. Administrators can refer to the [Configuration guide: Driver compliance](/platform/library-packs/security-and-compliance/driver-compliance/configuration-guide_-driver-compliance.md) to set up and customize the installed content. {% endhint %} The **Driver compliance monitoring** library pack provides actionable visibility to help maintain driver, firmware, and BIOS compliance across your device landscape. Use this pack to: * Prevent compatibility, security, and hardware issues caused by outdated drivers. * Monitor pending driver, firmware, and BIOS updates across Dell, HP, and Lenovo devices. * Identify devices that have not been scanned successfully. * Take action using vendor-specific remote actions and automation where supported. * Reduce manual remediation effort and service desk incidents. This pack includes three vendor-specific dashboards and preconfigured remote actions for detecting pending updates. It also includes an Automated driver compliance workflow that can automatically remediate pending critical driver updates for supported vendors. {% hint style="info" %} The dashboards support Dell, HP, and Lenovo devices. The automated workflow currently supports Dell and HP devices only. {% endhint %} ## Library pack uses Use the library pack content for the following purposes.
Visibility into Driver compliance The following [live dashboards](/platform/user-guide/live-dashboards.md) are the main visibility tools: * Driver compliance - Dell * Driver compliance - HP * Driver compliance - Lenovo Each dashboard provides a vendor-specific view of pending driver, BIOS, and firmware updates reported by the corresponding vendor tool: * Dell update tooling for Dell devices * HP Image Assistant for HP devices * Lenovo Thin Installer Utility for Lenovo devices Each dashboard helps you understand: * Devices with pending critical or security updates. * Devices with pending recommended, optional, or routine updates. * Device models contributing most to pending update exposure. * Devices that have not been scanned or have stale scan data. * Remote action scan health and execution status. Access the dashboards from **Live dashboards**.
Advanced troubleshooting and remediation Use the following data-gathering remote actions to retrieve update status and populate the dashboards: * Get Dell pending BIOS firmware and driver updates: Retrieves Dell update status and classifies pending updates as critical, security, recommended, or optional. * Get HP pending BIOS firmware and driver updates: Retrieves HP update status and classifies pending updates as critical, recommended, or routine. * Get Lenovo pending firmware BIOS and driver updates: Retrieves Lenovo update status and classifies pending updates by update type and severity. {% hint style="info" %} These data-gathering remote actions populate the live dashboard and should already be [scheduled](https://docs.nexthink.com/platform/user-guide/remote-actions/managing-remote-actions). You can query the results by [investigating KPIs from the Live dashboard](https://docs.nexthink.com/platform/latest/using-live-dashboards) or from [your own investigations](https://docs.nexthink.com/platform/latest/investigations). {% endhint %} To remediate driver updates remotely, use the vendor-specific execution remote actions where available: * Invoke install Dell pending driver updates * Invoke install HP pending driver updates For Dell and HP devices, the Automated driver compliance workflow can be used to automate remediation of pending critical driver updates. The workflow checks whether the device is Dell or HP, verifies whether critical driver updates are pending, and then runs the corresponding vendor-specific update remote action.
BIOS and firmware updates usually require a more controlled servicing process. Use the dashboards to identify affected devices, export or drill down into the device lists, and create the required service requests or endpoint management actions.
Review the use cases on this page to see relevant scenario applications. *** ## Use cases In addition to the relevant use cases covered below, you may uncover other troubleshooting scenarios specific to your environment. ### Identifying driver compliance exposure Use the vendor-specific dashboards to identify areas of improvement across your device estate. Each dashboard is organized around two main tabs. * Compliance overview: This shows the current update exposure and trend of compliant devices. * Admin: This shows whether remote actions and workflows are running successfully and reaching the expected devices. Start with the Compliance overview tab to understand whether there are devices with pending updates. Review critical or security updates first, then review recommended, optional, or routine updates. Then use the Admin tab to investigate whether the data is complete and reliable. If many devices are not scanned, resolve scan coverage issues before using the compliance data for reporting. ### Updating pending drivers - Dell devices Use the **Driver compliance - Dell** dashboard to identify Dell devices with pending driver updates.
Review the following areas: * Devices pending driver critical or security updates. * Devices pending driver recommended or optional updates. * Devices pending updates by model. * Dell update scan coverage and remote action execution results. To remediate Dell driver updates, run Invoke install Dell pending driver updates on affected devices. For automated remediation, use the Automated driver compliance workflow. For Dell devices, the workflow checks for pending critical driver updates and runs the Dell driver update remote action when critical driver updates are detected. ### Updating pending BIOS or firmware - Dell devices Use the **Driver compliance - Dell** dashboard to identify Dell devices with pending BIOS or firmware updates. Review the BIOS and firmware widgets to identify: * Devices pending BIOS critical or security updates. * Devices pending firmware critical or security updates. * Devices pending BIOS recommended or optional updates. * Devices pending firmware recommended or optional updates. * Device models with the largest update exposure. BIOS and firmware remediation typically requires a controlled servicing approach. Use drill-down results or exported device lists to create service requests or target the appropriate endpoint management process. ### Updating pending drivers - HP devices Use the **Driver compliance - HP** dashboard to identify HP devices with pending driver updates.
Review the following areas: * Devices pending driver critical updates. * Devices pending driver recommended updates. * Devices pending driver routine updates. * Devices pending updates by model. * HP scan coverage and remote action execution results. To remediate HP driver updates, run Invoke install HP pending driver updates on affected devices. For automated remediation, use the Automated driver compliance workflow. For HP devices, the workflow checks for pending critical driver updates and runs the HP driver update remote action when critical driver updates are detected. ### Updating pending BIOS or firmware - HP devices Use the **Driver compliance - HP** dashboard to identify HP devices with pending BIOS or firmware updates. Review the BIOS and firmware widgets to identify affected devices and models. Use the drill-down results or exported device lists to create service requests or target the appropriate endpoint management process. BIOS and firmware updates should be planned according to your organization’s servicing policy, maintenance windows, and restart requirements. ### Updating pending drivers - Lenovo devices Use the **Driver compliance - Lenovo** dashboard to identify Lenovo devices with pending driver updates.
Review the following areas: * Devices pending driver critical updates. * Devices pending driver security updates. * Devices pending driver recommended updates. * Devices pending driver optional updates. * Devices pending updates by model. * Lenovo scan coverage and remote action execution results. ### Updating pending BIOS or firmware - Lenovo devices Use the **Driver compliance - Lenovo** dashboard to identify Lenovo devices with pending BIOS or firmware updates. Review the BIOS and firmware widgets to identify affected devices and models. Use drill-down results or exported device lists to create service requests or target the appropriate endpoint management process. BIOS and firmware updates should be handled through your organization’s approved servicing process. ### Monitoring remote actions executions and workflow health Use the **Admin** tab in each dashboard to confirm that update detection and automation are working as expected. For remote action execution health, review: * Scan coverage. * Remote action execution results. * Devices not scanned or with stale scan data. * Device models with scan coverage gaps. For workflow health, review: * Workflow execution coverage. * Workflow outcomes. * Devices reached by the workflow. * Devices not reached by the workflow. The workflow health section is especially relevant for Dell and HP, because these are the vendors currently supported by the Automated driver compliance workflow. For Lenovo devices, use scan health and dashboard exposure data to support manual or external remediation processes. *** RELATED TOPICS * [Manage Live Dashboards](https://nexthink.gitbook.io/opd/user-guide/live-dashboards/managing-live-dashboards) * [Manage Remote Actions](https://nexthink.gitbook.io/opd/user-guide/remote-actions/managing-remote-actions) * [Manage Campaigns](https://nexthink.gitbook.io/opd/user-guide/campaigns/managing-campaigns) * [Configuration guide: Driver compliance](/platform/library-packs/security-and-compliance/driver-compliance/configuration-guide_-driver-compliance.md) for Nexthink administrartors --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nexthink.com/platform/library-packs/security-and-compliance/driver-compliance/usage-guide_-driver-compliance.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.