Coexistence of UEFI and Legacy - Troubleshooting help
-
Okay, thanks.
So, We have two DHCP Servers, one gets its settings from the other per replication. So both should have the identical settings.
I’m refering to: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
Our new DCs are Windows Server 2016.
Screenshots from my dhcp server settings are in the same folder as before, the details for the other vendor classes are the same.
I added Policies with a * in front of the vendor class because i hoped that would change something, it didnt work without those either though.
-
I am so so so sorry.
Just came out of a call with our external IT partner and casually he said: Oh btw.: I deactivated your Policies on the DHCP server.
And I didn’t notice of course … so sorry for wasting time, it works now.
-
@taspharel No worries, its always good to know that neither of us are insane where you know what should be and we found what is according to wireshark.
I assume they will reenable your policies? You kind of need them to support dynamic booting. Well that’s not totally true, if you can’t have the policies in your MS dhcp server you can run an external proxy dhcp to supply the missing pxe boot information. The point is there are other ways to achieve what you need.
Can we close this issue?
-
Already enabled and works like a charm.
Can be closed, thx for helping out.
