Thanks for the response. I will test the HIICLient in preview mode, but I don't think HII will do what we want.
We use manufacturer's driver packs and the issue isn't with detection of the hardware components in HII. The issue is deciding how to run the driver setup file to complement the driver pack. We do this because the setup will install the software that interacts with the driver (i.e. audio control panel for audio drivers, 3d drive guard notification for 3d drive guard drivers, etc.).
Correct me if I'm wrong on my assumptions, but if I were to use HII and driver package assignment, I would need to do the following:
1. Create a distribution package for the setup install and assign it to the device ID.
2. Rip out the driver from the driver pack, so no drivers are installed during detection, otherwise LANDesk will see that it already has a driver and won't run the package assigned.
Having the granularity of assigning packages to device IDs sounds like a good idea, but it just seems like unnecessary. Assigning the package to the hardware model would work just as well, however I can't find a way to do this without going the route of package detection (using queries).