This is usually the part where the fun begins. Newer servers do not have a floppy drive, but the only way to load drivers into Windows Server 2003, besides RIS or remastering CDs are floppy drives.
Getting an USB floppy drive is no big deal, you connect it to the machine, it boots, you press F6, select the storage adapter driver, format your hard disks, and then setup asks for the floppy again and again. Bummer.
The problem is that the first part of setup (loading the Mass Storage driver) is not handled by Windows, but instead by the BIOS’s floppy emulation. But the latter part, after formatting the hard drive is handled by Windows. And some of them are not recognized by the builtin USB storage drivers.
In my case, i had an iomega USB floppy with a built in card reader (don’t ask). I used device manager to find out the vendor and product id of this USB floppy.
I opened the txtsetup.oem supplied with my mass storage driver, and modified the section that my mass storage driver had.
I added the following line, directly to after the SCSI adapter itself:
id = "USB\VID_08BD&PID_1100", "usbstor"
I had no idea if this would work at all, but it did.
For your reference, i’ve included my txtsetup.oem, which works with iomega usb floppy dirves.