如何使SCCM同时支持BIOS PXE Boot 和 UEFI PXE Boot
发布时间：2024-12-11 点击：167
系统运维
learn how to pxe boot both bios &uefimachines with dhcp policies and custom vendor classes
one of the challenges that an it deployment administrator mayface in the field is the ability to boot both bios and uefimachines from the same wds environment. this is exactly the issue ifaced when our organization decided to purchase a number of newsurface devices. these were the first set of devices that wereconfigured to natively boot to uefi. this leaves you to decide froman organization standpoint whether you wish to boot all yourdevices using uefi or the legacy bios…or does it.
i am a strong believer that finding a workaround to a problem isnot a fix to the problem. to that end modern devices such as thesurface are meant to be booted using the native uefi boot. however,many organizations may also still have legacy bios devices that donot support uefi boot or just work better booting from bios.whatever the reasoning behind this it is actually quite easy tosetup dhcp to provide the bios or uefi boot file depending on whatis used.
the solution!
by using dhcp policies and custom vendor classes for the followingdhcp options:
option 60
option 66
option 67
the below assumes that you have sccm configured with a pxe enableddistribution point and a valid and configured dhcp server. youshould therefore be at a configured state where you are able to pxeboot bios based devices.
create custom vendor classes for use with your dhcppolicy
think custom vendor classes as detection method’s used to determinehow devices are requesting a boot image from the dhcp server.
open the dhcp console and expand the ipv4 node
right-click on ‘ipv4 node’ and select ‘define vendorclasses’
click ‘add’
create the uefi 64-bit vendor class first by entering thefollowing information
enter the following information for the respectivefields:
displayname:pxeclient (uefi x64)
description:pxeclient:arch:00007
ascii:pxeclient:arch:00007
click ‘ok’
click ‘add’
displayname:pxeclient (uefi x86)
description:pxeclient:arch:00006
ascii:pxeclient:arch:00006
click ‘ok’
click ‘add’
displayname:pxeclient (bios x86&x64)
description:pxeclient:arch:00000
ascii:pxeclient:arch:00000
click ‘ok’
creating custom dhcp policies
uefi 64-bit dhcp policy
right-click ‘policies’ and click ‘new policy’
give the policy a friendly name that coincides with the yourvendor class naming scheme:
policyname: pxeclient (uefi x64)
description: delivers the correct bootfile for (uefix64)
click ‘next’
on the ‘configure conditions for the policy’ page click‘add’
select the ‘value’ drop-down box and selectthepxeclient (uefix64)vendor class that you created in previoussteps
ensure that you check the box‘appendwildcard(*)’
select ‘add’
select ‘ok’
click ‘next’
if you want the policy to affect only a specific range withinyour scope configure it, otherwise select no and click ‘next’
on the configure settings for the policy page ensure that ‘dhcpstandard options’ is selected from the drop down box
configure the following scope options:
060: pxeclient
066:ip address of the sccm or wdsservice
067: smsboot\\\\x64\\\\wdsmgfw.efi
cick ‘next’
on thesummarypageclick ‘finish’
bios 32-bit &64-bit dhcppolicy
right-click ‘policies’ and click ‘new policy’
give the policy a friendly name that coincides with the yourvendor class naming scheme:
policyname: pxeclient (bios x86&x64)
description: delivers the correct bootfile for biosmachines
click ‘next’
on the ‘configure conditions for the policy’ page click‘add’
select the ‘value’ drop-down box and selectthepxeclient (bios x86&x64)vendor class thatyou created in previous steps
ensure that you check the box‘appendwildcard(*)’
select ‘add’
select ‘ok’
click ‘next’
if you want the policy to affect only a specific range withinyour scope configure it, otherwise select no and cl
云服务器脚本挂机
现在我们找了一家运维公司杀毒
代理服务器是什么?一文看懂什么是代理服务器?
腾讯虚拟云服务器怎么老是掉线连不上网
虚拟主机无法打开-其他问题
微信商城小程序怎么做
阿里云服务器怎么加office
开启百度云加速-虚拟主机/数据库问题
learn how to pxe boot both bios &uefimachines with dhcp policies and custom vendor classes
one of the challenges that an it deployment administrator mayface in the field is the ability to boot both bios and uefimachines from the same wds environment. this is exactly the issue ifaced when our organization decided to purchase a number of newsurface devices. these were the first set of devices that wereconfigured to natively boot to uefi. this leaves you to decide froman organization standpoint whether you wish to boot all yourdevices using uefi or the legacy bios…or does it.
i am a strong believer that finding a workaround to a problem isnot a fix to the problem. to that end modern devices such as thesurface are meant to be booted using the native uefi boot. however,many organizations may also still have legacy bios devices that donot support uefi boot or just work better booting from bios.whatever the reasoning behind this it is actually quite easy tosetup dhcp to provide the bios or uefi boot file depending on whatis used.
the solution!
by using dhcp policies and custom vendor classes for the followingdhcp options:
option 60
option 66
option 67
the below assumes that you have sccm configured with a pxe enableddistribution point and a valid and configured dhcp server. youshould therefore be at a configured state where you are able to pxeboot bios based devices.
create custom vendor classes for use with your dhcppolicy
think custom vendor classes as detection method’s used to determinehow devices are requesting a boot image from the dhcp server.
open the dhcp console and expand the ipv4 node
right-click on ‘ipv4 node’ and select ‘define vendorclasses’
click ‘add’
create the uefi 64-bit vendor class first by entering thefollowing information
enter the following information for the respectivefields:
displayname:pxeclient (uefi x64)
description:pxeclient:arch:00007
ascii:pxeclient:arch:00007
click ‘ok’
click ‘add’
displayname:pxeclient (uefi x86)
description:pxeclient:arch:00006
ascii:pxeclient:arch:00006
click ‘ok’
click ‘add’
displayname:pxeclient (bios x86&x64)
description:pxeclient:arch:00000
ascii:pxeclient:arch:00000
click ‘ok’
creating custom dhcp policies
uefi 64-bit dhcp policy
right-click ‘policies’ and click ‘new policy’
give the policy a friendly name that coincides with the yourvendor class naming scheme:
policyname: pxeclient (uefi x64)
description: delivers the correct bootfile for (uefix64)
click ‘next’
on the ‘configure conditions for the policy’ page click‘add’
select the ‘value’ drop-down box and selectthepxeclient (uefix64)vendor class that you created in previoussteps
ensure that you check the box‘appendwildcard(*)’
select ‘add’
select ‘ok’
click ‘next’
if you want the policy to affect only a specific range withinyour scope configure it, otherwise select no and click ‘next’
on the configure settings for the policy page ensure that ‘dhcpstandard options’ is selected from the drop down box
configure the following scope options:
060: pxeclient
066:ip address of the sccm or wdsservice
067: smsboot\\\\x64\\\\wdsmgfw.efi
cick ‘next’
on thesummarypageclick ‘finish’
bios 32-bit &64-bit dhcppolicy
right-click ‘policies’ and click ‘new policy’
give the policy a friendly name that coincides with the yourvendor class naming scheme:
policyname: pxeclient (bios x86&x64)
description: delivers the correct bootfile for biosmachines
click ‘next’
on the ‘configure conditions for the policy’ page click‘add’
select the ‘value’ drop-down box and selectthepxeclient (bios x86&x64)vendor class thatyou created in previous steps
ensure that you check the box‘appendwildcard(*)’
select ‘add’
select ‘ok’
click ‘next’
if you want the policy to affect only a specific range withinyour scope configure it, otherwise select no and cl
云服务器脚本挂机
现在我们找了一家运维公司杀毒
代理服务器是什么?一文看懂什么是代理服务器?
腾讯虚拟云服务器怎么老是掉线连不上网
虚拟主机无法打开-其他问题
微信商城小程序怎么做
阿里云服务器怎么加office
开启百度云加速-虚拟主机/数据库问题