WDS and FOG
-
I may have hit my last straw with WDS. I might be able to make it work by compiling my own rendition of iPXE, but it appears that everyone would have to compile their own if they wanted it to work with this. I am looking at another option now that will in the end still give proper arch detection and handling, and also allow those who want to use WDS to do so. But I can tell you right now that if this works out it will be a lot less hacky.
-
Hope it’s open source…
-
Oh, it is. I’m using dnsmasq.
-
[quote=“need2, post: 46615, member: 21891”]Oh, it is. I’m using dnsmasq.[/quote]
So, then this begs the question, can dnsmasq and DHCP be used on the same FOG machine? Because this will come up.
-
Fairly certain I saw config options that would allow for that. I’m pressing forward either way, and if it’s an issue I’ll try to fix it later.
-
I spent some time on this over the winter, specifically trying to add a custom entry for WDS to FOG’s advanced iPXE boot menu…without any help from dnsmasq.
I remember the part that stumped me was passing Option 60 (PXEClient) with iPXE. If this is even possible and anyone knows how to do this I’d love to hear it
-
It’s probably easier to use a Open-Source front end for everything… like SysLinux.
Cant change WDS’ code.
-
It shouldn’t be too hard to have a method to chain to WDS. Its just a matter of triggering the right file. It does matter what version of Windows Server you are running. When I get to that part, I will be making a connection to a Windows Server 2012. The same methods should also work on 2008r2 and 2012r2.
Any/all results and documentation on my UEFI/BIOS coexistence will be going into a new thread. Since that will use DnsMasq it will be off topic for this thread.
