Universal Imaging Utility: Discovery Tool
The Universal Imaging Utility comes with a small program that can scan devices and extract drivers. This can be useful for devices that are not included in the standard driver database. It can be downloaded from the download section on UIU’s website.
Running the Tool
Once you download and extract the Discovery Tool, be sure to modify the INI file and add your license key. This will make it so that you do not have to type it in every time you execute the program. Also, run the program from an open command line interface, not directly by clicking on the EXE. This will allow you to see the output of the program.
If you run the program without any parameters, it performs an analysis on the system. This analysis will give you a nice HTML file of missing drivers. It will also break it down by OS, no matter what OS is installed on the system. Here is an example of the output:
As you can probably guess, I ran this in a VM for this demonstration. You can also see that the drivers that are missing are considered “non-critical”. The distinction is made based on whether or not the driver is required for the system to boot. If it’s required, the driver is marked as critical, if not, it’s considered non-critical. You must read this report carefully, as it says that the missing drivers are not missing from the machine, but from the UIU database.
Import Drivers
When you run the analysis, the Discovery Tool will output the results HTML file, as well as a file with the extension .uiudt. This file can be used to create a custom repository. This file contains the drivers that are missing from the UIU database. I would suggest creating another package in SCCM and storing all of these files in that package. When you add your UIU line to your task sequence, select your custom package on the “Customer Driver Package” line.
Now, when you execute your task sequence, it will install drivers from the UIU database, as well as your custom repository.
