Creating a network boot disk for win xp

By Mulfygfunkera2000 ·
I have set up a RIS, but i have some computers that do not have pxe compliant network cards or floppy drives. I need to create a network boot cd or removable media such as a memory key. Any advice would be greatly appreciated.

Many Thanks


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Re: Creating a network boot disk for win xp

Hopefully the list below will help you out.
Hope all works out.

In short, a workstation can boot from a variety of methods - via floppy disk, local physical disk (or other media) or via the network. At boot time, a workstation that has been set to boot primarily from PXE will issue a BOOTP request via the network. BOOTP and DHCP are closely related - a workstation sends a request for a 2nd level TCP/IP unique identifier (IP address) based on the machine's MAC address, a unique number based on two parts - a manufacturer code and a unique number. The machine will also advertise its GUID or UUID (Globally Unique Identifier / Universally Unique Identifier) if the machine has one. If the machine has a GUID, the machine will advertise its GUID / UUID over a MAC address.

Once received, a BOOTP server will not only supply the IP address to the machine, but enable booting from remote media. In this case, the Microsoft RIS server will issue a floppy disk boot image, which can then be used to fetch either a system image file, or one from a third party system such as Symantec Ghost or Acronis TrueImage.

Following execution, the system will configure itself based on this information and will allow the system to boot as if a floppy disk was inserted. Following the use of a third party imaging solution, it is necessary to either directly alter the registry to change the system's unique ID, the SID; use the Microsoft tool NewSID, which will create a new SID and allow the user to rename the computer; or using the sysprep utility from Microsoft, the system will re-run the final configuration of an installation - which generates a unique SID and if required, will join a Windows domain.


On Windows 2003, two services are required to provide Remote Installation Services. These are DHCP and Remote Installation Service. The Remote Installation Service doubles as a proxy DHCP server to provide Boot Server and Filename instructions to clients. These however override any boot server options sent by the DHCP server itself. The Remote Installation Service utilises UDP port 4011[1], and provides to clients the content of each page OS Chooser displays. Additionally, this service provides drivers (such as for Network Interface Cards) to the clients. These are required to launch OS Chooser, and allow it to mount the share (REMINST) in which the images are stored.

It is possible to install or boot other Operating Systems through RIS, such as a GNU/Linux distribution through the Linux Terminal Server Project.

The required servers for performing this service are: domain controller, DNS, DHCP, RIS.

Windows Deployment Services

The successor to RIS is known as Windows Deployment Services (WDS),[2] and is intended to be used for remote deployment of Windows Vista and Windows Server 2008. It is also available for Windows Server 2003 (and included with SP2 version of the same). To use the WDS PXE server, the server must be configured for WDS server role and a WDS client requires Windows PE 2.0.

Please post back if you have anymore problems or questions.

Related Discussions

Related Forums