Numerous times in the past, I've had great success with changing hardware by Ghosting the server over to the new hardware, booting the system from the cd, allowing it to go through the load process, F6'ing new raid drivers in, and going all the way to the install to where it detects the previous installed version, doing a repair from that point and bringing the server up. However....
This is the first time I've attempted this with a Small Business Server 2000, and it appears as though something is different. The ghost image is fine on the new hardware, however of course due to the changes, I get the BSOD of Inaccessible_Boot_Device. This is usually cleaned up by the above mentioned process. The change is of course that the OS on the server is at a certain service pack level (4) and the original install disks are at sp1. So I've slipstreamed SP4 onto a new disk, extracted a SBS boot.bin file from the original, made a bootable cdrom with the boot.bin and the slipstreamed sp4 sbs cd. This works fine up until I tell Windows to install and it checks for a previous installation. It doesnt find it! I've never had this problem with regular 2k server, and this is a first. Obviously the SBS disk can NOT be slipstreamed and still detect the previous installation, so now Im at a loss. I've got a ghost image of the server on new hardware that is not going to work unless I can get into the system and change the mass storage information (which was done with the repair process and worked flawlessly with 2k standard).
When I boot with the original SP1 SBS cd, it correctly detects the previous installation and runs through the repair process, however my guess is, due to the differences in SP levels (4 on the server 1 on the cd), I still get the Inaccessible_Boot_Device error. If I cant get a decent way to clone this information over to the new server, I'll be forced to reinstall the original OS and copy all of the data over to the server. Ick!
Help!
This is the first time I've attempted this with a Small Business Server 2000, and it appears as though something is different. The ghost image is fine on the new hardware, however of course due to the changes, I get the BSOD of Inaccessible_Boot_Device. This is usually cleaned up by the above mentioned process. The change is of course that the OS on the server is at a certain service pack level (4) and the original install disks are at sp1. So I've slipstreamed SP4 onto a new disk, extracted a SBS boot.bin file from the original, made a bootable cdrom with the boot.bin and the slipstreamed sp4 sbs cd. This works fine up until I tell Windows to install and it checks for a previous installation. It doesnt find it! I've never had this problem with regular 2k server, and this is a first. Obviously the SBS disk can NOT be slipstreamed and still detect the previous installation, so now Im at a loss. I've got a ghost image of the server on new hardware that is not going to work unless I can get into the system and change the mass storage information (which was done with the repair process and worked flawlessly with 2k standard).
When I boot with the original SP1 SBS cd, it correctly detects the previous installation and runs through the repair process, however my guess is, due to the differences in SP levels (4 on the server 1 on the cd), I still get the Inaccessible_Boot_Device error. If I cant get a decent way to clone this information over to the new server, I'll be forced to reinstall the original OS and copy all of the data over to the server. Ick!
Help!
