With the new build:
So here is an interesting fact, I was trying something different when I originally made this post. I went into my VM I am using and deleted the last partition (it was marked as recovery tools), then uploaded and deployed, and it worked! So in all of my previous images the last partition is the OS drive, in this new version it makes a "recovery tools" partition (ntfs) as the last one by default.
So in your request to deploy only part 4 above that is only a recovery tools part, the actual OS part is 3
So I decided to update our golden image, so I fired up the Hyper-V VM (UEFI) that I always use, booted from the "disc" dumped partition tables, let windows build a new one and proceeded as usual from there. I uploaded the image then tested it on a machine (UEFI), and there was no boot, I changed to BIOS mode, still no boot. I haven't done anything different than I have in the past. I have tried to reupload a few times even tried to change compression back to lz4 (decompression errors then). I looked around at everything and the only thing I could see different was the schema has partitions that are a bit different than the previous. It has the partitions out of order. I then remembered I needed to check out the WinPE for some surface devices, so I set about getting that all configured. Then without changing anything else I used WinPE mode to upload and deploy and it worked.
So my issues is that WinPE mode is sloooow especially to boot, and I believe there is just something minor going on that could get me back to normal. I am attaching the logs from upload and deploy for review.
We are trying to do some cloning with the Surface go, and here is where we get stuck. We boot them up using the Microsoft USB>ETH adapter, once the PXE process hands off, we do not get keyboard or network. If we use a Belkin USB>ETH +USB adapter the Surface won't boot using PXE. So we end up pluggin the Belkin in, and attach Ethernet, Keyboard, and the Microsoft USB>ETH adapter, this then boots PXE through the MS adapter that is attached to the same network and the PXE hand off then uses the Belkin to connect to the network to do the actual cloning and the keyboard works.
I'm thinking it has to be a Kernel/driver issue so is there anyway we could get an updated kernel?
Just confirmed UEFI boot from the ISO/USB generator works fine, so I must be having the same issue as others with Dell and iPXE