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.
Best posts made by need2
-
RE: Debian 8, Fog trunk, PXELinux on MS Server and MS DHCP help
-
RE: Best version of Ubuntu for FOG 1.2.0
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.
-
RE: Debian 8, Fog trunk, PXELinux on MS Server and MS DHCP help
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.
-
RE: Best version of Ubuntu for FOG 1.2.0
@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.
-
RE: Imaging Windows 10
@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.