this is probably an easy one for someone.
a machine with an nt4 OS disk with dorked OS, registry corrupted.. whatever the problem du jour is.... there is lots of data on the disk. it would take a very long time to copy over the network, and I'm going to upgrade the machine to 2k anyway.
so, in an effort to be efficient, I image a different disk in the computer room (same make and model) with our windows 2000 image. set it up with the right name, join it to the domain... everything.
I go up to where the dorked machine is, and swap hard drives. boot it up just to make sure everything is cool.
then I install the nt4 disk as primary slave. when I boot up the machine with the second (nt4) disk, it does some stuff and tells me to reboot the machine. not wanting to reboot the machine, I do the file copy. it crunches along...
so after the copy. I shut the machine down. and remove the nt4 disk and reboot.
it then tells me that I have no paging file and won't let me log into the machine. so I put the disk back in, and it lets me log in, but it seems that the registry is currupted, and I was getting clsid errors trying to open MMC. and afer about 3 minutes, the machine shuts down of its own volition.
that's the situation. I'm out of the woods with this one as I just re-imaged the new disk and was able to use the bartpe xp boot disk to copy the data off the old drive onto the newly re-imaged 2k drive.
so here's the questions:
1.) what is the process that happens when I put an nt4 disk as slave into a 2k machine? (seems like it moves the page file and a bunch of other stuff with the program file directory... shortcuts int he start menu pointed to the program files on the nt4 disk. weird...)
2.) is there some non destructive preparation that I can do on the nt4 disk (or the 2k disk) to prevent this black magic from happening?
I think in the future I'm just going to use the bartpe disk after I install the nt4 disk to do the file copy. this way, the 2k OS won't even see the nt4 disk...