Thankyou so much for this video. I've been banging my head against this for ages. It was the Option 60 PXEClient that we were missing. Now I'm working.
Thanks sooo much for this!! I had issues trying to image some Surface Pro 4 tablets and this resolved that and now I also don't have to enable legacy boot devices anymore on other machines.
This is a great, informative video and well explained. Unfortunately not applicable to my WDS/MDT environment, but I still liked it. There's some weird comments on here, though- I don't know why people get so angry....I appreciate people like yourself taking the time to provide help for free!
This is not correct, this video is applicable for WDS/MDT, we use it just like that. The only problem we ran into was that we do not use the Microsoft DHCP Server and we had some problems with our DHCP Server and Client Classes
Hi, I did the whole configuration (2012 R2, clients win7 x64 uefi): 1 - I have to configured PXEClient on server options, clients didn't boot using Scope Options 2 - When boot the client doesn't see the policy, they always pick wdsnbp.com to boot Any suggestions? Thanks in advanced
Thanks for very helpful video, just have a question about boot image on SCCM. what is your boot image on SCCM? is it x86 or x64? because for UEFI x64 machines, x64 boot image should be used.
I pay attention to the helper address setting from switch, so my question is that has it to make a match with some switch or device to setup DHCP Server?
I follow this but it doesn't seam to pick a different boot wim. Right now we have the x86 boot wim as the default. Does settings this up not allow you to have any device boot up and choose the correct boot wim based on the architecture?
there is no need to use IPhelper if WDS and DHCP are on the same server and same network with clients. I have followed your instructions on setting up the DHCP policies and still not able to PXEboot an UEFI enabled Dell laptop. it shows no boot device found.
So followed instructions to a T, but it doesn't appear to be working when relying on the DHCP Policy. Works fine if I just do regular scope option 66&67 for BIOS or regular scope option 60,66, and 67 for UEFI. Systems attempting to PXE boot are a DELL Optiplex 9010 using Intel NICs if that matters. Any ideas?
BIOS works fine, its the UEFI method that doesn't appear to go thru it just hangs like it can't find DHCP/DP, I'll post update when back in office with better description. I also want to possibly try updating the BIOS to the latest version (that may be some issues as well) But same results on 9010/9020 systems. BIOS mode works UEFI tanks.
If I specifically tell DHCP scope options to use UEFI it works but if I try to follow the methods above for the Policy options to work for UEFI/BIOS together, is where I'm not getting thru just for UEFI. But I haven't had a chance to pickup and continue troubleshooting. Thanks anyhow I'll post back if I get any luck would certainly like to get the Policy Options in DHCP working to prevent having to manually set a large amount of scopes everytime when determining BIOS/UEFI as I would need to support both methods in our environment unfortunately.
Hello, i've set up DHCP like you did in this video, however when i try to PXE boot EFI through VMWare it works half the time, and gets stuck on contacting server half the time, resulting in error 0x102. I also noticed you made a vendor class for uefi x86 but you didnt make a policy for it, why is that?
Hello, I wonder if you can help. I am getting stuck at the contacting server... bit for UEFI computers, I have the option 66 and 67 set as you advise and I've added in option 60 (had to do it via command line though as it wasn't available to choose) and it is still stuck on the contact server....any ideas? As in your video if I change 67 for bios then it loads fine Thanks!
+zeofriendly are you booting both BIOS and EFI at the same time? If so you need to set them both as per the video. So BIOS boot fine but EFI not? You kind of elude to the fact that if you change something then BIOS boots, which it should always do if you follow the instructions above.
i am not getting Policy folder in my Server 2008 R2 DHCP Server.... any solution to it? i have 2 DC's at 2 physical sites. one is in Server 2012 R2 which i have successfully configured but i am stuck at configuring the other Server 2008 R2 DC. Can you help me out, Please.
As stated below, it just simply does NOT work for UEFI. Also the video proves nothing at all, as the very default WDS x64 efi files was specified: wdsmgfw.efi Try to do it with something completely different ie ipxe.efi to see that is really does NOT work Most likely to make it work, more config would be needed ie support.symantec.com/en_US/article.HOWTO7071.html
The vid was made with a ConfigMgr PXE Distribution Point, which has different file names, as mentioned in the comments below. Also highlights that Option 60 has to be set when using the iPXE boot loaders. When using customer loaders, like iPXE, you have modify the WDS boot names with a command line, on the WDS box itseld. Otherwise it wont work, as you have pointed out.
Huh? The video shows how to use DHCP to control booting to a ConfigMgr PXE Service Point, instead of using IP Helpers. Nothing else. This process still uses and requires the wdsmgfw.efi, which is why its selected and used. This file then communicates with WDS/PSP to get the rest of the files and process started. This process cannot use any other third party like iPXE, as the process depends on the Windows loaders. So whats your point? That the title should have been: "How to use DHCP to contol WDS/PSP instead of IP Helpers"?
Newbie question: I must be missing something... You say this guide is for using DHCP options instead of IP helpers, but you still need a DHCP relay (IP helper?) on the router that sits between your (PXE) clients and your DHCP & BOOT server, otherwise no DHCP broadcast packets from the clients will ever reach the DHCP server which is in another subnet. Right? (I'm not familiar at all with specific Cisco terms so that might explain my confusion) Thanks for any useful info regarding this...
Thank you so much for the class, simply brilliant!
Thankyou so much for this video. I've been banging my head against this for ages. It was the Option 60 PXEClient that we were missing. Now I'm working.
Brilliant! Was having problems deploying images to Surface Pro 3 until I found this. Great explanation and easy to follow. Thanks!
Great video covering a tricky configuration problem!
Great video!
Awesome work man, great video. Put this to use at work the other day and it paid off. Much much appreciated
Thanks sooo much for this!! I had issues trying to image some Surface Pro 4 tablets and this resolved that and now I also don't have to enable legacy boot devices anymore on other machines.
Have been trying to figure out how to pxe boot both bios and uefi, this is the ticket.
This is a great, informative video and well explained. Unfortunately not applicable to my WDS/MDT environment, but I still liked it. There's some weird comments on here, though- I don't know why people get so angry....I appreciate people like yourself taking the time to provide help for free!
This is not correct, this video is applicable for WDS/MDT, we use it just like that. The only problem we ran into was that we do not use the Microsoft DHCP Server and we had some problems with our DHCP Server and Client Classes
loving the vid bob, thanks helped me alot in setting up the wds
Brilliant, many thanks for sharing your experience!
Great and helpful video! Thank you for sharing!!
What a fabulous Video. Thankyou.
This worked great, thank you :)
Just....Genius !
AWESOME ! Very Helpful !
Brilliant. THANK YOU!!
Amazing video. Very helpful, and thank you for making it. What is the website for the class configuration?
UEFI boot results in PXE-E16 No offer received. Anyone ever seen that error before?
Hi, I did the whole configuration (2012 R2, clients win7 x64 uefi):
1 - I have to configured PXEClient on server options, clients didn't boot using Scope Options
2 - When boot the client doesn't see the policy, they always pick wdsnbp.com to boot
Any suggestions?
Thanks in advanced
Thanks for very helpful video, just have a question about boot image on SCCM. what is your boot image on SCCM? is it x86 or x64? because for UEFI x64 machines, x64 boot image should be used.
I don't have option 060 and smsboot\x64\.efi file does not exist. RemoteInstall folder has boot\x64\.efi file not smsboot\x64
I pay attention to the helper address setting from switch, so my question is that has it to make a match with some switch or device to setup DHCP Server?
I follow this but it doesn't seam to pick a different boot wim. Right now we have the x86 boot wim as the default. Does settings this up not allow you to have any device boot up and choose the correct boot wim based on the architecture?
there is no need to use IPhelper if WDS and DHCP are on the same server and same network with clients.
I have followed your instructions on setting up the DHCP policies and still not able to PXEboot an UEFI enabled Dell laptop.
it shows no boot device found.
why still using options 66+67 when a WDS is already taking care of this ? It works fine even wothout these DHCP options. Can someone explain please?
I'm not seeing the Policies folder in my DHCP, I am running server 2008 R2 with WDS.
Amazing thanks!
Great video. I don't have a Policies folder in my DHCP console, how do I enable this please?
+dreddric you upgrade to Windows Server 2012 or later. :-)
So followed instructions to a T, but it doesn't appear to be working when relying on the DHCP Policy. Works fine if I just do regular scope option 66&67 for BIOS or regular scope option 60,66, and 67 for UEFI. Systems attempting to PXE boot are a DELL Optiplex 9010 using Intel NICs if that matters. Any ideas?
The 9010 is bad at PXE, are you trying UEFI mode or BIOS?
BIOS works fine, its the UEFI method that doesn't appear to go thru it just hangs like it can't find DHCP/DP, I'll post update when back in office with better description. I also want to possibly try updating the BIOS to the latest version (that may be some issues as well) But same results on 9010/9020 systems. BIOS mode works UEFI tanks.
EUFI PXE is not supported on those models AFAIK. Talk to Dell!
If I specifically tell DHCP scope options to use UEFI it works but if I try to follow the methods above for the Policy options to work for UEFI/BIOS together, is where I'm not getting thru just for UEFI. But I haven't had a chance to pickup and continue troubleshooting. Thanks anyhow I'll post back if I get any luck would certainly like to get the Policy Options in DHCP working to prevent having to manually set a large amount of scopes everytime when determining BIOS/UEFI as I would need to support both methods in our environment unfortunately.
Hello, i've set up DHCP like you did in this video, however when i try to PXE boot EFI through VMWare it works half the time, and gets stuck on contacting server half the time, resulting in error 0x102. I also noticed you made a vendor class for uefi x86 but you didnt make a policy for it, why is that?
+Olve Skagen because the Windows loaders are buggy.
I don't get any other info after 0000 when I type in the Arch command?
TOP Man, I can use both option at the same time (Legacy and UEFI) ?
Muito obrigado!! Ajudou demais com a configuração no Windows Server 2012
Hello, I wonder if you can help. I am getting stuck at the contacting server... bit for UEFI computers, I have the option 66 and 67 set as you advise and I've added in option 60 (had to do it via command line though as it wasn't available to choose) and it is still stuck on the contact server....any ideas? As in your video if I change 67 for bios then it loads fine Thanks!
+zeofriendly are you booting both BIOS and EFI at the same time? If so you need to set them both as per the video. So BIOS boot fine but EFI not? You kind of elude to the fact that if you change something then BIOS boots, which it should always do if you follow the instructions above.
Awesome Thank you
i am not getting Policy folder in my Server 2008 R2 DHCP Server.... any solution to it?
i have 2 DC's at 2 physical sites. one is in Server 2012 R2 which i have successfully configured but i am stuck at configuring the other Server 2008 R2 DC. Can you help me out, Please.
Policy came with Server 2012 I believe.
is there way to use IPXE
I dont even get dhcp on efi mode.
nothing comes up when I try to define vendor class
Thanks!
yeah no iphelper
As stated below, it just simply does NOT work for UEFI. Also the video proves nothing at all, as the very default WDS x64 efi files was specified: wdsmgfw.efi
Try to do it with something completely different ie ipxe.efi to see that is really does NOT work
Most likely to make it work, more config would be needed ie
support.symantec.com/en_US/article.HOWTO7071.html
The vid was made with a ConfigMgr PXE Distribution Point, which has different file names, as mentioned in the comments below. Also highlights that Option 60 has to be set when using the iPXE boot loaders. When using customer loaders, like iPXE, you have modify the WDS boot names with a command line, on the WDS box itseld. Otherwise it wont work, as you have pointed out.
WDS is not configured when used with SCCM!
Just does not work. This video proves nothing at all!
Huh? The video shows how to use DHCP to control booting to a ConfigMgr PXE Service Point, instead of using IP Helpers. Nothing else. This process still uses and requires the wdsmgfw.efi, which is why its selected and used. This file then communicates with WDS/PSP to get the rest of the files and process started. This process cannot use any other third party like iPXE, as the process depends on the Windows loaders. So whats your point? That the title should have been: "How to use DHCP to contol WDS/PSP instead of IP Helpers"?
Lucky you, for my in same setup it NEVER works. I lost plot why you even bothered with options if using SCCM/WDS (as it is not needed at all)
Newbie question: I must be missing something... You say this guide is for using DHCP options instead of IP helpers, but you still need a DHCP relay (IP helper?) on the router that sits between your (PXE) clients and your DHCP & BOOT server, otherwise no DHCP broadcast packets from the clients will ever reach the DHCP server which is in another subnet. Right? (I'm not familiar at all with specific Cisco terms so that might explain my confusion)
Thanks for any useful info regarding this...
is there way to use IPXE