I sometimes use PXE and GRUB, and I'm too tired at the moment to remember what I usually do. But I like that I can use grub and its menu.lst file to help decide what to boot, and can therefore choose different partitions or a data recovery or ... and I can choose to boot from disk or the network.

I mostly use Unix though, although I had to look at this for windows once upon a time...

H

You can use some of the UBCD image's tools under a PXE boot... 'course not memory testers. :-)

BTW, you had better damn well trust your userbase to leave a TFTP running, switched fabric or not. Very susceptible to injection, and since they are nice bare packets at the PXE level... great for server and router backend, bad for corporate environments with "smart guys"... TFTP being nonauthenticating and every vulnerability it's ever had is always root level. Whoops. Even the protocol specification itself is flawed and vulnerable. Definitely consider risk mitigation options if you leave an open one running. (VLAN it off is one way, only machines on that segment who currently need it.)

We use PXE boot to image embedded devices, namely wireless access points (monowall and metrix). We have built and do maintain for one client, a PXE booting LTSP (Linux Term Serv Project) server and 6 clients that fire off of it. It has been nothing but stable and using KDE's Kiosk Tool's, a dream to take care of. I also have read a bit about PXE boot over WAN (it was related to a Debian project), which i can see being a good way to rescue machines (amongst other things).

I would like to learn pxe server. We currently have to use a win Bart PE disk to boot and them map network drive and run Ghost.
Can you tell me what I need to do step buy step so I can learn how to create an environment in which I can push out images to machines simultaneously by booting from LAN.