I would check in your C:\windows\temp folder for any DISM logs or HII logs and review those. Also check your Unattend.xml and be sure that it also has a line in there for c:\WIndows\lddrivers.
Last resort is to put a long pause in just before CTOS in your deploy script to give you time to review the logs in X:\ldprovision for any clues.
I did look at the HII logs, and HII Preview, but in my eyes, everything seems to be fine there. I don't currently have enough knowledge to understand the contents of the DISM and CBS logs, so I have created a ticket with Landesk as I am at a loss here. I'll try and look up how to create a CTOS pause.
1 of 1 people found this helpful
I assume that SOME drivers are working but not all?
If so, consider that some items (like components in USB) do not show up until after another driver is loaded.
For example, the USB Root Hub is a component off of the USB 3.0 Host Controller, so until the Drivers are installed for the Host Controller, the system does not even know the Root Hub exists, that it why it is recommended to run a second HII in the System Configuration section, to hopefully catch the stragglers.
HII will only deploy drivers for what it detects, in my example the USB Root hub does NOT exist until AFTER the Host controller drivers are installed and in place. So in your second pass of HII the USB Root hub will be detected and loaded, (hopefully).
Sorry about not responding. Things have been a little busy here.
I have actually done what you described. An additional HII action has been added to the Sys Config portion, but that did not seem to change anything. The odd things I found was that one of the drivers I manually assigned (after a first provision test) actually no longer appears and is truly, 100% successfully installed. That would be the ACPI\INT33A0 (Intel Smart Connect Technology driver). The ethernet and WIFI drivers aren't an issue. Landesk's suggestion would be to only have 1 single action with HII during the Sys Config, which I believe I've done but can't recall at the moment. I am going to try that again today and see if that changes anything.
Any possibility that Data Analytics is involved, and it is normalizing/changing your model information, and as a result changing what needs to be "assigned" for the model in HII? The side effect might be that you would see possibly two different model descriptions in the pull down menu in HII for the model. This could even carry over to manufacturer as well, since there are normalizer rules for several fields of data including manufacturer and model.
Sometimes not all the drivers come down in the first HII pass during the Post-OS stage. I typically keep the 2nd HII action in the System Config stage (by default the two are created on a new deploy template) because it will typically get those it wasn't able to install before CTOS runs. Usually, it's just my USB 3.0 driver that doesn't like to install. I'm not sure exactly which ones you're missing, but when I have this problem, I try to assign the missing driver to a different hardware device, such as disk. That helps for most models, however I have one that still doesn't get its driver. For that one I made a quick software distribution package for it that we add to the provisioning template.
Hope that helps! Good luck!