torpedor, that is perfect! The problem that we have right now is that the Intel USB 3 device is "hidden" behind the USB 3 Root Hub, so it doesn't always show up correctly in WinPE. When 9.5 SP2 comes out the solution will be to re-run HII in Windows. In the meantime what you did is perfect!
peter.wood,
For the fingerprint driver I would recommend running HiiClient /preview from within Windows on one of the affected devices. This will create a log file called HiiPreview.log and will show all the drivers that will be installed and whether they were auto-detected or manually assigned. Obviously all software package drivers are manually assigned. Make sure that it shows up there as something that will run. If it is showing up that it should run then make a template that just does HII within windows and gather the hiiclient log and attach it here (or open a support ticket to reach our support group directly and they can help you with this).
For the USB 3 driver there are a couple things I'd look at. Since it is downloading correctly it seems the detection is working how you'd like. If it won't install that means either Windows doesn't like the driver for that device (ie, it's the wrong driver because it's a slightly different USB controller than you expected) or there is a problem with the driver (ie, there is a file missing or something along those lines). The easiest way to troubleshoot both scenarios is to go into device manager on an affected machine and try to manually install the driver. Choose the option to browse on your filesystem and go to C:\Windows\LDDriverStore and make sure it's going to check all subfolders. It will do 1 of 3 things:
1 - Say it couldn't find a driver. This indicates it's the wrong driver and you'll need to find the correct driver.
2 - Say it found a driver, but then give an error saying it couldn't install it. This is likely a missing file. If this is the case there are some Windows logs you can look into and find out what's really wrong. I can't remember the process off the top of my head, so we'll cross that bridge when we get there. As for the LANDesk side this could indicate that a required file is not being downloaded which is either an HIIClient problem or something like an IIS setting that is filtering certain extensions, etc. This whole scenario would require a bit more digging to find the actual underlying problem.
3 - Say it found a driver and then successfully install it. This scenario is very unlikely because we do one command that installs all the drivers in the LDDriverStore and the rest seem to work. It's a standard Microsoft tool that does the actual install for us, and I've never had it selectively fail without good reason. I really think 1 or 2 is what we'll find.
Let me know what you find out with the HiiClient /preview stuff for the fingerprint scanner and the testing you do for the USB3.
Thanks!