UEFI PXE boot

tesparza

@george1421 https://drive.google.com/file/d/1CqqzV3NZey74vw-CaOhQjEjTcwYN4glK/view?usp=sharing

tesparza

@george1421 0_1536950052139_Screen Shot 2018-09-14 at 1.33.25 PM.png

george1421

@tesparza Update: after the OP supplied a clean pcap and reviewing it, we’ve determined that the issue is with the dhcp server. The target computer is behaving exactly as it has been told.

So lets focus back onto your dhcp server can you post a screen shot of your dhcp vendor classes? (Hint: the free application GreenShot or the Windows clipping tool will give us a better resolution picture. I like greenshot because it gives you the tools to annotate the picture.)

Your vendor classes should look like mine.
0_1536950567636_70afb2ad-c22e-41bd-b69a-3831d840d71d-image.png

The xscale entry is not necessary for almost 100% of the installations. Your vendor class fields must match exactly what I have under the description.

george1421

@george1421 Then in the policy for the scope in question (could also be a global scope, but make sure you don’t have any local overrides) your polices should be set up similar. Just be aware you will need one policy for each vendor class you setup. Here is an example of one.

On the conditions tab you setup what to match in the packet
0_1536950886939_ade90cf9-7c7a-457f-9764-c60e9fa6fee8-image.png

Then on the options tab, you need to set dhcp option 67 to the boot file you need. In this case its ipxe.efi.
0_1536950949738_d5865ddb-d88e-4b67-9e08-9460ab71c988-image.png

tesparza

@george1421 0_1536951271937_Screen Shot 2018-09-14 at 1.54.17 PM.png

george1421

@tesparza Well OK that one looks perfect. What about the policy now? Will you post images from the tabs I referenced below?

tesparza

george1421

@tesparza While this is a bit off point, the dhcp 66 options for each policy is a bit redundant since you are not changing the boot server based on each policy, you only need to change the boot file name.