Best posts made by ek_N

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.