Driver Injection - Need help
-
Guys,
I am trying to setup a FOG Server for our org (which I have done) but I am so confused on the driver injection for multiple types of hardware models. Can someone lead me in the right direction? I am new to the whole unattend.xml files and driver injection.
I have seen some of the forums here but still haven’t been able to get it straight.
We are running Lenovo and Dell laptops and desktops and all Windows 10 64bit.
-David
-
I can get you started with the structure you need to setup. Let me get the tutorial link then I can discuss a bit more.
-
This is from 2017 but its still relevent today. I should update just so it doesn’t confuse people thinking well its 3 years old it can’t still work.
Driver injection happens in 2 parts. The first part is a feature of FOG called a post install script. These are bash (linux scripts) that gets called just after FOG deploys the image to the target computer and just before FOG reboots the computer at the end of imaging.
Using these scripts we check the model number of the computer then copy over the right drivers to a common location on the target computer. That is where the FOG world stops.
In the windows world we add a command to the windows standard batch file that gets run at the end of OOBE and before the first login pane appears. This file is called setupcomplete.cmd. In this file we are going to add a command that calls the windows pnputil.exe program and point it to the directory where FOG dropped the drivers.
pnputil.exe /add-driver "C:\Drivers\*.inf" /subdirs /installThat pnputil program will search all sub-directories in c:\drivers looking for inf files to install. That program will also replace any windows generic drivers with hardware specific drivers.
I use a modified version of the script in the tutorial to support 15 models of Dells with one base image. Those post install scripts can also be used to update the unattend.xml file with (FOG) run time settings. I don’t use the fog client on my campus, but I use a post install script to supply the system name and target OU to the unattend.xml file and then let the target computer name itself and connect to AD in the proper OU.
