Hello!

I recommend following these guides.
https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection?page=1

https://forums.fogproject.org/topic/11012/resolution-to-inject-drivers-in-windows-10-sysprep/5
Have worked for all of my models so far.
And all i need to do is keep my driver model repo in check.

Here is another approach.
https://forums.fogproject.org/topic/9859/post-deployment-driver-installation-using-powershell-scripts

Hope this guides you in the right direction.

No volume license is one key that has many activations.

I’ve noticed that using the same OEM key on the same model and manufacturer has worked but you shouldn’t do it.

Here is link to check the OEM key and automate the activation.
https://blogs.technet.microsoft.com/in-teaching-others-we-teach-ourselves/2016/12/13/how-to-deploy-windows-10-with-a-oem-product-key-from-the-bios-with-microsoft-deployment-toolkit/

Hello!
so there has to be imaging task in place for the computer to start imaging. These tasks are managed from the FOG server.
Even If they manage to start pxe boot without there being a scheduled imaging task in place it will just load the “fog menu”.
The menu has the option “Deploy now” but you can have that password protected.

That’s how we have it set-up. My English is not the best hope it makes sense and answered your question.

Hey guys we can close this I solved it.

The drivers that i had extracted with 7-zip was incomplete and with errors.
Removed the folder and extracted the .cab with pea zip and it started working as normal again.

Don’t know why that made it work, but it did.

@quazz So I tried it on a different model a laptop latitude 7480. And it works great no issues.
It’s just the workstation that is having the issue.
I can’t see that it copied every thing except the “video” folder which appears to be 2.89 GB. In size.
I had to hand out the desktop and don’t have one to test it on.

I will update you next time I try it.

@quazz This is what I have. Followed the guide that George wrote.

#!/bin/bash
ceol=`tput el`;
manu=`dmidecode -s system-manufacturer`;
dots "Identifying hardware"
case $manu in
    [Ll][Ee][Nn][Oo][Vv][Oo])
        machine=$(dmidecode -s system-version)
        ;;
    *[Dd][Ee][Ll][Ll]*)
        machine=$(dmidecode -s system-product-name)
        ;;
    *I[Nn][Tt][Ee][Ll]*)
        # For the Intel NUC and intel mobo pick up the system type from the
        # baseboard product name
        machine=$(dmidecode -s baseboard-product-name)
        ;;
    *)
        # Technically, we can remove the Dell entry above as it is the same as this [default]
        machine=$(dmidecode -s system-product-name) 
        ;;
esac

# if the machine isn't identified then no need to continue with this script, just return to caller
if [[ -z $machine ]]; then 
    echo "Unable to identify the hardware for manufacturer ${manu}";
    debugPause;
    return;
fi 
echo "${machine} Identified";

# Removes Spaces in machine name, works better with path definitions

machine="${machine%"${machine##*[![:space:]]}"}";

dots "Verifying we've found the OS disk"
if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
    echo "! OS root Not found !";
    debugPause
    return;
fi
echo "Found";
        
dots "Verifying target Arch"
system64="/ntfs/Windows/SysWOW64/regedit.exe"
[[ ! -f $system64 ]] && arch="x86" || arch="x64"
echo "${arch} found";

debugPause

# set osn path names based on the osid set in the FOG WebGui
case $osid in
    5) osn="win7" ;;
    6) osn="win8" ;;
    7) osn="win8.1" ;;
    9) osn="win10" ;;
esac

dots "Preparing Drivers"
clientdriverpath="/ntfs/Drivers"
remotedriverpath="/images/drivers/$machine/$osn/$arch"

debugPause

if [[ ! -d "${remotedriverpath}" ]]; then
    echo "failed";
    echo " ! Driver package not found for ${machine}/$osn/$arch ! ";
    debugPause;
    return;
fi
echo "Ready";

debugPause

[[ ! -d $clientdriverpath ]] && mkdir -p "$clientdriverpath" >/dev/null 2>&1
echo -n "In Progress"

rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1

[[ ! $? -eq 0 ]] && handleError "Failed to download driver information for [$machine/$osn/$arch]"

debugPause

# the following code is only valid for Windows 7 operating systems since Windows 8 and beyond
# relies on the unattend.xml section to locate OEM drivers. If you are no longer deploying Win7
# you may exclude this section. 

regfile="/ntfs/Windows/System32/config/SOFTWARE"
key="\Microsoft\Windows\CurrentVersion\DevicePath"
devpath="%SystemRoot%\DRV;%SystemRoot%\inf;";
reged -e "$regfile" &>/dev/null <<EOFREG
ed $key
$devpath
q
y
EOFREG

@george1421 So checked the folder and it is missing some files on the target machine when copying.
Is there a timeout on the script that causes it to kill the transfer if it takes too long?

Well it doesn’t fail as you can see in the next picture pnputil is installing the drivers.
and the folder is on the C drive with no missing files.

“Well your “debug mode” picture explains why the task is not done”
It’s the copy drivers that fails the entire task to not complete?

So this is weird. It says Failed to download driver.
But it works as you can see in the next picture where it’s installing the drivers.
Still doesn’t mark the task as complete.

https://imgur.com/5WEjN1c
https://imgur.com/IDMD696

Hello!

I’m are having an issue where the images get’s pushed but the tasks never completes in the task view tab.
Causing the computer to get stuck in a reboot loop every time it boots in to windows.

https://imgur.com/a/2t54Wum

I am using postDL scripts for Driver injection.
I’m running FOG 1.5.4
Ubuntu 14.04.5 LTS

Hello!

I recommend following these guides.
https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection?page=1

https://forums.fogproject.org/topic/11012/resolution-to-inject-drivers-in-windows-10-sysprep/5
Have worked for all of my models so far.
And all i need to do is keep my driver model repo in check.

Here is another approach.
https://forums.fogproject.org/topic/9859/post-deployment-driver-installation-using-powershell-scripts

Hope this guides you in the right direction.

Hello!
so there has to be imaging task in place for the computer to start imaging. These tasks are managed from the FOG server.
Even If they manage to start pxe boot without there being a scheduled imaging task in place it will just load the “fog menu”.
The menu has the option “Deploy now” but you can have that password protected.

That’s how we have it set-up. My English is not the best hope it makes sense and answered your question.

No volume license is one key that has many activations.

I’ve noticed that using the same OEM key on the same model and manufacturer has worked but you shouldn’t do it.

Here is link to check the OEM key and automate the activation.
https://blogs.technet.microsoft.com/in-teaching-others-we-teach-ourselves/2016/12/13/how-to-deploy-windows-10-with-a-oem-product-key-from-the-bios-with-microsoft-deployment-toolkit/