We have been using IT Edition to move our servers to new Hardware.

As a test we always image the old servers to a IBM Xseries 100 

the latest server we tried has a EISA Configuration Partition at the start of the Disk 0, the other servers we have imaged do not have this partion,

and we have never had any issues. ( I have a screen scape of this, I can upload if you want to see it - how do I upload a file?  )

We use HIR and have never had to install any aditional drivers to get a system up and running on the IBM ( graphics sometimes looks awful, but . . )

this is the original boot.ini from original machine

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect

during restore of the c: drive image, the boot.ini file gets patched, and looks like this.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows"
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect

When booting the machine after the restore,

option1 gives a BSOD C0000135 ( unable to locate dll ) the dynamic link library winsrv.dll could not be found in the specified path Default Load Path.

option 2 gives a screen saying Windows 2000 could not start because of a computer disk hardware configuration problem.

I have also tried converting the C: drive image with vmconverter and starting the VM in vmserver, but I get the same error.

Anyone ever imaged a machine with a EISA Partition ( we don't want the EISA Partition bringing over to the new machine)  ?  

cheers

Jeff 

Missing winsrv.dll and BSOD 0xC0000135 smell of registry hive corruption or some problem when backing up the machine. Are you certain the source machine is still healthy and can you check if the target machine does indeed have that file missing?

I once got such a machine going again by deleting MountedDevices from the non-booting migrated (not source!) machine registry.

It could be an HIR problem though, so why not ask support for some help. There is too little information to say for certain what the problem might be.

I re-imaged the server, and had the same issue.

I have found a work around after reading another forum.

Once the image has been restored with HIR, before booting the system, I deleted the winnt\system32 directory from the c: drive,

mounted the image of the c: drive, and copied the winnt\system32 from the mounted image onto the c: drive, and all works ????? 

Jeff