Provisioning Services 7.8 Introductory Series tutorial 14 UEFI support and Bootptab editor

continued provisioning Services 7.8 Introductory series Tutorial 13 using Boot Device Management (BDM)

UEFI, full name unified extensible Firmware Interface, or "Unified Extensible Firmware Interface", is a standard specification for a new type of interface, a standard firmware interface for computers, designed to replace the BIOS (basic input/output system). This standard was created by more than 140 technology companies in the UEFI Alliance, including Microsoft Corporation. UEFI is designed to improve software interoperability and address BIOS limitations.

UEFI starts with the following features compared to the traditional BIOS boot:

1. Improve security by protecting pre-boot or pre-boot processes against Bootkit attacks.
2, shorten the start time and resume from the sleep state time.
3. Supports drives with capacity exceeding 2.2 TB.

booting a computer using UEFI requires both hardware and operating system support . The current computer hardware (mainly motherboards) supports both boot modes, and some operating systems, such as Windows 2003,XP, do not support UEFI installations, and operating systems such as Windows 2012,windows 10 support.

One, PVS support for UEFI

It should be said that in the actual production environment there may be two kinds of startup mode coexistence phenomenon, and these two boot methods need to download the boot program is not the same. The traditional boot mode requires ardbp32.bin files, and the UEFI boot needs to be Pvsnbpx64.efi.

In previous versions of PVS, the simultaneous presence of two boot files brought some complexity to the network topology. Because under the same scope, the DHCP server can only set a boot file name (067 option). Therefore, in order to meet the actual needs, the user

Can only be resolved in two ways:

1. If DHCP option 67 is selected, there are two topology options:

On a single segment, use DHCP reservation to specify the bootstrapper file name for each target device (option 67). This applies to smaller environments, but can be quickly scaled to suit the enterprise environment.

Separate the environment into segments to isolate legacy devices from UEFI devices. For each segment, establish a scope in the DHCP server by setting the corresponding option 67.

2, the user can also establish the way of Bootptab database, to distinguish the starting mode of each device. for this, see the following Bootptab file introduction.

PVS 7.8 provides good technical support for both of these startup modes and the phenomenon. The user only needs to establish the appropriate options in the DHCP scope options:

Establish DHCP options 11–RLP server

Option 11 allows you to specify multiple IPV4 addresses. Use this option to specify the address of the stream NIC on the Provisioning Services server. You can specify more than four addresses. The UEFI bootstrapper reads all addresses and then uses a round robin mechanism to select an address to connect to.

Note: Option 17 has a higher priority than option 11.

Establish DHCP option 17– boot path

The boot path option is typically used in conjunction with ISCSI to specify which servers and virtual disks to start. Provisioning Services uses the following format to specify the server address:

Pvs:[:17:]

pvs– the required identifiers

Address of the streaming NIC on the ipv4–provisioning Services server

17–UDP protocol identifier (this parameter is required if a login port is specified)

port– Login Port (this port is not required if default port 6910 is used)

Example:

pvs:192.168.0.213

pvs:192.168.0.213:17:7800

In order to be familiar with the operation process, I added a virtual machine in Hyper-V as the target device, installed Windows R2, and produced the image, the virtual disk is win12u.

Note that in order to implement UEFI boot, you should select the algebra of the virtual machine as "second generation".

650) this.width=650; "title=" DSS061 "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" DSS061 "src=" http:// S3.51cto.com/wyfs02/m01/80/12/wkiom1c2b2xtwsqkaaeemgeqvl8007.jpg "height=" 538 "/>

Other process slightly.

Results and questions:

The author creates a new virtual machine, which is used as a test device and is added to PVs. After booting through the network, such as

650) this.width=650; "title=" DSS060 "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" DSS060 "src=" http:// S3.51cto.com/wyfs02/m01/80/0f/wkiol1c2ceqjqmabaadw7r0q81o482.jpg "height=" 531 "/>

As you can see, the device downloaded the boot file pvsnbpx64.efi.

However, the device does not start properly, and the following error always occurs:

Bnistack failed, network stack could not be initialized

Workaround: Remove the hidden network adapter from Device Manager by querying on the network.

However, the author can not succeed through numerous increases.

Interestingly, although other new devices cannot be started, the original target device (the device that produced the UEFI image) is changed directly to boot from the virtual disk and can be successful.

So I finally think that this is probably the problem of hardware in Hyper-V virtual environment.

Above fault hope that the majority of users help solve.

Second, about the Bootptab editor

Users can use the Bootptab file to associate a target device with a specific bootstrapper. The Bootptab Editor is a utility for creating, editing, and maintaining entries in the Bootptab database file.

The format of the Bootptab file is as follows:

: ha=:ar=:bf=

Example:

Host001:ha=001122334455:ar=0:bf=ardbp32.bin

Host002:ha=554433221100:ar=7:bf=pvsnbpx64.efi

If an architecture flag is missing, the default value is 0.

The "AR" tag specifies the architecture of the target device's boot environment.

When ar=0, the architecture is x86 BIOS, the boot program is named Ardbp32.bin;

When ar=6, the architecture is x86 UEFI, the boot program is named Pvsnbpia32.efi;

When ar=7, the architecture is x64 UEFI, the boot program is named Pvsnbpx64.efi;

Ha=mac address, in a PXE environment, sometimes wildcard characters are used to represent the MAC addresses of multiple groups of client PCs, eliminating the need for a single 12-bit address.

bf= the boot program name.

At this point, the entire series of tutorials is finally complete. As I have written earlier, the whole tutorial does not, and do not want to have too many theories, in fact, I do not understand too much theory. Just want to highlight the actual operation, record the deployment process.

Only hope for those who "past me", with the IT dream of "those people", helpful, so enough!

This article is from the "Start from the Heart" blog, please be sure to keep this source http://ycrsjxy.blog.51cto.com/618627/1773214

Provisioning Services 7.8 Introductory Series tutorial 14 UEFI support and Bootptab editor