Changing W2k Server hard disk

Hoo boy. Yes, you will run into problems. If you will permit, I recommend searching the Microsoft knowledgebase at support.microsoft.com for further information on this question and also on the boot process for windows 2000.
Of course, you will need to have compatible scsi adaptor drivers installed. One thing you will run into is that the boot.ini file will need to be modified to point to the new scsi boot drive. this is all explained in various knowledgebase articles.
I wonder if you should install a 'temporary' OS onto the new scsi drive and then copy the old OS onto it? that would get you proper boot record and boot.ini

Umm, I agree with the previous answer. You will need to plan this out. I really don't know if a Ghost image of your IDE drive will work properly with no manual modifications to put the OS on the SCSI drives.
One thing you could try is setting up the SCSI drive(s) in the computer with its existing OS on the IDE drive, set up your SCSI array (if you are gonna have more than 1 SCSI drive), then bring the OS up and set up a software mirror between the IDE drive and the SCSI drive/array.
Once the mirror is stabilized, you could then create a Win2K boot floppy with a manually modified BOOT.INI that points to the SCSI drive.
Then you could boot that way, from the floppy, onto the SCSI drive, and then Remove the IDE drive and break the mirror, setting the SCSI drive/array as the sole partition with the OS on it.

Good luck

Modified question: Would it be a lot more simpler and straight forward if I were to change to IDE interface HD?

Thanks

If I were you ...I would rather get another server (even a regular Workstation )and configure it as a W2K server then promote it as a DC with AD, then tinker the old server. That way you don't need to go to each computer and add them to domain including SAMS for the users, if the plan goes SNAFO.

Changing the HD from EIDE to SCSI is a tough job. If you have Syamntec Ghost software.. you could create an image of your hard drive with the OS. Then create a network boot up disk with the scsi driver so that when you will pull the image back the scsi drives will be recognized and when you pull up the image. Again this is a good for one drive but the Hardware raid controller may complicate matters.

Good luck

To your modified question in answer three, YES, it would be far simpler for you to change the IDE drive with another IDE drive and GHOST the image over to the new drive. I would suggest that you also run scandisk and defrag before running GHOST. You can GHOST this with the new drive slaved in and then GHOST the Master drive to the Slave drive. Once this is complete, remove the old drive and set the new drive as the Master drive. This would completely eliminate the installation of the SCSI controller drivers and editing the boot.ini. Should you decide that SCSI is the way to go, install the SCSI controller card first and install the drivers while still booting on the old drive. You should then be able to GHOST old to new, remove the old, set the BIOS to boot to the SCSI drive and edit the boot.ini file for the SCSI controller and drive. .... Simply put, sticking with IDE would be much more simplistic. Also be prepared to do a repair load of the OS, in either case. As usual, always prepare for the unexpected and backup your old drive first. I have also found it worth while to FDISK the new drive on another computer, without any other hard drives attached, and set the partition as Active when it is FDISKed.

I hope this helps.

This question was closed by the author