精心封装过的winpe在进行系统维护时非常方便深受大家的喜欢,在以前启动winpe时 一般都是通过硬盘/U盘/光盘来进行,后期grub4dos 和syslinux 都已经开始支bootp 的标准了,为我们通过网络远程启动winpe 提供便捷,而且目前绝大多数的主板集成网卡都支持PXE ,因此现在国内玩PXE 网启winpe 的朋友也越来越多了;
要想winpe 可以远程从网络启动(PXE 启动),除了需要有网络引导程序(NBP)和winpe 本身的支持外,还要有一套更重要的服务/协议来为pxeclient的引导启动提供支持,它们就是DHCP/TFTP ;DHCP与TFTP 的配置以往会比较复杂一般要在server 系统才有支持,后来也有流传一些经典的集成工具,仅一个小程序就可以完成所有的工作,比如大家常用的:tftp32.exe ;
我看见很多论坛上玩网启的朋友用的也都是这个工具,但是此工具原本是英文版的后又经国内汉化,其功能设计与界面布局上都难以满足专业用户的需要,今天我在测试多引导切换启动时就采用了国内深度论坛新推出的一款 ,它似乎对pxe 启动的支持做了很多人性化功能,方便大家在多机情况配置多启动。
下面我将演示使用grub4dos(grldr ) 和syslinux(pxelinux.0) 同时启动
软件主界面如下图:
选择服务器右键菜单点; 如下图:
可以弹出对话框, 在这里面可以对 DHCP 的相关参数进行设置;
DHCP分配IP 的启止范围: 192.168.10.100~192.168.10.250
子网掩码:255.255.255.0
网关:192.168.10.1
正常情况这些参数该软件在运行时是可以根据环境自动生成的,如有需要可以自己的情况进行配置,但是在手工设置时要注意防止地址冲突,否则会影响到客户机无法从PXE 正常启动。
如下图:
在“启动配置”中可以对进行配置, 这里的启动文件指是就是将要由PXE 客户机TFTP 下载执行的引导文件。 比如大家常用的grldr
在这里配置的“启动文件”为默认启动文件,所有新开启的PXE 启动工作机在连接到此时都将以该引导文件进行启动。

而实际上,这款“远程启动管理器”最大的特点就是支持多启动,即我们可以建立多个启动分组,每个分组设置一个“启动文件(NBP)”,需要启动的客户机则可以分别加入到这些启动分组中,以不同的引导文件分别启动不同的系统。
为此我们可以在主界面左侧的树型列表“引导分组”上鼠标右键菜单选
弹出对话框,如下图:
这里可以设置新的启动文件; 注册工作目录 必须正常设置,特别是以TFTP单个单个文件传输启动WINPE 时,工作目录设置错误会导致无法正常加载文件;

基本设置到此结束。
下面我开启一台客户机,设置从PXE 网卡启动;
工作站从发出DHCP 请求到出现grub4dos 的菜单仅用三秒,确实速度非常快;

这里的grub4dos 菜单是事先编写好的,国内很多论坛上都有关于编写menu.lst 的教程和示例, 这个菜单也是改过的。 这个菜单中的启动winpe 是以网络加载ISO 文件的方式启动,从理论上只要支持光盘启动的pe 就可以直接以ISO 方式启动,不需要改造winpe 的文件。
title 从ISO启动Deepin_WinPE
map --mem (pd)/Deepin_PE4.iso (hd32)
map --hook
chainloader (hd32)
boot
这个加载的过程,根据ISO 文件的大小而异,有时会稍慢一些

启动到PE 桌面了。
刚才上面我们是以默认的grldr 引导的,加载的是winpe 的一个ISO文件,下面我们再试一下用pxelinux.0 来引导,换另一种方式启动winpe
之前我们已经在“引导分组”中新建了一个pxelinux 的分组,在这里只需要把这台客户机“拖动”到该分组上即可。
也可以在鼠标右键菜单上加入到该分组;
重启客户机,这个时候客户机就是以pxelinx.0 为启动文件,进行网络启动,其启动相关配置由pxelinux.0 的菜单文件来设置,我也只把别人配好的直接拷贝。
LABEL 03PE
MENU LABEL 启动 WIN03 PE 系统
MENU DEFAULT
kernel /BOOT/STARTROM.0
这样,另一方式winpe 也网启成功了;
于是,我在网上又找了几个高人们封装的winpe 包, 新建了几个新的引导分组,设置了对应的引导文件。(从网上下载的封装好的winpe 一般会自带引导文件和菜单文件,按说明填写即可)
改变客户机的引导分组,重启;
切换不同的引导分组,均能正常按指定的启动文件分别启动,十分方便。

grub4dos 和 pxelinux 的菜单编写知识和winpe 的封装,并不在本文的讨论范围,以前没有做过的网启动的朋友可以在网上搜一下,就可以找到很多高人做好的文件直接使用,相关介绍文章也很多, 以前一直使用tftp32.exe 玩网启winpe的熟手们这就不用多说了,希望可以都来体验一下这款工具,支持国产支持原创。愿这款在大家工作、学习和封装测试过程中带来方便。
Last edited by hbxfwjww on 2010-7-13 at 17:52 ]
Well-packaged WinPE is very convenient for system maintenance and is well-liked by everyone. In the past, WinPE was generally started through hard disks/USB drives/cd - ROMs. Later, grub4dos and syslinux have started to support the bootp standard, which provides convenience for us to remotely start WinPE through the network. And currently, most motherboards' integrated network cards support PXE, so more and more friends in China are playing with PXE network - booting WinPE;
To make WinPE can be remotely started from the network (PXE boot), in addition to the need for network boot programs (NBP) and the support of WinPE itself, there is also a more important set of services/protocols to support the boot of PXE clients, which are DHCP/TFTP; The configuration of DHCP and TFTP used to be relatively complex and generally only supported in server systems. Later, some classic integrated tools have been spread, and just one small program can complete all the work, such as the commonly used tftp32.exe;
I see that many friends playing with network boot on forums also use this tool, but this tool was originally in English and then was localized by domestic users. Its functional design and interface layout are difficult to meet the needs of professional users. Today, when I was testing multi - boot switching boot, I used a newly launched "Remote Boot Manager" from the domestic Deepin Forum. It seems that it has done a lot of user - friendly functions for PXE boot support, which is convenient for everyone to configure multi - boot in multi - machine situations.
Next, I will demonstrate using grub4dos (grldr) and syslinux (pxelinux.0) to start simultaneously
The main interface of the software is as follows:
Right - click the server in the menu and select ; As shown in the following figure:
The dialog box can be popped up, and the relevant parameters of DHCP can be set here;
The start - stop range of DHCP - assigned IP: 192.168.10.100~192.168.10.250
Subnet mask: 255.255.255.0
Gateway: 192.168.10.1
Under normal circumstances, these parameters can be automatically generated by the software during operation. If necessary, they can be configured according to the situation, but when setting manually, attention should be paid to preventing address conflicts, otherwise it will affect the normal boot of the client from PXE.
As shown in the following figure:
In "Boot Configuration", the can be configured. The boot file here refers to the boot file that will be downloaded and executed by the PXE client via TFTP. For example, the commonly used grldr
The "Boot File" configured here is the default boot file, and all newly started PXE boot workstations will start with this boot file when connecting to this.

In fact, the biggest feature of this "Remote Boot Manager" is that it supports multi - boot, that is, we can establish multiple boot groups, each group sets a "Boot File (NBP)", and the clients that need to boot can be added to these boot groups respectively to boot different systems with different boot files.
For this, we can right - click the "Boot Group" in the tree - type list on the left of the main interface and select
The dialog box is popped up, as shown in the following figure: Here, the new boot file can be set; The registration working directory must be set normally, especially when starting WINPE by transferring files one by one via TFTP, if the working directory is set incorrectly, it will lead to the failure to load files normally;

The basic settings are over here.
Next, I start a client and set it to boot from the PXE network card;
It only takes three seconds from the workstation sending the DHCP request to the appearance of the grub4dos menu, which is really very fast;

The grub4dos menu here is written in advance. There are many tutorials and examples about writing menu.lst on many domestic forums. This menu has also been modified. The way to start WinPE in this menu is to start by loading the ISO file over the network. In theory, as long as the PE that supports CD - ROM boot can be started directly in ISO mode, and there is no need to transform the files of WinPE.
title Start Deepin_WinPE from ISO
map --mem (pd)/Deepin_PE4.iso (hd32)
map --hook
chainloader (hd32)
boot
The loading process depends on the size of the ISO file. Sometimes it will be a little slower

Booted to the PE desktop.
Just now, we were booted with the default grldr, and an ISO file of WinPE was loaded. Next, we will try to use pxelinux.0 to boot and start WinPE in another way
We have already created a pxelinux group in the "Boot Group" before. Here, we only need to "drag" this client to this group.
It can also be added to this group in the right - click menu;
Restart the client. At this time, the client will use pxelinx.0 as the boot file to start over the network, and the relevant boot configuration is set by the menu file of pxelinux.0. I just copied the configured one directly.
LABEL 03PE
MENU LABEL Start WIN03 PE System
MENU DEFAULT
kernel /BOOT/STARTROM.0
In this way, WinPE is successfully network - booted in another way;
So, I found several WinPE packages encapsulated by experts on the Internet, created several new boot groups, and set the corresponding boot files. (The encapsulated WinPE downloaded from the Internet generally comes with boot files and menu files, just fill in according to the instructions)
Change the boot group of the client and restart;
Switching different boot groups can all start normally according to the specified boot files respectively, which is very convenient.

The knowledge of writing grub4dos and pxelinux menus and the encapsulation of WinPE are not within the scope of this article. Friends who have not done network boot before can search on the Internet, and many ready - made files made by experts can be directly used. There are also many relevant introduction articles. For those who have been using tftp32.exe to play with network - booting WinPE for a long time, there is no need to say more. I hope everyone can experience this tool, support domestic products and original creations. May this tool bring convenience to everyone's work, study and encapsulation testing.
Last edited by hbxfwjww on 2010-7-13 at 17:52 ]