@Wayne-Workman I am able to get it to work too. Used this: https://technet.microsoft.com/en-us/library/dn613857.aspx to add all network drivers (got around 40 laptops here) and created 2 samba shares on the FOG server. One to the installation folder (where I got win7, win8 and win10) and one to the same folder with write rights. This way I am able to alter the installations from my pc and create an unattended.
scrolling down shows me you beat me to it 
@Wayne-Workman @Quazz already on it. Mounted the disk with DISM
dism /Mount-Image /ImageFile:“c:\temp\winpe\x86_64\media\sources\boot.wim” /index:1 /MountDir:“c:\temp\winpe\x86_64\mount”
navigated to Windows\System32\startnet.cmd
It already contains wpeinit. Do not change that line, but add your code after that.
Mine so far is
net use z: \x.x.x.x\isos\win7
net use x: \x.x.x.x\isos\win8
net use y: \x.x.x.x\isos\win10
menu.bat
now creating a menu in a separate batch file
So after that I created a menu.bat in the system32 folder with
http://www.sevenforums.com/tutorials/78083-batch-files-create-menu-execute-commands.html
to start the setup of different windows versions. Now I only have one PE box and 3 Windows installs. The next step is to automate the installations.
Did you get the same error in installation as mine?
https://forums.fogproject.org/topic/7326/there-can-be-only-one-timestamp-column-with-current_timestamp
Got same error as result
searched a lot in the forums, but couldn’t find the answer.
Try to set up a new FOG image server. Installed Debian (later also tried CENTOS and Ubuntu) and get the latest developer release. I need this release because of the Broadcom chipset in the workstations.
When I install it, everything works fine. But at some point in the Install script one needs to go to the url
http://xxx.xxx.xxx.xxx/fog/management
to create the database and create the tables.
After pressing the button, the following message appears:
Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause
ALTER TABLE fog.hosts ADD COLUMN hostSecTime TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
The login works, but there is no possibility creating hosts. Every registration fails.
What needs to be done to get it running?
@Wayne-Workman in out environment that’s nearly impossible. We sell new and second hand laptops. So we got different models every day. Now we can just start the installation and sysprep it afterwards.
Do you want the documentation or did you write your own now? I almost finished and only need to translate it.
I didn’t test it. But I would say, mount it via linux (ssh into the fog server) and make sure it got the right permissions.
@Wayne-Workman @Quazz already on it. Mounted the disk with DISM
dism /Mount-Image /ImageFile:“c:\temp\winpe\x86_64\media\sources\boot.wim” /index:1 /MountDir:“c:\temp\winpe\x86_64\mount”
navigated to Windows\System32\startnet.cmd
It already contains wpeinit. Do not change that line, but add your code after that.
Mine so far is
net use z: \x.x.x.x\isos\win7
net use x: \x.x.x.x\isos\win8
net use y: \x.x.x.x\isos\win10
menu.bat
now creating a menu in a separate batch file
So after that I created a menu.bat in the system32 folder with
http://www.sevenforums.com/tutorials/78083-batch-files-create-menu-execute-commands.html
to start the setup of different windows versions. Now I only have one PE box and 3 Windows installs. The next step is to automate the installations.
@Wayne-Workman I am able to get it to work too. Used this: https://technet.microsoft.com/en-us/library/dn613857.aspx to add all network drivers (got around 40 laptops here) and created 2 samba shares on the FOG server. One to the installation folder (where I got win7, win8 and win10) and one to the same folder with write rights. This way I am able to alter the installations from my pc and create an unattended.
scrolling down shows me you beat me to it
@Wayne-Workman But it works
Now I can starting the UEFI project. My working day is over, so get back to you tomorrow. Thanx for your help so far.
@Wayne-Workman The link you gave me says the same I think:
Download the latest version of wimboot and extract the file wimboot to the same directory on your web server.
Create a text file boot.ipxe in the same directory on your web server, containing:
#!ipxe
cpuid --ext 29 && set arch amd64 || set arch x86
kernel wimboot
initrd ${arch}/media/Boot/BCD BCD
initrd ${arch}/media/Boot/boot.sdi boot.sdi
initrd ${arch}/media/sources/boot.wim boot.wim
boot
The files are present at the given location.
@Wayne-Workman thx! My paths are very different,
kernel winpe/wimboot
initrd winpe/${arch}/media/Boot/BCD BCD
initrd winpe/${arch}/media/Boot/boot.sdi boot.sdi
initrd winpe/${arch}/media/sources/boot.wim boot.wim
boot
but I will test it now.