Categories
Planning

How to network boot the bitdefender rescue cd (pxe)

About

The PXE environment allows you to boot a computer with SystemRescue even if this computer has no CDRom drive or USB socket. It allows you to boot SystemRescue from the network, and then it is faster to troubleshoot computers on your network once a PXE-boot-server is installed. It is also useful if you want to boot a computer that has no optical drive (CD or DVD) or to troubleshoot a remote computer to which you have no physical access to insert the disc.

Instructions provided below correspond to files from the 64 bit version (amd64/x86_64) of SystemRescue. If you use the 32 bit version you need to replace all instances of x86_64 with i686 .

Requirements

  • Servers to provide PXE services including DHCP with SystemRescue files available to serve clients requests
  • A client computer with a PXE able network card on the same network and enough memory to fully store SystemRescue files

How the PXE boot process works

The PXE boot server

The PXE boot server is made of three stages:

  • stage0: the PXE-booting client sent an extended DHCPDISCOVER
  • stage1: the DHCP server send an IP address to the client and supplementing information such as the TFTP server
  • stage2: the PXE-booting client configures the network and requests the first boot files from the TFTP server (boot loader, kernel image and sysresccd.img)
  • stage3: the PXE-booted client requests the squashfs root file system image from the HTTP or NFS or NBD server

These three parts can be installed either on a single machine or on several computers.

The PXE boot process

You may need to understand what happens when you boot SystemRescue from the network. You will need this knowledge for troubleshooting in case of problems. Here are the most important steps of the PXE boot process:

  • When the client computer tries to boot with PXE, it first emits a DHCP request on the network to get an IP address.
  • Then a DHCP server replies with a DHCP offer that contains a new IP address that was not already allocated and some specific options (DNS, default route) and the IP address of the TFTP server
  • The client receives this DHCP offer and accepts it. It connects to the TFTP server (it received its IP address in the previous stage) to get the boot loader files.
  • The TFTP server sends the boot loader files ( pxelinux ) and the text files displayed on the screen by pxelinux .
  • The client displays the pxelinux prompt, and the user can choose the boot options. It then requests from the TFTP server the kernel and initramfs files necessary to boot the system
  • The TFTP server sends the kernel and initramfs files (eg: vmlinuz + sysresccd.img ) to the client
  • The client boots this kernel and executes the init programs that come with the initramfs.
  • During its initialization the kernel makes a DHCP request again because of the ip=dhcp kernel boot parameters. Indeed the kernel does not know the IP address used by the computer at the pxelinux stage.
  • The client needs the airootfs.sfs file. If you use HTTP or TFTP for the third stage, then airootfs.sfs will be downloaded into RAM so the client has to have enough memory (estimated requirement: 1GB). If you use either NFS or NBD then you don’t have this memory requirement and the client will make permanent requests to the server each time it needs a file from the root filesystem.
  • The client mounts airootfs.sfs and it can now complete the boot process.
  • At this stage the client holds all the files in memory, if you used TFTP/HTTP for the third stage, so it does not require a boot server any more. If you are using NFS or NBD, the connection is still required.

Customization of the boot command line

The PXE server is made of several services. In the second stage, the server uses TFTP to send multiple things to the client: boot loader (pxelinux.0), kernel image (vmlinuz), initramfs (sysresccd.img). The boot loader is pxelinux.0 and it comes with a configuration file which is sent to the client. This configuration file contains the boot command line which will be used by the client to start the Linux kernel. This command line is important since it contains the SystemRescue boot options that are required to run the third stage. The boot command line can be used to specify the network settings and the method that the PXE client will use in the third stage of the PXE boot process. Here are two examples of valid command lines for PXE boot:

PXE boot options supported by SystemRescue

SystemRescue is based on Arch Linux since version 6.0 hence it supports PXE boot options implemented by the upstream. These boot options provide support for various protocols (HTTP, NFS, NBD) and are documented on the following page: https://gitlab.archlinux.org/archlinux/archiso/-/raw/v43/docs/README.bootparams

Example of a PXE configuration to boot SystemRescue using TFTP and HTTP

Here is an example of a PXE configuration which allows to boot SystemRescue using TFTP and HTTP only. It is one of the simplest PXE configuration you can have hence it is recommended to follow this example if you want a simple PXE configuration for SystemRescue.

In this example the boot loader is pxelinux.0 and TFTP is used to get the kernel image and initramfs images. It then uses an HTTP server to download the large squashfs file system airootfs.sfs .

When you configure the TFTP server you have to copy the boot loader (pxelinux binary files), a pxelinux configuration file in pxelinux.cfg/default , and you need to copy the sysresccd directory as it is (even though not all files are required by the TFTP server) from the ISO image to provide files that will be requested via TFTP.

Here is the list of all required files and their location on the TFTP server:

And here is the example of a configuration located in pxelinux.cfg/default :

The SYSAPPEND option is important and you need to make sure you are using a recent version of pxelinux as versions older than 5.10 do not support it. Also users of the PXE boot feature are strongly encouraged to use very recent versions of SystemRescue as fixes related to PXE were made in versions 6.1.5 and 6.1.6. Cf PXE boot issues for more details.

You need to update the IP address of the HTTP server from which the squashfs image will be downloaded. In this example it will download this file and its checksum from the following URLs:

Make sure you are able to successfully download these files from a regular web client before you try to boot from PXE. You can customize the boot command line by adding options such as setkmap=us after the checksum option.

Chúng tôi đã chỉ cho bạn cách sử dụng CD cứu hộ BitDefender để dọn dẹp PC bị nhiễm của bạn, nhưng nếu bạn muốn đạt được điều tương tự chỉ khi không có CD qua mạng thì sao? Trong hướng dẫn này, chúng tôi sẽ chỉ cho bạn cách.

Hình ảnh của baronsquirrel

Điều kiện tiên quyết

  • Giả định rằng bạn đã thiết lập máy chủ FOG như được giải thích trong Phần mềm khởi động mạng (PXE) của chúng tôi và Bạn có thể sử dụng nó như thế nào?.
  • Bạn sẽ thấy chương trình VIM Cảnh được sử dụng làm trình chỉnh sửa, điều này chủ yếu là do nó có sẵn rộng rãi trên các nền tảng Linux. Bạn có thể sử dụng bất kỳ trình soạn thảo nào khác mà bạn muốn.

Tổng quan

Trong 10 cách thông minh nhất để sử dụng Linux để khắc phục PC Windows của bạn, một trong những điều chúng tôi đã trình bày là có thể cài đặt phần mềm chống vi-rút và quét máy tính của bạn từ Ubuntu LiveCD. Như đã nói, điều gì sẽ xảy ra nếu bạn muốn chắc chắn rằng máy tính của bạn không bị nhiễm bằng cách quét nó bằng một phần mềm chống vi-rút khác?

Cuối cùng, bạn có thể sử dụng một đĩa CD cứu hộ chống vi-rút khác, và có một số cái mà chúng tôi đã xem xét trong quá khứ như Kaspersky và Avira. Điều thông minh là, điều gì sẽ xảy ra nếu bạn muốn thêm công cụ bổ sung này vào máy chủ PXE của mình, vì vậy bạn sẽ không bao giờ phải tìm CD của tiện ích?

Chúng tôi đã hoàn thành công việc và nhận thấy rằng, mặc dù nó yêu cầu một số bài khởi động TLA, CD cứu hộ BitDefender cho đến nay là dễ dàng nhất để có được PXEable từ các tùy chọn trên.

Trong phần Cách cài đặt mạng Tiện ích có thể khởi động mạng bằng cách sử dụng hướng dẫn PXE, chúng tôi đã hứa rằng chúng tôi sẽ đưa ra một ví dụ khác cho phương thức Kernel + initrd + NFS và chúng tôi sẽ cung cấp. Nguyên tắc ở đây cũng giống như đối với Cách khởi động mạng (PXE) Ubuntu LiveCD.

Chúng tôi sẽ gỡ các tệp ra khỏi CD, làm cho chúng có sẵn thông qua chia sẻ NFS và trỏ máy khách PXE đến chia sẻ NFS này dưới dạng hệ thống tập tin gốc của nó.

Thiết lập phía máy chủ

Những gì bạn sẽ làm là lặp lại các bước được thực hiện trong Hướng dẫn khởi động mạng (PXE) Hướng dẫn Ubuntu LiveCD, đó là:

  • Tải xuống ISO mới nhất từ ​​trang web của bitdefender và đặt nó vào trang web / tftpboot / howtogeek / utils /.
  • Tạo điểm gắn kết:

sudo mkdir -p / tftpboot / howtogeek / utils / bitdefender

/tftpboot/howtogeek/utils/bitdefender-resTHER-cd.iso / tftpboot / howtogeek / utils / bitdefender udf, người dùng iso9660, vòng lặp 0 0

Lưu ý: Mặc dù đại diện, đây là một dòng không bị gián đoạn.
Kiểm tra rằng điểm gắn kết hoạt động bằng cách phát hành:

ls -lash / tftpboot / howtogeek / utils / bitdefender /

/ tftpboot / howtogeek / utils / bitdefender * (ro, sync, no_wdelay, insecure_locks, no_root_squash, không an toàn)

sudo /etc/init.d/nfs-kernel-server khởi động lại

sudo vim /tftpboot/howtogeek/menus/utils.cfg

nhãn BitDefender Cứu hộ trực tiếp
kernel howtogeek / utils / bitdefender / casper / vmlinuz
chắp thêm tập tin / utils / bitdefender

Đó là về phía máy chủ, khách hàng của bạn sẽ sẵn sàng khởi động vào đĩa CD cứu hộ thông qua PXE.

Sử dụng phía khách hàng

Như chúng tôi đã nói trong phần tổng quan, phần mềm chống vi-rút này yêu cầu một số can thiệp, khi bạn thực sự khởi động vào nó bằng PXE so với máy khách được khởi động từ chế độ CD.

Vấn đề nằm ở cách thiết lập / phát hiện mạng khi CD cứu hộ của Linux được khởi động, nhưng cách khắc phục khá đơn giản.

Khi bạn khởi động vào môi trường cứu hộ, bạn sẽ gặp lỗi cập nhật như:

Nhấn OK và đóng tin nhắn này.

Tiếp theo, nhấp vào biểu tượng của Dog Dog để hiển thị menu chương trình.

Khi ở trong thiết bị đầu cuối, đưa ra chỉ huy Midnight với quyền root, bằng cách phát hành:

Khi đã ở vị trí chỉ huy lúc nửa đêm, hãy truy cập vào các tập tin / mạng / vân tay và chỉnh sửa (sử dụng F4).

Tìm dòng đọc hướng dẫn if iface eth0 inet hướng dẫn sử dụng và thay thế hướng dẫn bằng cách sử dụng bằng tiếng Pháp.

Vì vậy, cấu hình cuối cùng của bạn sẽ trông giống như:

Thoát chế độ chỉnh sửa chế độ canh trong khi lưu các thay đổi của bạn bằng cách nhấn vào F10 và chọn Cẩn Có khi nhắc.

Khởi động lại mạng máy khách, bằng cách phát hành:

sudo /etc/init.d/networking khởi động lại

Nếu mọi việc suôn sẻ, bạn sẽ thấy rằng bạn đã có được địa chỉ IP và bây giờ bạn có thể sử dụng chức năng cập nhật của ứng dụng BitDefender.

Từ đây trở đi, các hướng dẫn cũng giống như với Cách sử dụng CD cứu hộ BitDefender để làm sạch hướng dẫn máy tính bị nhiễm của bạn.

Thật dễ dàng khi bạn hiểu rõ về nó và như mọi khi, Tận hưởng PC không có vi-rút của bạn

Hình ảnh chính là của baronsquirrel, phần còn lại được chụp bởi Aviad Raviv.

เราได้แสดงวิธีการใช้ BitDefender Rescue CD ในการล้างเครื่องคอมพิวเตอร์ที่ติดเชื้อของคุณแล้ว แต่ถ้าคุณต้องการทำสิ่งเดียวกันโดยไม่ต้องใช้ CD ผ่านเครือข่าย ในคู่มือนี้เราจะแสดงให้คุณเห็นว่า.

ข้อกำหนดเบื้องต้น

  • สันนิษฐานว่าคุณได้ตั้งค่าเซิร์ฟเวอร์ FOG แล้วตามที่อธิบายไว้ในคู่มือ“ What Is Booting (PXE) และคุณจะใช้งานได้อย่างไร”.
  • คุณจะเห็นโปรแกรม“ VIM” ที่ใช้เป็นตัวแก้ไขส่วนใหญ่เป็นเพราะมันมีอยู่ในแพลตฟอร์ม Linux คุณสามารถใช้โปรแกรมแก้ไขอื่น ๆ ที่คุณต้องการ.

ภาพรวม

ใน 10 วิธีที่ชาญฉลาดในการใช้ Linux เพื่อแก้ไขพีซี Windows ของคุณหนึ่งในสิ่งที่เราได้แสดงคือการติดตั้งโปรแกรมป้องกันไวรัสและสแกนคอมพิวเตอร์ของคุณจาก Ubuntu LiveCD ด้วยวิธีการดังกล่าวจะเกิดอะไรขึ้นถ้าคุณต้องการตรวจสอบให้แน่ใจว่าคอมพิวเตอร์ของคุณไม่ได้ติดไวรัสจากการสแกนด้วยโปรแกรมป้องกันไวรัสอื่น?

ด้วยเหตุนี้คุณสามารถใช้แผ่นซีดีป้องกันไวรัสตัวอื่นและมีบางส่วนที่เราได้ตรวจสอบในอดีตเช่น Kaspersky และ Avira สิ่งที่ฉลาดคือถ้าคุณต้องการเพิ่มเครื่องมือเพิ่มเติมนี้ลงในเซิร์ฟเวอร์ PXE ของคุณดังนั้นคุณจะไม่ต้องมองหาซีดีของยูทิลิตี้อีก?

เราได้ทำมาอย่างถูกต้องแล้วและพบว่าถึงแม้ว่ามันจะต้องใช้ TLA post boot แต่แผ่นซีดี BitDefender Rescue นั้นเป็นวิธีที่ง่ายที่สุดในการรับ PXEable จากตัวเลือกด้านบน.

ในคำแนะนำ“ วิธีการตั้งค่าดิสก์ยูทิลิตี้สำหรับบูตเครือข่ายโดยใช้ PXE” เราได้สัญญาไว้ว่าเราจะให้อีกตัวอย่างหนึ่งสำหรับ“ Kernel + Initrd + NFS method” และเราจะส่งมอบ หลักการที่นี่เหมือนกันกับวิธีการบูตเครือข่าย (PXE) Ubuntu LiveCD.

เราจะนำไฟล์ออกจากซีดีทำให้สามารถใช้งานได้ผ่านการแชร์ NFS และชี้ไคลเอนต์ PXE ไปยังการแบ่งปัน NFS นี้เป็น “ระบบแฟ้มราก”.

การตั้งค่าฝั่งเซิร์ฟเวอร์

สิ่งที่คุณต้องทำคือทำซ้ำขั้นตอนที่ทำในคู่มือวิธีการใช้เครือข่าย Boot (PXE) คู่มือ Ubuntu LiveCD ซึ่ง ได้แก่ :

  • ดาวน์โหลด ISO ล่าสุดจากเว็บไซต์ของ bitdefender และใส่ไว้ใน“ / tftpboot / howtogeek / utils /”.
  • สร้างจุดเมานท์:

sudo mkdir -p / tftpboot / howtogeek / utils / bitdefender

/tftpboot/howtogeek/utils/bitdefender-rescue-cd.iso / tftpboot / howtogeek / utils / bitdefender udf ผู้ใช้ iso9660, ลูป 0 0

หมายเหตุ: แม้จะมีการเป็นตัวแทนนี่เป็นหนึ่งบรรทัดที่ไม่ขาดสาย.
ทดสอบว่าจุดต่อเชื่อมทำงานได้โดยออก:

ls -lash / tftpboot / howtogeek / utils / bitdefender /

/ tftpboot / howtogeek / utils / bitdefender * (ro, sync, no_wdelay, insecure_locks, no_root_squash, ที่ไม่ปลอดภัย)

sudo /etc/init.d/nfs-kernel-server รีสตาร์ท

sudo vim /tftpboot/howtogeek/menus/utils.cfg

ป้ายกำกับ BitDefender Rescue Live
เคอร์เนล howtogeek / utils / bitdefender / casper / vmlinuz
ผนวกไฟล์ = / cdrom / preseed / ubuntu.seed boot = แคสเปอร์ initrd = howtogeek / utils / bitdefender / casper / initrd.gz splash vga = 791 lang = us root = / dev / nfs netboot = nfs nfsroot = / utils / BitDefender

การใช้งานฝั่งไคลเอ็นต์

ดังที่เรากล่าวในภาพรวมโปรแกรมป้องกันไวรัสนี้จำเป็นต้องมีการแทรกแซงเมื่อคุณบูตโดยใช้ PXE กับไคลเอนต์ที่บูตจากโหมดซีดี.

ปัญหาคือวิธีที่เครือข่ายติดตั้ง / ตรวจจับเมื่อมีการบูทซีดีช่วยเหลือของ Linux แต่การแก้ไขนั้นค่อนข้างง่าย.

จากนั้นคลิกที่ไอคอน“ สุนัข” เพื่อเปิดเมนูโปรแกรม.

เมื่ออยู่ในผู้บัญชาการเที่ยงคืนให้ไปที่“ / etc / network” แล้วแก้ไข (ใช้ F4) ไฟล์“ interfaces”.

ค้นหาบรรทัดที่อ่าน“ iface eth0 inet manual” และแทนที่ manual ด้วย“ dhcp”.

ออกจาก “โหมดแก้ไข” ในขณะที่บันทึกการเปลี่ยนแปลงของคุณโดยกดปุ่ม “F10” และเลือก “ใช่” เมื่อได้รับแจ้ง.

หากทุกอย่างเป็นไปด้วยดีคุณจะเห็นว่าคุณได้รับที่อยู่ IP และตอนนี้คุณสามารถใช้ฟังก์ชั่นอัพเดทของแอพพลิเคชั่น BitDefender.

คำแนะนำจะเหมือนกันกับวิธีใช้แผ่นซีดี BitDefender Rescue เพื่อล้างคู่มือพีซีที่ติดไวรัสของคุณ.

ภาพหลักคือโดยยักษ์ใหญ่ส่วนที่เหลือถูกจับโดย Aviad Raviv.

Rescue Disk

A Rescue CD or USB boots with the computer bypassing Windows. It is mainly used when Windows is unable to start, which may be because of various reasons. Some of them are:

  • It is infected with malware.
  • The hard disk has bad sectors. Some of the Windows boot files are present on those sectors, and therefore cannot boot/start.
  • Windows files are corrupt or missing, because of the previous two or some other reasons.

In these cases, a Boot CD/USB can prove to be a lifesaver. It can be helpful in a number of ways. Some of them are:

  • Rescue disks can be used to clean an infected copy of Windows. To remove infections from Windows, Rescue disks provided by antivirus companies can be helpful. These disks let the user connect to the online antivirus database of that company, then scan and remove the infections from the computer.
  • Rescue disks can be used to repair the corrupt Windows installation. Windows lets its users make a recovery drive. This recovery drive can be used to repair or reinstall a corrupt Windows.
  • Rescue disks can be used to backup the data of the host computer to an external storage device. Any Linux distro based CD/USB disk can be used for this purpose.

Bitdefender is one of the best antivirus products for the Windows computers. It consistently occupies the first spot or ranks among the top three positions in most of the independent antivirus tests, reports and surveys.

Creating Bitdefender Rescue CD

Download the Bitdefender Rescue CD .iso file from the following official download link:
http://download.bitdefender.com/rescue_cd/latest/bitdefender-rescue-cd.iso

To create a Rescue CD (or USB), you need to burn the downloaded .iso (image) file on the CD (or USB). In order to burn the .iso to your USB drive (or pen drive or flash drive or thumb drive), you need an image burning software installed on your computer. The recommended software here is Rufus. Download and open Rufus.

Select your USB drive in the Rufus Device menu.

Use MBR partition scheme for BIOS or UEFI. The USB made using this option can run on both types of systems – the older BIOS as well as the newer UEFI.

Keep FAT32 as the File System.

Use the Default Cluster size.

In the Format Options, click the button with the disk icon to browse the iso file that you want to burn on the USB drive. In this case, I’m selecting the Bitdefender Rescue CD iso file.

When the Bitdefender iso has been selected, you’ll notice that the New volume label has automatically changed.

Now’s the time to make sure that the USB you’re going to use is not having any files in it. Because the drive will be formatted at the beginning of the burning process, and all of your files inside the USB drive will be deleted. Also, make sure that you have selected the right USB drive. There may be more than one USB inserted into the system. In such a scenario, you could accidentally delete your files and burn the iso on the wrong drive.

Click the Start button at the bottom of the program window to start the burning process.

The program may ask you to download updates or some important required files. Click Yes to continue.

Again, select the Recommended option, and then click the OK button.

The program displays a final warning message before starting the burning process. Click OK when you’re sure.

The process starts. It may take around 5 minutes to complete the burning process.

Once the process has finished, Rufus will display the READY text in its status bar. You can safely remove the USB drive and Close the program.

Now, you are ready with the Bitdefender Rescue USB.

1 thought on “How to Create Bitdefender Rescue CD Disk for Windows 10, 8.1, 8, 7.”

Please spread the word that the hibernation has tol be turned off in or for Bitdefender and ESET bootales to work with Windows 10. Open command prompt —. Type the commad “pwrcfg /hibernate off”f —-.Then type “exit” and press enter. Restart system with rscue disk.

The lastest rescue-cd, downloaded 17-dec-2018, size=832MB (sorry, I dont see any versionnumber) did not work in win10-64bit.

But an older version, from around October-November,size=667 MB did work.(Since this worked, I could see it was version AVCORE v2.1. 11.0.1.18(aug 9, 2017))

I formated the pen with fat32 in both cases. After I had the version v2.1. 11.0.1.18 up and running, i tried again with the new version, but nope, it does not work.

The new version loads until the language selection(only english, and troubleshooting) Then it outputs this error:

!!/dev/loop0 is an invalid root device

!!could not find the root block device in .

!!please specify another value or:

-press Enter for the same

-type shell for a shell

A novice, like me had to figure out a couple of things, that I might as well share:

-For a new system with UEFIbios, its necessary to enable (I am talking about a Lenovo-bios, its proberly similar names for other bios´) CSM(compatibility Module Support) and disable “secure boot”. For me, when enabling CSM, the bios automatically disabled “secure boot”. And the other way around, enabling “secure boot” again, would disable CSM. But it has to be in the right order, disabling “secure boot” first is NOT enough, CSM must be manuel enabled. For me the paths where:

I also disabled Devices\Network Setup\Boot agent(PXE startup), because that dosent sound right, that a home-pc can boot from the networkcard.

Comments

I tried that but I still get the message of invalid boot device. please help. the bios of the computer i was trying to scan doesnt have the CSM option but i disabled the secure boot and still get the message.

The way I interpret the interdependency between the “secure boot”-setting and the “CSM”-setting, is like this:

The “secure boot” functions like an umbrella/parent/global -setting, where the “CSM”-setting is just a child-object. This way, if you see the “secure boot” is enabled, you know all its child-objects are also on tight security. But if you disable “secure boot”, it will not loosen security on all its child-objects. That would be too radical I guess.

So you have to find the relevant child-object, and relax its security. I suspect its name would be something like CSM/compatibility boot/legacy boot/legacy support/insecure boot/or something similar. If you do this, the “secure boot” will automatically become disabled, as it can no longer garantee the full security level, and the “secure boot” dont wont to make false announcement.

Boot security like this, is not particular important for my own home-pc, because I dont expect people who come to my home will be trying to boot my pc on an independent boot operating system. But I could see this as relevant in a business enviroment, where you dont want a random person booting on an usb-pen.

Remember, this is just my own interpretation, from what I experienced on my own Lenovo-bios. I could be wrong, or things could be different on other Bios´.

We’ve discontinued our rescue CD software and no longer support it, however, it’s functions have been baked into our classic line of products. You can read more about the new Rescue Environment in our user guide below:

Table of Contents

Other Tutorials you might like:

also checkout this free PXE software from Aomei Technology – easy to setup up but only supports one boot image at any one time. (thanks to ‘Jack‘ for the heads up on this one!).

INTRODUCTION

This makes installing Windows XP, 2003, Vista, Win 7, Win 8 or Win 2K8 via PXE very easy!

It is called Serva and can be found here. It does NOT require the Windows WAIK to be installed and is quite a small download – with it you can set up a RIS and WDS server on your Windows PC and you don’t need to even touch any existing DHCP server or router!

The instructions are easy to follow, but here is what I did to get PXE booting and a Windows 7 install going in just 5-15 minutes!

MY SETUP

I have a typical home network – an ADSL router which has four Ethernet ports (and a wireless aerial) and a Windows 7 PC. The target PXE boot PC was an Asus netbook.

Windows PC Dlink ADSL router + 4 port hub any other PXE-boot capable computer

(Win 7 + Serva PXE & TFTP Server) (PXE client) Unsupported embed

QUICK HOW TO

1. Download Serva from the Serva website (the Community version is free)

2. Run the download to unpack and copy the Serva files to any convenient folder on your Windows hard disk (you might like to make a link on your Desktop to the exe)

3. Create a C:\SERVA_ROOT empty folder.

4. Run Serva.exe and click on the Settings button at the bottom (if you get a Windows FireWall warning then ALLOW the program access through the firewall).

5. Click on the TFTP tab and set the Root directory to C:\SERVA_ROOT and tick the TFTP Server box as shown below:

6. Click on the DHCP tab and set proxyDHCP (if you already have a DHCP server or DHCP router)and tick the BINL box.

7. Quit the app and re-run the Serva.exe app again. This is necessary because when Serva re-starts it will generate the PXE download files according to what folders you have created. Serva only does this when it starts. If you make any changes to the folders under C:\SERVA_ROOT then you should always quit and re-run Serva before you try a PXE boot.

8. Check that there are now some folders underneath the C:\SERVA_ROOT folder.

9. Set up a Windows share to the C:\SERVA_ROOT\WIA_WDS folder and after that, use the Windows Advanced Properties dialogue (click on the folder and then click Properties – Sharing) to set access for Everyone and set the Share name to WIA_WDS_SHARE.

10. Copy the contents of your Windows 7 (or Win8/10 or Vista or Server 2K8R2) DVD to a new folder – e.g. copy a Win 7 SP1 32-bit install DVD to C:\SERVA_ROOT\WIA_WDS\Win7_32_SP1

11. If you have more DVDs, just make a new folder for each of them under C:\SERVA_ROOT\WIA_WDS

12. If you have NT OS source files (e.g. 2003, XP or Server2K8 non-R2) then put these under C:\SERVA_ROOT\WIA_RIS and share the C:\SERVA_ROOT folder as WIA_RIS_SHARE (see doc on website). Make sure “Everyone” group has read permission on the just created share. You also need to set a Null Session share on the C:\SERVA_ROOT folder.

13. Quit the Serva app and re-run it

14. Now try to PXE boot your target system

15. For a WDS install (Vista, Win7,Win8, WIN10, SVR2K8R2), you will be prompted for a username and password – use your host PC computername\username and password – e.g. mynewHP\Administrator myhppwd.

That’s it – now try to PXE boot a system over Ethernet.

I would recommend using a Windows 10 32-bit or 64-bit install folder (copy of the install DVD) to start with as these will have the most network drivers in them already and will work on any CPU. The troubleshoooting documentation on the Serva website explains how to add OS network drivers if the standard Microsoft install files do not already contain the correct network driver for your target systems.

TROUBLESHOOTING

  • After connecting the network cable, watch the Windows SystemTray network icon – wait until the icon animation has stopped (usually 1-2 minutes) before you attempt to start Serva.
  • If you having problems, try disabling the Windows Firewall on your PC and temporarily stopping your Anti-Virus protection,.
  • If you are using a router as a hub, disconnect any other Ethernet cable except for the target PXE system and your Serva Windows PC.
  • Try a different PXE client notebook or PC – some PXE BIOSes are buggy (not all PXE BIOS ROMs support proxyDHCP PXE booting)!
  • If it starts to load the OS installation files and then stops with an error message – see here.
  • If you are installing XP and you just see the black screen with the XP logo, make sure you have set up the Share on the C:\SERVA_ROOT folder correctly and followed the Null Session share instructions.
  • If the client is having communication problems with the Serva host PC (e.g. PXE client is not receiving the DHCP offer or lots of timeouts, etc.) try switching off and on your router – if still no joy, switch off your host PC, client PC and router. Then switch on the router, wait 1 minute and the switch on your host PC. Now try again!

Note: grldr and grub.exe will not work if the PXE server is using proxyDHCP mode. Grub4dos does not currently support this feature. To use grub4dos your PXE server must also be the DHCP server (i.e. do not use proxyDHCP mode and disable your DHCP server services whilst Serva is running).

USE ORACLE VM VIRTUALBOX TO PXE BOOT FROM SERVA

You can PXE boot using Oracle VM Virtual Box to test that PXE booting is working.

1. Add a new Virtual machine which has a virtual hard disk that you can install the OS onto.

2. Set up the Network Adapter to Bridged and set the Name to the physical network adapter on your host system (see below).

3. Run the VM and press F12 to get the BIOS boot option menu:

Press L to boot from the LAN. You should then see the Serva menu if PXE booting was successful:

Note that Windows XP will require the correct network driver to be added. See the Serva website for instructions.

You can now install XP or Win7 to your virtual hard disk (if you wish).

Win7 logon pop-up. You may need to add the correct Win 7 network drivers if they are not already in Win 7 WinPE.

BOOTING LINUX VIA PXE USING SERVA

Please read here to see how to boot various linux distros using SERVA.

To boot multiple computers within LAN, you can setup PXE network boot server in Windows. But it requires a high level of computer knowledge. So why not try an easier way?

By Delia / Last update April 8, 2021

Case: setup PXE boot server in Windows to boot another PC

When a computer has aging hardware or system errors, it may be difficult to boot it by normal means. In this case, you can set up a PXE server to boot another computer(s) within the LAN.

PXE, short for Preboot Execution Environment, is a standard client-server environment that boots client computers remotely by an administrator via network server. There are many significant advantages of PXE boot, for example:

  • The administrator can boot and maintain multiple PXE-enabled client computers.
  • Installation disc or USB (along with CD drive or USB port) is unnecessary for client computers.
  • The administrator can solve problems and breakdowns on client computers remotely.
  • It’s easy to centrally manage installation, updating, etc. and add new computers to network.

If you think it’s worth a try, keep reading and find how to setup PXE network boot server in Windows.

Prerequisites to PXE network boot

Before setting up PXE boot server, each client computer you want to boot should meet following conditions:

1. A PXE-capable network interface controller supporting Wake-on-LAN mode

2. A wired Ethernet connection to the network

3. All the computers you want to boot are on the same network

How to deploy PXE boot server in Windows?

Windows PXE boot setup basically consists of two parts – DHCP configuration and PXE boot configuration, which takes more effort than it looks. The working process is roughly like this:

The client connects to the network and sends out a DHCP broadcast. The DHCP server picks up the broadcast

The server replies with a suggested IP address, the client uses the provided address.

The client sends out a DHCP broadcast and states it needs to PXE boot, then the DHCP server replies it with the IP address to use.

The client contacts the PXE boot server to request and receive the boot file.

The boot file is then loaded on the client machines.

As you can see, the operation is relatively complicated. It’s not recommended to setup PXE boot server on your own if you are not computer savvy or simply afraid of trouble. After all, there are plenty of tools on the market that can simplify the process.

But if you insist on doing it without any third-party utility, here’s a more detailed tutorial for your reference.

Easier way to setup PXE boot server in Windows

Among all the PXE boot utilities, AOMEI PXE Boot Tool is a good choice with its strong compatibility and easy interaction.

It’s integrated in AOMEI Backupper Workstation, which is a powerful and cost-effective data backup & disaster recovery solution for Windows 10/8.1/8/7/Vista/XP.

AOMEI PXE Boot Tool is specially designed to safely boot and maintain multiple client computers within LAN through network. With it, you can directly create a Linux bootable ISO or Windows PE bootable ISO image file, and you don’t have to spend that much time setting up PXE boot server.

Steps:

1. Download and install AOMEI Backupper Workstation. Go to Tools tab and choose AOMEI PXE Boot Tool.

2. Select AOMEI Windows PE System and click Start Service. It will directly create a Windows PE system image for network boot.

в—‰ Boot from AOMEI Linux System applies to older or Linux based computers, and the third one Boot from custom image file allows you to load the special micro-system created by AOMEI PE Builder or Bart PE.
в—‰ Alternatively, you can create a bootable file by Create Bootable Media in Tools tab.

3. Now you can enable the computers within LAN to use PXE service. Turn on the client computers and press the required key to enter BIOS settings.

в—‰ The required key might be F2, F10, Del, etc., which depends on the specific brand and model of the device. You can search it on Internet or refer to the user manual.

4. Find Boot mode selection and make your choice.

в—‰ In general, UEFI mode includes more security features than the legacy BIOS mode. But if you’re booting from a network that only supports BIOS, you’ll need to boot to legacy mode.

5. Then find and enable the PXE boot option.

6. Set the PXE option as the first boot device in Boot Option Priorities.

7. It will take some time to boot from PXE boot server, specifically depending on your network speed and the size of the image file.

Related tips:

AOMEI PXE Boot Tool do support booting UEFI machines but currently only the WIM file can be used for UEFI (not the ISO file). If the file is an ISO file, you better change the boot mode to Legacy Boot Mode.

The network speed may be impacted if there are many computers using PXE boot. Thus you can try dividing PXE boot clients into smaller groups to boost the speed.

AOMEI PXE Tool contains a DHCP server that can be used if an existing DHCP server is not available. DHCP is usually offered by the LAN router.

Conclusion

PXE boot is a feasible way to boot multiple computers within LAN for system maintenance even when you don’t have any installation media. But to easily setup PXE boot server in Windows 10/8/7, you need the help of a reliable tool, like AOMEI Backupper Workstation. It not only has a powerful built-in PXE Boot Tool, but also a Create Bootable Media tool that can be used in cooperation.

Moreover, you can deploy the system image created on one computer to others with Image Deploy tool, which is integrated in AOMEI Backupper Technician and Technician Plus.

Table of Contents

Introduction

There are two different generations of virtual machines in Hyper-V: Generation 1 and Generation 2 virtual machines.

Generation 1 is a virtual machine that uses legacy BIOS, and a Generation 2 Hyper-V machine is a UEFI-based machine.

The Hyper-V virtual machine’s generation matters because PXE uses different boot files depending on if the machine boots are using Legacy BIOS or UEFI.

In most cases, I recommend that you create a Generation 2 virtual machine if you don’t have a specific reason not to. One reason could be that you have not yet enabled UEFI in your environment.

This blog post describes how to add a Legacy Adapter to generation 2 VM to enable PXE boot for devices not yet on UEFI.

If you want to learn more about Hyper-V, I recommend the courses at Pluralsight.

What is PXE boot?

PXE boot is a network boot where a small boot file is sent to a client at the initial boot-up. The PXE server typically uses WDS and DHCP to enable this communication. As an IT administrator, you can use a virtual PXE server or a physical PXE server.

Start PXE over IPv4 on a Hyper-V generation 1 machine

How do I verify the Hyper-V virtual machine generation?

If you want to verify if the Hyper-V VM is a Generation 1 or Generation 2 machine, select the VM in Hyper-V Manager and check the Generation version on the first page.

Why doesn’t legacy PXE work on generation 2 virtual machines?

A Hyper-V Generation 2 machine is like a running UEFI workstation.

The UEFI workstation could not communicate with legacy PXE, but only with UEFI boot images.

A machine configured with UEFI will use boot\x64\wdsmgfw.efi on the WDS server when starting the boot. A legacy boot will use boot\x64\wdsnbp.com.

The same issue with UEFI communication also applies to Hyper-V Generation 2 machines. This guide explains how to start PXE over IPv4 on Generation 1 Hyper-V VMs.

If your network is configured to deploy boot images using legacy methods, you must configure the virtual machine’s hardware.

How to configure a Generation 2 VM for legacy PXE boot

Step #1 – Create a virtual switch

First, you need to create a virtual switch. The virtual switch is required for the Virtual Machine to communicate with the network. If you have already created a virtual machine for your network, you can skip this step. Start by right-clicking the Hyper-V host in Hyper-V Manager and selecting Virtual Switch Manager.

Create a new Virtual Switch. Select External. External is similar to “Bridged” if you are using other virtualization platforms.

Give the new Virtual Switch a name. I named mine “Bridged.”

Step #2 – Add a legacy network adapter

By default, there is only a “Standard Network Adapter” installed on the Virtual Machine, but for PXE functionality, it requires you to add a Legacy Network Adapter.

Go to the Legacy Network Adapter that you just added and specify that it should use the Virtual Switch that you just created.

Step #3 – Configure startup order

6. Now, we need to make sure that the client boots first using the Legacy Network Adapter. Just select the Legacy Network Adapter and move it to the top of the list using the buttons.

Step #4 – Start the Hyper-V virtual machine

Start your Virtual Machine, and now PXE boot should work 🙂

Conclusion

As I mentioned in the introduction, in most cases, I recommend creating a Generation 2 virtual machine in Hyper-V if there are no specific reasons not to do so.

For a thorough explanation about choosing a Generation 1 or Generation 2 VM, refer to Microsoft Docs.

Do you usually create Generation 1 or Generation 2 machines in your Hyper-V environment? Let me know in the comments below 🙂

If you want to learn more about Hyper-V, I would highly recommend the courses at Pluralsight.

If you have more than one computer to install or maintain, it would be much more convenient to network boot multiple computers with PXE. But how does it work?

By Delia / Last update April 1, 2021

Cases to boot multiple computers via network

Normally when a computer fails to boot, you can start it with a bootable CD or recovery drive for further maintenance. But there are some special cases in practice, for example:

Your bootable media like CD/DVD/USB gets lost and you don’t want to buy a new one

You are in charge of many computers and it takes too long to install or maintain system one by one

Some machines don’t have a CD drive or cannot boot from a USB device

In these case, you may want to network boot multiple computers within the LAN instead of adopting traditional methods. But how does it work?

How does network booting work?

Network booting is not a new concept. The key to the idea is that a computer has its bootstrap code in non-volatile memory, e.g. a ROM chip, which allows the computer to contact a server and obtain system files over a network link. It makes network booting available so as to reduce the cost of maintaining – you don’t need a bootable media, you don’t need to do this machine by machine, you’ll even have a system that can be switched between different OS.

Another concept you should know is PXE, which is the short for preboot execution environment. It describes a standardized client-server environment that boots a software assembly retrieved from network, on PXE-enabled clients. As for client side, it requires a PXE-capable network interface controller (NIC), and a set of network protocols such as DHCP and TFTP.

To sum up, you can use PXE boot if following conditions are met on each client computer:

в–¶ A PXE-capable NIC that supports Wake-on-LAN mode

в–¶ A wired Ethernet connection to the network

в–¶ All the computers you want to boot are on the same network

How to boot computers over network with AOMEI PXE Boot Tool?

Now that you’ve known what PXE is, and understand the basic principles of booting multiple computers over network. What you should do next is learning how to configure a DHCP server, how to configure a TFTP server, how to set up accordingly in the BIOS to get an IP address from the PXE server and download the necessary boot images.

Wait, do you already feel troublesome just by looking at it? Actually it’s really not that complicated if you follow this guide step by step, and also, use the reliable AOMEI PXE Boot Tool integrated in AOMEI Backupper Workstation.

As the name suggests, it’s designed for PXE booting many computers from micro system in network. The only thing you should do is to run the tool on one computer within the LAN, and boot other computers via network.

AOMEI PXE Boot Tool allows you boot image file in network to maintain or manage multiple computers over network. Compared with other PXE boot tools, AOMEI PXE Boot Tool can directly create a Linux bootable ISO or Windows PE bootable ISO image file, and it doesn’t require you to deploy other plug-ins or programs. Thus, you can easily boot multiple computers over network.

Steps:

1. Download and install AOMEI Backupper Workstation following the setup wizard. Then click Home > Tools > AOMEI PXE Boot Tool.

2. Make your choice between Boot from AOMEI Windows PE System, Boot from AOMEI Linux System and Boot from custom image file. The first one is recommended since it will directly create a Windows PE system image for network boot, the second one can be used to boot older or Linux based computers, and the third one allows you to load the special micro-system created by AOMEI PE Builder or Bart PE. Then click Start Service to continue.

3. AOMEI PXE Boot Tool will configure related data automatically and wait for target computers.

4. Turn on the client computers and press the required key to enter BIOS.

5. Switch to Bios Features tab and find Boot Mode Selection. Press Enter on it to choose UEFI and Legacy or Legacy Only.

6. Press down arrow to choose LAN PXE Boot Option ROM and enable it.

7. Now you can set the PXE option as the first boot device by selecting Boot Option #1 in Boot Option Priorities, and then press Enter on the option Realtek PXE B02 D00.

8. Your computer is now booting from PXE over the network. It may take a few minutes till the process ends, depending on your network speed and the size of the image file.

Tips:

Alternatively, you can create a bootable file by clicking Home > Tools> Create Bootable Media in sequence.

The required key to enter BIOS usually refers to F2 or Del, but this depends on the PC manufacturer after all, so please check the documentation if needed.

AOMEI PXE Boot Tool support booting UEFI machines but currently only the WIM file can be used for UEFI (not the ISO file). If the file is an ISO file, you better change the boot mode to Legacy Boot Mode.

AOMEI PXE Boot Tool contains a DHCP server that can be used if an existing DHCP server is not available. DHCP is usually offered by the LAN router.

Conclusion

AOMEI PXE Boot Tool is specially designed to perform network booting. With it, you can easily PXE boot Windows 10 as well as other Windows OS on multiple computers within the same LAN.

Beyond that, AOMEI Backupper is also a comprehensive backup & restore software for personal and even business use. For example, you can backup or clone Windows OS to new SSD, restore system image to different computer with dissimilar hardware, sync changed files from source directory to destination in real-time, etc.

Applies to: Configuration Manager (current branch)

Bootable media only includes the boot image and a pointer to the task sequence. It downloads the OS image and other referenced content from the network. Since the bootable media doesn’t contain much content, you can update the task sequence and most content without having to replace the media.

Deploy operating systems over the network with boot media in the following scenarios:

Complete the steps in one of the OS deployment scenarios and then use the following sections to use bootable media to deploy the OS.

Configure deployment settings

When you use bootable media to start the OS deployment process, configure the task sequence deployment to make the OS available to the media. Set this option on the Deployment Settings page of the deployment. For the Make available to the following setting, select one of the following options:

Configuration Manager clients, media, and PXE

Only media and PXE

Only media and PXE (hidden)

Create the bootable media

When you create bootable media, specify whether it’s a USB flash drive or CD/DVD set. The computer that starts the media must support the option that you choose as a bootable drive. For more information, see Create bootable media.

Install the OS from bootable media

To install the OS, insert the bootable media, and then power on the computer.

Support for cloud-based content

Starting in version 2006, bootable media can download cloud-based content. For example, you send a USB key to a user at a remote office to reimage their device. Or an office that has a local PXE server, but you want devices to prioritize cloud services as much as possible. Instead of further taxing the WAN to download large OS deployment content, boot media and PXE deployments can now get content from cloud-based sources.

革命的愛熊主義者同盟!

  • このページの旧URLは
    • http://www10.plala.or.jp/palm84/multiiso_5_pxe_networkboot.html

内容古いです!

  • 【その1】準備編
  • 【その2】マルチブートDVD(CD) 作成編 ( ※ 改訂中、まだできてません。orz)
  • 【その3】マルチブートUSBメモリ作成編
  • 【その4】HDブート設定編 ( ※ まだです。orz)
  • 【その5】PXEネットワークブートサーバ構築編 ← 今ココ

これってなに?

  • 変更 : サーバを TFTPD32 から Tiny PXE Server に
  • 追加 : Lubuntu(i386), Redo Backup, Avira Rescue System, Bitdefender Rescue CD, Comodo Rescue Disk, Panda SafeDisk, linuxBean, KonaLinux
  • 更新 : Ubuntu, SystemRescueCd, Partition Wizard Home Edition, Clonezilla Live
  • 削除 : KNOPPIX InetBoot, EASEUS Todo Backup, Parted Magic

変更内容 2014.07.04

  • SystemRescueCd – 3.4.1 → 4.2.0 ( systemrescuecd-x86-4.2.0.iso )
  • Clonezilla Live – 2.1.0-26 → 2.2.3-10
    • clonezilla-live-2.2.3-10-amd64.iso
    • clonezilla-live-2.2.3-10-i486.iso
  • Partition Wizard Home Edition → ファイル名変更 : pwhe.iso

メモリ (RAM) が少ないと起動失敗することあったり、ほげほげと試行錯誤中.

さぁ何でしょう?(説明できるほどわかってません. 滝汗)。とりあえず、DHCP/TFTPサーバでPXEネットワークブート用サーバを稼動できます。Windows では TFTPD32 を使うと簡単です。

さらにわかってませんが gPXE (iPXE) ではHTTPサーバからのブートが可能になります。

尚、ココで設定しているモノは下記の通り。必要なものを選択してクダサレ。すべてで 7.65 GB 程でした。

  • Windows PE / RE
  • バックアップ・リカバリー
    • True Image WD Edition
    • DiscWizard | Seagate
    • Paragon Backup & Recovery
  • ウイルススキャン LiveCD
    • AVG Rescue CD
    • Comodo Rescue Disk
  • パーティショニング・ツール LiveCD
    • Partition Wizard Bootable CD

以上は 【その1】【その3】と共通のファイル配置 、基本的にisoを丸ごとメモリ (RAM) にロード(ダウンロード)してから起動するので、メニューで選択してブート画面が出るまで多少時間がかかります。

以下はサブディレクトリへisoをそのまま展開、PXEブートサーバーから kernel と initrd をダウンロード後に、Windows共有 or NFSサーバに接続します(※ linuxBean, KonaLinux, Panda SafeDisk は【その1】【その3】と共通 のファイル配置)。

PXELINUX MEMDISK

GRUB for DOS ではなく、PXELINUX (SYSLINUX) + MEMDISK に変更しましたです。

※ SYSLINUX のバージョンは 5.01 での確認です。

GRUB for DOS でもisoブートは可能なのですが、ネットワークブートに関してはこちらの方が利便性が高いかなぁと。

  • PXELINUX は http サーバからのダウンロードが可能なので TFTP に比べダウンロードが格段に速くなる
  • GRUB for DOS の利点として Direct Mapping 機能があるが、ネットワークブートでは不可
  • 他のブートストラップのチェインロードが割とカンタン

逆に欠点として、GRUB for DOS の様にisoのマウント後に kernel パラメータなどの個別オプション指定はできません。なので GRUB for DOS のチェインロードも可能に設定しとくであります。

ダウンロード

  • SYSLINUX(※ zip版をダウンロード)
    • バージョン 5.xx: Index of /pub/linux/kernel.org/utils/boot/syslinux/5.xx
    • 最新 : Index of /pub/linux/kernel.org/utils/boot/syslinux

【注意】バージョン5.01で確認しています。(※ バージョン 6 以降ではパスは bios 以下となります。)

  • 必要ファイル :
    • \core\pxelinux.0
    • \com32\elflink\ldlinux\ldlinux.c32 (SYSLINUX 5.x 以降では必須)
    • \com32\lib\libcom32.c32 (SYSLINUX 5.x 以降で pxechn.c32 使うには必須)
    • \com32\libutil\libutil.c32 (SYSLINUX 5.x 以降で menu.c32, pxechn.c32 使うには必須)
    • \com32\menu\menu.c32 (メニュー用)
    • \com32\menu\vesamenu.c32 (メニュー用)
    • \com32\modules\pxechn.c32 (pxelinux.0 チェインロード用)
    • \memdisk\memdisk (ファイル – img, iso 読み込み用)

※ バージョン 6 以降では、BIOS (legacy, not EFI) 環境でのブート用ファイルは bios 以下にあります。

  • GRUB for DOS ( grub4dos-0.4.4.zip ) をダウンロード
    • Browse GRUB4DOS and WINGRUB Files on SourceForge.net
    • 必要ファイル : grub.exe
  • PXELINUX 設定ファイル : default
  • PXELINUX 設定ファイル : 192.168.11.8_pxe_menu.cfg
    • pxe_menu.cfg にリネーム ( * IPアドレス要修正)
  • GRUB for DOS PXEブート用 : menu.lst menu_pxe.lst
    • menu.lst にリネーム
  • PXELINUX 設定ファイル : default
  • PXELINUX 設定ファイル : 192.168.11.8_pxe_menu.cfg
    • pxe_menu.cfg にリネーム ( * IPアドレス要修正)
  • GRUB for DOS PXEブート用 : menu.lst menu_pxe.lst
    • menu.lst にリネーム

pxe_menu.cfg を環境に合わせて修正

  • IPアドレス 192.168.11.8
  • CIFS(Windows共有)のユーザー名・パスワード – NFSOPTS=-ouser=HOGE,pass=HAGE

Windows用 DHCP/TFTP/HTTPサーバ – Tiny PXE Server

  • Tiny PXE Server – reboot.pro

TFTPルート下の pxesrv ディレクトリへ展開

  • config.ini サンプル 192.168.11.8_config.ini
  • config.ini サンプル 192.168.11.8_config.ini (Google ドライブ)
    • config.ini にリネーム ( * IPアドレス要修正)

Windows用 NFSサーバ

  • Free Network File Server (FreeNFS) for Windows
  • Windows PE / RE
  • True Image WD Edition
  • DiscWizard | Seagate
  • Paragon Backup & Recovery
  • AVG Rescue CD
  • Comodo Rescue Disk
  • Partition Wizard Bootable CD

isoをサブディレクトリへ展開

【注意!】KonaLinux はHDインストールができません。後述しますが、Ubuntu, Lubuntu, linuxBean はLive起動時にネットワークの修正、HDインストール後にGRUB2の修正が必要になります。

  • cifsroot (Windows共有) – Ubuntu, Lubuntu, linuxBean 14.04
  • nfsroot (NFSサーバ) – Ubuntu, Lubuntu, linuxBean 12.04, KonaLinux,
  • Ubuntu ja Desktop DVD 14.04 (amd64)
  • Lubuntu Desktop DVD 14.04 (i386)
  • SystemRescueCd 4.2.0
  • linuxBean 12.04 / 14.04
  • KonaLinux 2.3 i386
  • Avira Rescue System
  • Bitdefender Rescue CD
  • Panda SafeDisk
  • Clonezilla Live 2.2.3-10-amd64
  • Clonezilla Live 2.2.3-10-i486
  • Redo Backup

TFTPルート下のisoサブディレクトリへisoをそのまま展開、設定ファイルを追加。SystemRescueCd は pxelinux.0 を \isolinux から一つ上へコピー、ディレクトリ pxelinux.cfg を作成して設定ファイルをコピー。

IPアドレスは 192.168.11.8 になっているのですべて置換してください。 pxe_bean1404cifs.cfg はユーザー名/パスワードの修正も。

Tiny PXE Server (PXEブートサーバ)

Windows版 DHCP/TFTP/HTTP サーバです。ネットワークの基本を理解してれば設定は簡単。

  • config.ini

サンプル config.ini は 192.168.11.8/24 となってるので環境に合わせて適宜修正してください。

コマンド プロンプトから ipconfig /all で自PCのIPアドレスなどを確認。

NFSサーバ

  • Free Network File Server (FreeNFS) for Windows
  • FreeNFS | Free software downloads at SourceForge.net(※ あやすい広告バナーに注意)
  1. FreeNFS.exe 実行
  2. アイコン右クリ【Settings】で Root Folder を指定

CIFS(Windows ファイル共有)

Ubuntu, Lubuntu, linuxBean で可能ですが、これらはNFSブートも可能なので不要なら設定しなくてよいです。

  1. isoフォルダを共有設定
  2. Users にアクセス許可(※ パスワードなしだとダメ. 多分. )

ファイルの配置

【注意!】問題点

Ubuntu, Lubuntu, linuxBean, KonaLinux では修正が必要な問題が発生しました!

KonaLinux 2.3 i386

  • 【FreeNFS】Windows で Debian Live ネットワークブート用サーバの設定【NFS編】

Ubuntu 14.04 amd64, Lubuntu 14.04 i386

  • CIFSブートではインターネット接続が無効となっているので修正作業が必要
  • NFS/CIFSともHDインストール時は実行前にネットワーク接続の修正が必要
  • NFS/CIFSともHDインストール実行後にGRUB2の修正が必要

http download ではかなり速いですが、オンメモリ起動となるので RAM は 512MB 以上必要となってます。(※ 1GBあった方がいいかも?)