saccrue

Hey, I think I may have figured this out. I tried a couple of things at once because I am in a hurry right now. I'll go back and do it again this weekend and then edit this post, but, to get you going... I went to the MSDN downloads site and grabbed the VL 2003 Server that I needed. I talked to someone that said that they had a similar problem when trying to do an RIS with Windows 2000 with a version of the OS that came from an MSDN disk that had multiple OS versions on it. Something about a mismatch between the txtsetup.sif file and the fact that the disks that have multiple OSes on them are not for deployment, yak yak yak. So, I grabbed the Retail 2003 VL .iso from MSDN and then used the files from that to build the unattended install. While doing that, I also decided to make sure that the volume label that I gave my .iso that was made by CDImageGui was the same volume label that the .iso I downloaded had, and, I named my .iso file the same name as the downloaded file. I doubt that this had anything to do with it, but you may want to download the MSDN file and if that doesn't work, then set the volume label. Mine is working now.

I have the same issue. I created an XP Volume License install and it worked great. My Windows 2003 Server Enterprise Volume License install is doing the same thing. It is looking for a previouse version of windows.