White Papers

Windows Driver Updates with OpenManage Enterprise 3.4 | 434
1.3 Navigating the OS driver update workflow
The user workflow for OS driver update is described in this section.
1.3.1 Using the compliance report
For ease of use and familiar workflow for users, the OS driver update workflow has been kept almost identical
to the firmware update workflow.
1. Create a catalog in OME by either pointing to Dell online or by specifying a catalog on a network
share (catalog created manually / using DRM). The user can specify if the catalog is manually
refreshed or automatically refreshed periodically.
2. Create a baseline by choosing a catalog and a set of devices or group of devices to associate with
that catalog. This causes a compliance evaluation to run. The compliance evaluation compares the
software inventory collected for the devices in that baseline, against the versions specified in the
catalog.
In versions prior to OME 3.4, the software inventory only includes the Firmware component inventory.
With OME 3.4, it also includes the OS driver inventory for applicable systems. The compliance report
displays both Firmware and OS driver compliance.
The “Advanced Filters” for compliance reports has an additional filter option for “Component Type”
with values: All, Firmware, Drivers. The default option for the “Component Type” filter is All. If an OS
driver update requires a host reboot, the “Reboot required” field for the appropriate driver update is
true.
The following screenshots show an online catalog, a baseline targeting a mix of servers (discovered via
iDRACs and discovered via Windows OS) and the resultant compliance report.
Creating online catalog