Question : Windows Deployment Services on WIN 2003  PXE Server ISSUES?

At my work I have a WIN 2003 Server setup with Windows Deployment Services on it. We use it to PXE boot to it, and then pull an OS image from it to install on our new computers. The computer that I want to image first boots from a boot.wim file, from the PXE server. which is custom made. This boots VERY fast, and then presents a .htm gui interface to pick which image you want to pull from the server and install on the computer. It works awesome, and installs the image .wim in 2 mins or so.

ISSUE: If I am trying to image more than one computer at the same time, which Is what we need to do. It makes all the computers that are trying to be imaged go WAY slow and take up to an hour. Is there some kind of setting or adjustment I need to do on the PXE server inorder to allow multiple deploys at the same time?

Answer : Windows Deployment Services on WIN 2003  PXE Server ISSUES?

No, nothing you rally can do about the performance degradation other than faster disks in the server and more bandwidth to the network from the server.  In windows 2003 each computer that connects to the WDS is a unicast or one to one connection.  Each additional connection will degrade the performance of all.  I find that with a 1gb connection from the server I can get five or so simulatneous images done in an hour and a half or so.  More than that and it gets pretty slow.  One thing to try is to stagger the image process somewhat so they aren't all trying to do the same thing at exactly the same time.  I've had better success doing it that way.  If you have WDS installed on a 2008 server, then you could enable multi-casting which would allow you to image multiple systems with little performance degradation.