@Wayne-Workman said in DHCP failed - undionly.pxe:
It’s really easy to do.
@george1421 said in DHCP failed - undionly.pxe:
@tigerpride said in DHCP failed - undionly.pxe:
FWIW: Only the dhcp server needs to be 2012 the reset of your domain can remain on 2008. But you will have to migrate sooner or later. 2008 server is already 8 years old.If you don’t want to upgrade and can isolate the uefi and bios clients to different dhcp scopes you can do it that way too. Just create different scopes with different boot files for each scope. Its not really clean but will work. In my case we only pxe boot when we image machines, the default target computer will boot from the hard drive and only boot pxe when we select it from the boot menu.
Probably is a snap and I realize it needs to be done, but the thing is, I’m just week 4 into my new position and environment. DHCP is done by the primary DC. I could move it to the secondary (which is 2012) but I don’t know what’s all dependent yet. I’d rather not risk it at this point since my users will return in a week and a half. I’ve a ton on my plate as is, and the main LAN + VOIP system potentially tanking is not really how I’d like to remember my start here.
To be honest I’m waiting for Server 2016 to come out of RC to set up a test tertiary and see about winking off 2008 if that’s to my liking.
@forte647 said in DHCP failed - undionly.pxe:
My company recently switched to Probook 455 G3s, and I had the same issue after the switch. Something about the NIC in these laptops isn’t playing nice with undionly.pxe? I switched my boot file to ipxe.pxe and it worked. So maybe try using ipxe.pxe and see what happens.
You got it! That works. No dhcp failed or kernel panics! I’m grabbing the stock image as we speak, then setting up a fresh W10 image to base a capture from for the rest of this lot.
TYVM! Thanks for all the help everyone!