Network Service Boot 1

[sman26]

I am writing to get some clarification on the NETWORK SERVICE BOOT option (pressing F12 on an HP during POST for ex.) that most PCs come with now which can be configured in the PC's BOOT Order. What is this used for and how can I benefit by having this option. After the PC goes into the Network Service Boot it seems to be searching for an IP address. This is outputed on the screen :
CLIENT MAC ADDR: 00 15 60 C1 C4 1E GUID: 37916DEE 1983 DB11
DHCP... / (the forward slash spins)
Do I need to have a separate server, RIS (Remote Installation Service), set up which then talks to this PC.
Any information would be appreciated.
Thank you.
sman

 

[LawnBoy]

The most common network boot protocol these days is PXE. RIS is still used fairly widely, but most new PCs are configured for PXE (check the pc BIOS to change).

In order for any Network Boot Services to work you must have an appropriate server on your network. When the PC boots, it sends an extended DHCP request, and your PXE or RIS server responds by sending a bootable image to the PC via the network. The PC then boots from this image.

When the slash 'spins' the PC is waiting for a PXE/RIS response.

I've not used RIS, but if you deploy a PXE server be aware of the security risks involved. The PXE spec includes BIS (Boot Integrity Service) which secures the exchange, but I've seen several implentations of PXE that don't include BIS.

 

[PalmTest]

At VMWare you can download the free VMWare Player.

http://www.vmware.com/products/player/

With this Player you are able to run preconfigured VMWare environments on your Windows platform.
VMWare has a large collection of Appliances.

http://www.vmware.com/vmtn/appliances/directory/

One of them is a PXE environment.

http://www.vmware.com/vmtn/appliances/directory/74

It enables you to test and check (and play) with PXE without the risk of ruining a real server.
But be aware of the risks LawnBoy mentioned.