189 8069 5689
系统运维
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.
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.
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:
Click ‘OK’ Click ‘Add’ Click ‘OK’ Click ‘Add’ Click ‘OK’ Creating Custom DHCP Policies Right-Click ‘Policies’ and click ‘New Policy’ Give the policy a friendly name that coincides with the yourvendor class naming scheme: Click ‘Next’ On the ‘Configure Conditions for the policy’ page click‘add’ Select the ‘Value’ drop-down box and selectthe Ensure that you check the box 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: Cick ‘Next’ On the 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: Click ‘Next’ On the ‘Configure Conditions for the policy’ page click‘add’ Select the ‘Value’ drop-down box and selectthe Ensure that you check the box 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: Cick ‘Next’ On the UEFI 32-Bit DHCP Policy Right-Click ‘Policies’ and click ‘New Policy’ Give the policy a friendly name that coincides with the yourvendor class naming scheme: Click ‘Next’ On the ‘Configure Conditions for the policy’ page click‘add’ Select the ‘Value’ drop-down box and selectthe Ensure that you check the box 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: Cick ‘Next’ On the Remove Default PXE Options Ensure that you have removed the 067, 066, 060 options from thedefault scope options to ensure that the Policies take precedenceotherwise you will end up with conflict As long as you have configured everything correctly you should nowhave the ability to boot machines from BIOS orUEFI. Hopefully this helps alleviate some of the stress surroundingyour PXE deployments. This has worked great on all of ourdistribution points since implementation and has allowed ourdeployments to be much more flexible.
分享文章：如何使SCCM同时支持BIOSPXEBoot和UEFIPXEBoot
网站路径：http://cdxtjz.cn/article/cgjdse.html