Issues using driver path in sysprep - Windows 10
-
In our district we have multiple hardware releases, so we try to make our images general enough to work across multiple hardwares. With Windows 7 all we used to have to do is add in the sysprep unattended file the driver path, and it would then brows to the sub folders to find drivers.
With Windows 10 I am not experiencing the same issue. After running Generalize on my finalized image, and then capturing it to FOG, I then deploy to stations, and am finding newer hardware that I have added the drivers to this path “C:\Drivers” are not automatically used, so I have to manually correct each of these hardware items on these devices.
It may be that this method just doesnt work any more as I am fairly unfamiliar with the changes in sysprep of Windows 10, but I also was curious if this is even the best way to add drivers to the images.
Any advice appreciated on assisting me in making my generic images that I am building on one hardware type work across the multiple hardware platforms.
Thank You
-
@hauser said in Issues using driver path in sysprep - Windows 10:
It may be that this method just doesnt work any more as I am fairly unfamiliar with the changes in sysprep of Windows 10, but I also was curious if this is even the best way to add drivers to the images.
You are rigth, M$ broke this handy feature of defining where the drivers are. What I’ve found to be reliable is using the pnputil command in the setupcomplete.cmd batch file to load in any remaining hardware specific drivers. So for my campus I have 2 golden images (one bios and one uefi) for 15 different hardware models, where the hardware specific drives are transferred to the target computer using a post install script, then I run the pnputil program to load the drivers.
