This content has been marked as final. Show 4 replies
HII will scan the .inf files of the drivers for matching data to assign them to the correct model.
Sometimes multiple drivers will match up with a model which causes HII to assign the "wrong" one.
Best Practice is to assign the drivers that are not automatically set up successfully.
Reference the following document regarding how to set up HII:
I'm resuming this topic because we have the same problem as Bob.
We followed the document you posted but the issue persist.
When the provisioning reach the HII step, it doesn't load the drivers assigned in the "HII Driver Management", it rescan ALL of the drivers contained in the drivers.db3 and choose from whatever model or even manufacturer it thinks is going to work with catastrophic results like BSOD.
I don't think there is a solution to this problem, I think this is a bug or an error in the design of the HII.
I recommend opening a ticket with support to troubleshoot why assigning drivers is not working.
I've recently worked with multiple admins through this process and it has worked every time provided there are no other issues.
1 of 1 people found this helpful
we already had a webex with Ivanti support...
They told us that what we are experiencing is the normal behaviour of HII and if we want it changed we have to open a request for it (3 to 6 months of developing?)
In the meantime we crafted our own TII (because we discovered this only now)