UEFI PXE Boot SCCM 2012 R2 + Server 2012 DHCP Boot Options
HI,
I have a problem with SCCM 2012 R2 server. Server 2012 R2
UEFI PXE boot is not working.
I am not sure what to specify in Option 67
DHCP Option 67 : \smsboot\x64\wdsnbp.com
i have also tried \smsboot\x64\wdsmgfw.efi
but neither options are working for UEFI.
\smsboot\x64\wdsnbp.com Works if I switch the client BIOS to BIOS (Not UEFI) Non uEFI clients are working. able the receive the boot file.
I have also got Option 60 = PXEClient
Otpion 66 : ipaddress of SCCM server
I have a problem with SCCM 2012 R2 server. Server 2012 R2
UEFI PXE boot is not working.
I am not sure what to specify in Option 67
DHCP Option 67 : \smsboot\x64\wdsnbp.com
i have also tried \smsboot\x64\wdsmgfw.efi
but neither options are working for UEFI.
\smsboot\x64\wdsnbp.com Works if I switch the client BIOS to BIOS (Not UEFI) Non uEFI clients are working. able the receive the boot file.
I have also got Option 60 = PXEClient
Otpion 66 : ipaddress of SCCM server
ASKER
Using HP Switches.
No vlans Client and WDS/SCCM and DHCP server are in the same Vlan.
Client is a Vmware esxi VM
SCCM/WDS is a VMware esxi VM
DHCP/DC is a Vmware Esxi VM
I don't thing there are and Ip-helper address on the switches.
What is the recommended best practice ?
This setup should work as Client and Server are in the same Vlan/Broadcast domain.
but when the client trys to boot it gets PXE-E21.
I will try to remove PXE role from SCCM and wait 20 mins and add it back
No vlans Client and WDS/SCCM and DHCP server are in the same Vlan.
Client is a Vmware esxi VM
SCCM/WDS is a VMware esxi VM
DHCP/DC is a Vmware Esxi VM
I don't thing there are and Ip-helper address on the switches.
What is the recommended best practice ?
This setup should work as Client and Server are in the same Vlan/Broadcast domain.
but when the client trys to boot it gets PXE-E21.
I will try to remove PXE role from SCCM and wait 20 mins and add it back
You would be right, everything on ESXi - are they on the same vSwitches? Same Hosts?
I can't say I've seen a scenario where all the servers and clients are in VMs, but I would think it will become more common now.
I would try option 60 and 66, but leave out 67 for now - if correct, the client should pick it's own bootfile.
Let me know how the PXE role repair works out.
I can't say I've seen a scenario where all the servers and clients are in VMs, but I would think it will become more common now.
I would try option 60 and 66, but leave out 67 for now - if correct, the client should pick it's own bootfile.
Let me know how the PXE role repair works out.
ASKER
PXE role repair did nothing...
I also removed option 67 to test . Still nothing
I am getting PXE-E21 still..
nothing in the PXE log either.
I also removed option 67 to test . Still nothing
I am getting PXE-E21 still..
nothing in the PXE log either.
Is there any option on your HP switches for something similar to portfast in Cisco?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
THATS IT!!!!
Solution was to completely remove Option 60,66,67 and It started working.
Now i just need to setup ip-helpers.
Solution was to completely remove Option 60,66,67 and It started working.
Now i just need to setup ip-helpers.
What switches are you using for the infrastructure?
Are you using vLans?
Are your WDS and DHCP servers on the same subnet?
If using iphelpers to DHCP and bootp relay to WDS, then you don't need to provide any DHCP options to clients. Using a combination of iphelper and DHCP options is sure to cause havoc.
The client booting will select the correct bootfile (or it should anyway).