Saw that. Good work. The only reason I wanted WDS and FOG to work together was to leverage WDS’s handling of UEFI/BIOS identification. But the DHCP method is much more elegant and less resource intensive.
I am glad that you got that working though. Options are valuable when doing IT work.
Also please remember that UEFI is not necessarily Secure Boot. Secure Boot is an optional feature of UEFI, which you you will need to disable if you want to boot ANYTHING other than Windows. Yes, technically Secure Boot signing is available to the Linux community, but very few Linux kernels will ever work with Secure Boot.
UEFI support handles the new method of using the hardware initialization and interaction which is much more efficient than BIOS, which is one of the reasons that an OS that supports UEFI can boot so much faster on a UEFI board. So yes, you can make FOG work with a UEFI ecosystem, but you will either need to disable Secure Boot on each workstation every time you want to boot it with FOG, or you will need to disable Secure Boot completely. Honestly Secure Boot is more of a benefit to consumers, and only helps prevent them from getting their bootloader hijacked. A company or enterprise network should have other security measures in place that help prevent and/or mitigate this risk.
Curiosity is killing me… what where you wanting to do with this kind of setup?
@Tom-Elliott True, if you are imaging odd systems, you absolutely want to specify LAN drivers. However the Windows Driver Framework supports so many classes of LAN adapters, chances are yours are already supported by built in Windows drivers. You should of course test a few systems before rolling out a new image.
You may need to check that the UEFI Windows Boot Manager option in the BIOS is pointed at the right location.
@Wayne-Workman In relation to your manual installation of drivers… Windows 10 is able to automatically identify and install drivers for so many devices anymore, its hard to want to bother even adding drivers manually for most workstations.
@Wayne-Workman We’re in the process of replacing an XP desktop that was running the controller for our HVAC with a Windows 10 system. I guess we can let this new one sit for another 10 years. 
I’m late to the party, but no I never got WDS and FOG to play well together. I wasn’t just trying to get them to coexist on the same network though, I was pressing their faces so hard together that they’d forget if they were kissing or not. My goal was to work around the now solved issue of using a Windows DHCP environment to handle Legacy and UEFI PXE coexistence, which WDS can inherently handle.
This is tempting me… but I must stick to my guns on migrating away from our 2008R2 servers. Still, I am interested in this too. For science.
Agreed. Really it just comes down to the IT department at the organization on whether they are more comfortable managing bare metal Windows Server or Linux.
And wow… 80K a year… guess I better do some more training.
For reals this time though, I’m done hijacking the thread.
I suggest against installing Linux distros on Generation 2 Hyper-V. Newer Debian family distros technically support it, but I have seen some instability caused by the emulation of EFI hardware. Generation 1 works well still; its only drawbacks are a little more overhead and slightly slower boot times. But since Hyper-V and Linux have never fully integrated together, you shouldn’t see much difference in performance.
That being said, I’ve had FOG running on Gen1 Hyper-V for quite a long time here (even prior to 1.2.0), and its worked incredibly well. Granted I have dedicated a fair amount of resource on the host machine, and made sure that the other virtual instances running on the host are not disk-intensive.
Honestly, if you are running a most Microsoft server environment, I would strongly suggest using Hyper-V for your virtualization. It has been the easiest to manage throughout our domain, and most people’s Windows Server licensing already covers the use of at least two Windows Server instances on the host without having to pay for any additional licenses. And Linux system’s won’t use up any licensing at all, because Linux. And then there’s the added benefit that you can scale from a single virtual host to eventually having a clustered group of servers with fail-over and/or load balancing, using identical or mixed hardware. Really I do not understand why more Enterprise users running predominantly Windows environments do not use Hyper-V and instead go with less flexible and more expensive solutions.
</thread hijack>
So glad I set up a WSUS server on our domain. Its allowed me to dodge a number of bullets like this now. Its my common practice now to sit on all Microsoft patches for a week before rolling them out. Let the consumers and small businesses find the bugs. Enterprise aint got time for dat.
The best version of Ubuntu that I can recommend for any server installation is called Debian.
I would strongly suggest using the latest “trunk” version of FOG, as well as making sure you have your Surface’s firmware completely up to date, because earlier versions of the Surface firmware made using UEFI network boot nearly impossible.
If you can reupload the image, then yes, I would do a fresh install on the 3020 and overwrite the VM image.
The mode you would want to switch to to make the current image boot is ATA by the way.
Windows 7 still thought SATA was a little hard. Before you upload the image, you should generalize the way Windows handles its storage drivers. HowTo:
How to change sata modes after windows installation
What that will do is force Windows to try multiple different types of storage driver on boot, instead of just the last one it used. The reason you are having this is that the VM likely used a form of IDE driver, and your Dell Optiplex 3020 defaults to AHCI mode on its SATA port.
If you really didn’t want to upload the image again, you could go to the BIOS and change the SATA mode to IDE or Compatibility. This should allow you to boot at least, but you will be running the drive controller much slower than it is capable of.
Press F8 and select “Disable Automatic Restart on System Failure”, then look for a BSOD.
.