[Off-topic] hilaireg:
The process you're after is a sub-process of imaging.

Here's an abridged version, very abridged, but should give you a sense of what's involved ... having done this a few (aka many many) times.

Media

Generally, the media to use for this type of activity is obtained directly through Microsoft as using another OEM's media is generally problematic as it has been altered for their requirements. Since you're using the DELL OEM CD on DELL OEM systems, you can "get away" using it.

One of the steps you may want to do is slipstream WinXP SP3 to the media. Here's a good site to get you on your way, there are many more out there:

http://www.winsupersite.com/showcase/xpsp3_slipstream.asp

Product Key

The product key embedded in the OEM CD ensures that it is only useable on DELL branded equipment. This permits end-users to rebuild their system and skip the product activation phase - the caveat being that OEM media is used on the OEM system; you can't interchange OEM media/systems as this will trigger activation.

Enterprises usually obtain a Volume License Key (VLK) which allows them to use imaging methodologies to deploy the O/S to workstations.

Note

Before others chime in ... yes, there are "work arounds" but since we're sticking to legitimate usage - we'll avoid that topic.

Pre-Delivery Process

There are two approaches to this process.

The first, traditionally used by OEM's (ex: DELL, HP, etc.) is to inject their drivers into the O/S media and modify some of the setup information files so as to ensure that the drivers are detected during the TEXT & GUI setup portions of Windows.

The second, traditionally used by Enterprises (ex: 20+ workstations) is to build a base image which is: install windows, install drivers, run SYSPREP, capture (seal) image. Knowledgeable IT builders will usually inject the drivers they require and adjust the setup information files prior to running SYSPREP and "sealing" the image.

Note

Large OEM's will also use the second process so that they may build many similar systems at once for shipment purposes. In a nutshell, the customer gets the media but the actual system HDD has been imaged.

Additionally, some OEM's will ship their systems with a hidden partition that is accessible by pressing a combination of keys at boot. The hidden partition contains a copy of the system image which can be restored to the visible partition.

Post-Delivery Process

The are two approaches to this process.

The first, traditionally used by OEM's (ex: DELL, HP, etc.) is to provide the O/S media along with the system. At the factory, an image is copied to the system HDD (see note above) and the system is shipped to the customer. When the customer unpacks and starts the system, the mini-SYSPREP is initiated and the system goes through a mini-GUI setup procedure.

The second, traditionally used by Enterprises (ex: 20+ workstations) is to take the pre-delivery process "sealed" image and upload it to a distribution system such as SMS, Altiris, OnCCM, Symantec GHOST, etc. The BIOS of the workstations are usually configured so that the Network Adapter (NIC) is set for Pre-eXecution (PXE) boot. A Wake-On-LAN is sent to the MAC address of the workstation (which has been recorded during asset receipt/delivery), the workstation turns on, sends a PXE-Boot request, the DHCP server responds to the request and forwards the request to the distribution server, the workstation receives a boot image from the distribution server, which in turn initiates imaging of the workstation HDD. Once completed, the workstation reboots and goes through an automated mini-GUI setup which performs all of the necessary detection and driver installation.

Some Final Points

You can inject drivers to the physical media (ex: Windows XP) and perform individual installs of Windows on a system-by-system basis. This is often referred to as slipstreaming drivers or injecting drivers. This is often required for AHCI controllers on new systems.

Imaging can be "tricky" if you have to deal with multiple variations of hardware abstraction layers (HAL) such as in the case with single/multi processor architecture.

Ensure that customers receive a copy of the media with their systems so as to remain compliant and not violate license agreement terms.

Avoid using NLITE unless your company is planning on providing continuous ongoing support with each system sold. NLITE is an extremely fast method of preparing systems for mass image distribution. Unfortunately, it is not officially endorsed/supported by Microsoft and/or OEM's. Enterprises or individuals can usually "get away" with using NLITE as they typically self-support their systems.

Recommendation

In your situation, it may be easiest to read up on the following methodologies:

Slipstream service pack to cd-rom (media)

Slipstream (inject) drivers to cd-rom (media)

HTH,