@arcfury The last question is in regards to how you configured your dhcp server to load the iPXE boot kernel. Without those settings in place you should not get the FOG menu to display. For dhcp option 66 you should have the IP address of the fog server, and for dhcp option 67 you might have a file like undionly.kpxe.
From the sounds of it when you pick registration the screen just goes black? You don’t see any messages about loading bzImage and init.xz??
I can’t seem to get into my MDT environment at the moment, but I can get at the setupcomplete.cmd file.
This undoes what our action turns on in MDT
reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v PromptOnSecureDesktop /t REG_DWORD /d 1 /f
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
[Edit]: Look in this thread: https://social.technet.microsoft.com/Forums/en-US/865bc19b-c3f5-4a87-b1fb-b255de072180/temporary-disable-driver-signing-check-in-windows-7?forum=w7itproinstall
Search for: “UAC Lower.bat” to see the premise of what is going on.
@fishfox Give me a moment to look at my MDT setup
First let me say I have not done this yet, but there is a plugin called TaskStateEdit that you can use to create custom fog tasks. Look at the Memtest86+ task to get an idea what you might do for your custom task.
Also realize that your iPXE menu has nothing to do with fog custom tasks. They are similar in setup, but different.
If what I posted was correct, then you have bitlocker enabled on your hard drive (even if you have not turned on bitlocker to start).
Review this post: https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
Pay specific attention to what @THEMCV has to say.
Is this a win10 image? If it is, can we assume that when FOG goes to capture it, partclone is using RAW format?
@fishfox pnputil is the easiest fix if you have signed drivers. If you don’t have signed drivers, turn off driver signing requirements before you sysprep the image then turn the requirements back on after you run pnputil in setupcomplete.cmd. Not an ideal solution and really unsure why MS broken driver loading with 1709. I haven’t touched 1803 yet to see if they’ve fixed it or broke it even worse.
lets start out with some basics.
@zacadams Would you mind uploading the pcap to a google/dropbox drive and IM me the link. I’d like to look at a bit more than a pict of the file.
But just off the top, I would expect that splat ( * ) at the end of the file name to be trouble.
[Edit] Also watch the firmware on those 7010’s I had one with A16 yesterday that couldn’t pxe boot in uefi mode until I updated to A25.
With the http redirection that fog is currently using, its a bit difficult to host other files under the http protocol.
So what can you do?
Move to one of the other supported protocols like tftp:// or nfs://
To use the tftp:// protocol you would update your menu to be something like this (note I fixed your fetch kernel parameter too).
kernel tftp://${fog-ip}/iso/gparted/live/vmlinuz vmlinuz boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=tftp://${fog-ip}/iso/gparted/live/filesystem.squashfs
initrd tftp://${fog-ip}/iso/gparted/live/initrd.img
The only thing I’m unsure of is if the kernel supports tftp pulling. Also the variable ${fog-ip} is replaced by the fog menu with the IP address of your fog server. Hard coding the IP address in the fog menu doesn’t make it very portable.
So since we are using tftp:// protocol you need to place the files in /tftpboot/iso/gparted based directory.
If that doesn’t work then you could try nfs:// which should be supported by the linux kernel.