I am replacing an old domain controller with a new one. Both are running
small business server 2000. This is a simple network with one domain
controller. I am attempting to use the full backup of the old server to
restore to the new server to make deployment easier. I set up partitions on
the new server just like the old one. I installed sbs 2000 on the new box,
just that and nothing else. Then I successfully restored the c and d
partition to the new server. Here's where the trouble begins. When I restore
the system state to the new machine, everything goes ok, then I reboot and I
get the Windows screen, then a blue screen with stop error "inaccessible boot
device". When I try to boot from the cd and do a repair, I get an error
stating that there is no windows installation to repair. I get the same when
trying to boot from an erd.
I then did a parallel install into a different directory, copied the
"drivers" folder from the new install to the original, and I still can't boot
to it.
I am almost positive that this is a scsi driver issue, but I don't know
how to make windows use the correct drivers.
I know this is procedure is possible, because I have done it this way
with great success in the past. Any ideas?
Thanks
Jeff Middleton [SBS-MVP] - 25 Aug 2004 03:41 GMT
My suggestion, in the interest of keeping it brief, is to do an in-place
repair on the new server. That should solve the driver problem, and it
shouldn't have a negative affect on the domain.
If you really need more detailed ideas, let me know.
BTW, copying the driver folder from the old server really isn't addessing
the issues involved.
> I am replacing an old domain controller with a new one. Both are running
> small business server 2000. This is a simple network with one domain
[quoted text clipped - 16 lines]
> with great success in the past. Any ideas?
> Thanks
Pat Horridge - 31 Aug 2004 16:09 GMT
I agree with Jeff that an in-place repair would be best.
If the old server is still un and running you could try installing the
drivers for the new MB (particularly the SCSI) even without the hardware
present. Then do your backup and then try restoring that on the new system.
> My suggestion, in the interest of keeping it brief, is to do an in-place
> repair on the new server. That should solve the driver problem, and it
[quoted text clipped - 35 lines]
>> with great success in the past. Any ideas?
>> Thanks