@mwilcox said in Windows 10 Driver and Deployment Question:
So maybe that was the other unsigned driver which caused the hang. I can do more testing tomorrow
If there are any unsigned drivers or any reason why the driver install pops up with a question it will fail the install (probably not something you want to happen at a client’s place). There is a bcd edit command you can turn on in your golden image and then turn off in the setupcomplete file that will accept all drivers signed or not. Usually Dell only ships signed drivers. So I’m a bit surprised at the condition.
With that setup does it install drivers after the deployment while it’s booting up Windows?
Yes, but in the golden image we will typically deploy the Dell WinPE driver pack so the golden image has at least the basis drivers. If you are shipping the hardware with Win10 then most of the basic drivers are already built in.
Would there be a prompt or something somewhere in the FOG GUI that would ask for a activation key before image deploy?
If you are using the load and go approach, you are not registering the computers with FOG. Normally when you do a full registration you could enter the key there. But if you are using the load and go approach then you are not registering the machine with FOG so you have to be a bit more creative. In this case you would create in your post install script a prompt to enter the key value, then take that key and update the unattend.xml file using the fog.updateunattemd. Probably that script is where you would want to stop and ask the FOG installer for the key.
Testing is the key even if you eventually end up with a hybrid of FOG doing everything, except you turn the system on at your facility do a QC check (drivers: yes, activation: yes, etc) then ship it to the customer like you do today. The idea is to eliminate as much hands on stuff you do so you can build more systems faster.
