@george1421 Sorry for not getting back to you earlier, thanks for the response again. This sounds like exactly what I would want to do. Although it leaves me a bit worried about the drivers installing and Windows activating after it’s left our shop. But I guess if I can test it and it works it wouldn’t be any worse than what we’re doing now.
I did get your driver scripts, and drivers for a Dell E6430, loaded last night and after the deployment it did find the drivers on the server. It didn’t load them because I did’t have the setupcomplete.cmd set up yet. I did make that file on the imaged 6430 and ran it and it did install the drivers (minus one fingerprint reader), so they were there in the C:\drivers. There was one unsigned driver that I had to give permission to install.
This is the same as Windows 10 hangs at “Just a moment…” on Dell Latitude 5500 because I then put the setupcomplete in C:\Windows\Setup\Scripts (which I created; right or wrong) on my golden image. I deployed that today and it still found the drivers, but after finding the drivers it eventually just hung at the “just a moment” screen. This was after about a half hour and I had to leave work, with this machine, so I just unplugged it. After seeing the previously mentioned thread I booted it up and it went to the OOBE, I went into audit mode and indeed all the drivers were installed, but now missing 2 fingerprint reader drivers instead of one previously. So maybe that was the other unsigned driver which caused the hang. I can do more testing tomorrow.
With that setup does it install drivers after the deployment while it’s booting up Windows?
But back on task, it sounds like I’ll need to use the unattend file for the activation code and the setupcomplete.cmd will take care of putting the driver on the target machine. Would there be a prompt or something somewhere in the FOG GUI that would ask for a activation key before image deploy?
Then it is shipped and drivers and activation is done when the end user turns it on. I can see how this would be a huge time saver on my end. I would just be worried about something going wrong with driver installs and activation on the customers end. Drivers not working would be my fault but I also worry about someone entering the activation code wrong. I’m sure there’s ways to safeguard that, someone has to be doing this already.
I’ll get the home lab set up again tomorrow and see what I can get working.
Sorry for the ramble, thanks for the help!