FOG Post install script for Win Driver injection

  • Moderator


    First I have to say this article contains the results of many brilliant people and is not my content. I’m only assembling this information into a consistent document instead of spread around buried in posts and responses. My intent is to not dig into the details behind the scripts or how to tweak them for your needs. You can read the links below to figure out why things are being done the way they are. I wanted to create a tutorial that was as close to a cut and paste to get driver injection going in your environment. Now I will primarily focus on Dell hardware for the main reason that Dell does supply driver archive files (known as .CABs) that can be downloaded and extracted quickly to create the driver structure. I’m sure that HP, Lenovo, and others have similar driver packs.

    You can download the Dell driver cabs for your hardware from here:

    Reference links:

  • This post is deleted!

  • Moderator

    @Jonathan-Cool No problem on the bad english. I’m a native english speaker, and I speak it bad too…

    There are a few threads for setting up driver injection using a postinstall script. The thing you must remember if you go this path is that the postinstall scripts run under linux as a bash shell script and not windows. So there are somethings you can not do like DISM injection.

    There is a second requirement for this process to work. Your drivers must be in inf format and not built into a .exe installer. All of the Dell and most of the Lenovo drivers are in INF format. I can’t speak for the HP and their drivers.

    The postinstall scripts can work for all models the post install script will first check the manufacturer of the hardware then check the model number of the hardware to identify what drivers are needed.

    I wrote a tutorial (in addition to this thread) for this process.

    Also Lee wrote an excellent that takes a slightly different approach too.

  • Moderator

    @Jonathan-Cool Postdownloadscripts are up to the user to implement correctly, the system exists in FOG and this thread talks about using that system with a community created script.

    It’s easily the most convenient if you have a lot of the same models and it doesn’t change all the time.

  • Hello,
    (french user, sorry for my bad english … :( )
    Sorry for the question (the post is quite old) but i’m lost to choose the best solution for Driver Injection after image Deploy.

    In my environment, we have HP, DELL, Lenevo computer (laptop, desktop).

    What is the best way ? postdowloadscript included in Fog ? Or this way ? Or … it’s “depend on” ?

    Many thanks :)
    Have a nice day.

  • Moderator

    @Jamaal I can say for my organization, I use MDT to update the registry entry during the reference image build. That always has worked for me.

    The other way people have done it was via the fog.drivers script here (look at the very bottom)

    the fog.driver script route appears to work, but I’ve never used that route. It was easier for me to just create the mdt task to update the registry key, plus I could/do validate the reference image matches the our design standard before image capture, so I need all of the bits to be in place for validation.

    What is important (for the registry key) is to have the c:\drivers path first then the c:\windows\inf directory. You want OOBE to search for the model specific driver before it uses the windows built in driver (if both exist).

  • @george1421 George, 2 more questions as I’m starting to get the hang of MDT 2013 and fog. How do I put in the task to change the registry to put c:\drivers for where Fog will drop the drivers for the Lenovo machines? And the other thing that’s giving me an issue, where else in the fog.drivers script do I edit c:\drivers?

    Other than that, I’m feeling confident I’ll be able to deploy our fleet.

  • @Jamaal said in FOG Post install script for Win Driver injection:

    @george1421 George, I think I got the name correct for the Lenovo, getting further than before. I remember I had the name structure as ThinkPad T560 under the drivers folder, but getting stuck at Preparing Drivers… in progress. In the task menu on the web, it only shows like 1% and not moving. Any idea on why that’s happening?

    I think I see what is the issue. Just that the screen moves too fast and said no such file or directory and it reboots.

  • @george1421 George, I think I got the name correct for the Lenovo, getting further than before. I remember I had the name structure as ThinkPad T560 under the drivers folder, but getting stuck at Preparing Drivers… in progress. In the task menu on the web, it only shows like 1% and not moving. Any idea on why that’s happening?

  • Moderator

    @Jamaal You can join the machine to the domain by:

    1. Have the unattend.xml file join the computer to the domain
    2. Have the FOG Client connect the computer to the domain
    3. Create a script that is executed by the setupcomplete.cmd file

    I use the first option because based on the image used, type of computer, site deployed to, our post install script will choose the correct OU and update the unattend.xml file accordingly. That is something the fog client isn’t designed to do.

    Many people use option 2.

    As for why your setup is not connecting to the domain. Is the network driver being loaded so the client can reach the domain controller? If I had a system that wouldn’t connect to the domain, I would log into it and then manually connect it to the domain. Be sure you use the user ID and password you defined in fog, that user account must have computer add rights. The other thing may be that you are defining a destination OU that doesn’t exist? Also you may be able to glean some information by looking at your DC’s security log to see if its a permission issue.

  • @george1421 Ok, I’ll try that tomorrow when I go back to work. Thanks for the info, but can you tell me about the joining of the domain? or maybe it’s best if I use a script to just join it?

  • Moderator

    @Jamaal Just for clarity this tutorial was intended for Dells only.

    With that said it can work for Lenovos or other models. I can tell you that lenovos (more precisely) Dell store the system name in a different location than other computer manufacturers. So your fog post download script will need to look in a different location that my scripts indicate (because they are Dell centric).

    Since you are a Windows convert, you MUST remember that case IS important to linux. So just pay attention when creating file paths.

    The built in fog.postdownload script is just a shell script (it doesn’t do anything right out of the box). It is up to you as the FOG admin to add content to that script. So in short yes you will need to update that script as indicated.

    So for the Dell computers we have to use this smbios key to pick up the system name using dmidecode
    dmidecode -s system-product-name

    For the other manufacturer (I believe lenovo too) you have to use this key
    dmidecode -s baseboard-product-name

    One manufacture stores the name in the system structure and one in the baseboard structure. Both are correct just a pain if you have a mixed fleet. In out production fog script we use another dmidecode key to find the manufacturer dmidecode -s baseboard-manufacturer and then use a case statement to query the right key for the system name.

    What I might do until I was comfortable with the hardware setup would be to schedule a debug capture of the new and untested hardware. A debug capture will drop you to a command prompt on the target hardware when you pxe boot it. Once at the command prompt on the FOS engine (the linux OS that boots on the target hardware) run the dmidecode command and inspect what get returned. This code returned must match exactly the driver parent folder in the /images/drivers/XXXXX

  • Hello, George,

    1st off, thanks for all of your documentation on this. I’m getting further than before in my deployment.
    I’m however stuck on a few things, so I’ll provide as much info as you need.
    Fog server running on Ubuntu 16.04 server
    Fog server version: 1.3.0-RC-10.

    So here are the machines and other things we have in our environment:
    laptops: Lenovo ThinkPad T540p, ThinkPad T560, Lenovo ThinkPad T530, and other lower models.
    Desktops: Lenovo ThinkCentre M800

    I used MDT 2013 Update 2 as you were saying about MDT and I took an image on our VMware and deployed the image on a ThinkPad T560 from the fog server I have on our VMware. On my fog server, there is already an image folder, so I created under there drivers/ThinkPad T560/win7/x64. 0_1482360759122_Lenovo.docx

    Now do I need to create another subfolder under the root like images 2 or something like that? Sorry, I’m a Windows guy and still getting used to Linux. I also replaced the fog.postdownload with what you have in this forum and ran that chmod command and looked like it took it.

    When I deploy the image to the T560, it 1st gave me an error with the fog.driver script from in the forum that failed to load the driver, had it just Thinkpad T560, had to do ThinkPad T560, then it would get stuck on in process during the driver loading and when it was preparing it for the first time, I would get errors during syspre that it had errors, forgot the exact error, so I would restart it and get an error windows rebooted and reinstalling Windows during the sysprep.

    Can you tell me what I’m doing wrong? also I’m unable to join the machine to my test domain. I did the hostnamechanger and did the encrypt, but still won’t join my test domain, the account is not a domain admin, but I gave it delegate to the test OU I created. Does it need the hostnamechanger for 1.3.0? I verified the options in AD on the console are checked off.

    Look at the Word attachment I’ve attached.

  • Thanks for all of this…great help while I’m making a windows 10 image. I do have 1 question. When you say this script will not work and you need to add this to the unattend file.

    [moderator note] The content of this question has been forked to this thread since it went a bit beyond the scope of this tutorial:

  • Moderator

    @Lee-Rowlett said in FOG Post install script for Win Driver injection:

    @george1421 nice write-up - think this needs updating to be inline with hostinfo.php variables?

    Thank you for your kind words.

    Yes, looking over the code its a bit dated. There are a few things that while they work, could use a fixup because I don’t think they work as well as it should.

    Possibly include setting the host name with this snippet. So they host name can be anything and sed will just swap it out. In the one I wrote for my business it is setup for global deployments. It will identify the local subnet where its being installed and update the timezone, system mui language and keyboard settings for the local region. But the point is they all use a variant of the sed script below.

    sed -i -e "s#<ComputerName>\([^<][^<]*\)</ComputerName>#<ComputerName>$hostname</ComputerName>#gi" $unatendfile 


  • Developer

    @george1421 said in FOG Post install script for Win Driver injection:

    This script can be used to update files on the target computer. In this case we’ll use it to update the unattend.xml file with install time data like host name, connect to AD or what ever you need. I can say if you use the FOG client to do this stuff, then this script isn’t really needed. But its here to show you what’s possible.

    hostadpwd="ADPASSWDHERRE"; #only downside to this method- this is the plain ad password
    unattends=$(find /ntfs/ -iname "unattend.xml")
    for unattend in $unattends
        [[! -f $unattend]] && return
        dots "Preparing Sysprep File"
        #rm -f /ntfs/Windows/System32/sysprep/unattend.xml >/dev/null 2>&1
        #if [[! $? -eq 0]]; then
            #echo "Failed"
            #handleError "Failed to remove original unattend file"
        echo "Done"
        dots "Writing Computer Name to $unattend"
        sed -i "/ComputerName/s/*/$hostname/g" $unattend >/dev/null 2>&1
        if [[! $? -eq 0]]; then
            echo "Failed"
            handleError "Failed to update originating unattend file"
        echo "Done"
        echo "ComputerName set to $hostname in $unattend"
        [[-z $addomain]] && continue
        dots "Set PC to join the domain"
        sed -i "/<JoinWorkgroup>/d" $unattend >/dev/null 2>&1
        if [[! $? -eq 0]]; then
            echo "Failed"
            handleError "Failed to remove the Workgroup setter"
        sed -i \
            -e "s|<Password></Password>|<Password>${hostadpwd}</Password>|g" \
            -e "s|<Username></Username>|<Username>${addomain}\\\\${aduser}</Username>|g" \
            -e "s|<MachineObjectOU></MachineObjectOU>|<MachineObjectOU>${adou}</MachineObjectOU>|g" \
            -e "s|<JoinDomain></JoinDomain>|<JoinDomain>${addomain}</JoinDomain>|g" $unattend >/dev/null 2>&1
        if [[! $? -eq 0]]; then
            echo "Failed"
            handleError "Failed to update user, pass, ou, and domain setter"
        echo "Done"

    @george1421 nice write-up - think this needs updating to be inline with hostinfo.php variables?

  • Moderator

    @Tom-Elliott I think having more than one repo for community scripts is a bad idea. It’s just scripts. It’s not jumbled together. It’s well organized, every contribution has a readme. The entire idea was to put scripts into one place.

  • Senior Developer

    fog-community-scripts I think should be their own thing independent of “post download scripts”

    Maybe we could get a postdownload scripts repo in a similar fashion though?

  • Moderator

    @Joe-Schmitt are these scripts something we can add to the fog community scripts repo? I didn’t originally write them.

  • Moderator


    This script is called by the FOS engine just after the image has been pushed to the target computer. It is up to the FOG Admin to decide what to do in this script and what other scripts to call. This script will replace the default fog.postinstall script. Don’t forget if you replace this file you must change the file mode to 755 using the following linux command chmod 755 fog.postdownload
    This script will call 3 additional scripts that will do a bit more than copying the drivers to the target system. You can include or exclude these scripts based on your need. This (fog.postinstall)) script will setup the foundation functions needed by the other scripts.

    I’ll include an attachment at the end of this post to help speed up script deployment.

    . /usr/share/fog/lib/
    [[ -z $postdownpath ]] && postdownpath="/images/postdownloadscripts/"
    case $osid in
            [[ ! -d /ntfs ]] && mkdir -p /ntfs
            if [[ -z $hd ]]; then
                handleError "Could not find hdd to use"
            getPartitions $hd
            for part in $parts; do
                umount /ntfs >/dev/null 2>&1
                fsTypeSetting "$part"
                case $fstype in
                        dots "Testing partition $part"
                        ntfs-3g -o force,rw $part /ntfs
                        if [[ ! $ntfsstatus -eq 0 ]]; then
                            echo "Skipped"
                        if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
                            echo "Not found"
                            umount /ntfs >/dev/null 2>&1
                        echo "Success"
                        echo " * Partition $part not NTFS filesystem"
            if [[ ! $ntfsstatus -eq 0 ]]; then
                echo "Failed"
                handleError "Failed to mount $part ($0)\n    Args: $*"
            echo "Done"
            . ${postdownpath}fog.log
            . ${postdownpath}fog.drivers
            . ${postdownpath}
            umount /ntfs
            echo "Non-Windows Deployment"


Log in to reply





Looks like your connection to FOG Project was lost, please wait while we try to reconnect.