System State Restore > Different Hardware > Continous Restart. 2

[boston33]

Hello,

We backup a Win 2003 Domain Controller. We backup the System State, C:\Windows, C:\Documents And Settings, C:\Autoexec.bat, C:\boot.ini, C:\ntldr, and C:\NTDetect.com.

We are doing a restore test. The recovery server has different hardware. On the recovery server, we restarted into directory services restore mode. We restored the system state and the other files. We kept the recovery server's hal.dll file, because of different hardware.

After we finished restoring, we restarted the server. Now the recovery server shows Windows starting then restarts. It is continuously restarting.

Do you have suggestions on how to resolve this issue? Thanks for your help.

 

[FloDiggs]

The problem is the different hardware. There is something that we always referred to as the "HAL Trick" that forced a reinstall of the HAL, but didn't effect the Windows installation itself. I think the better option for you would be to create a new server on the different hardware, and then promote it to a domain controller using the backup tape. That is one of the best features of 2003.

 

[tmccarty8]

Hi Boston33, I have had this issue with XP and found that just using the original install CD and doing a repair install will solve the problem. It is your problem if you chose to do the first repair option using the Repair Console, I always choose the second repair option when the installation finds the existing install and asks if you want to repair it. I feel that this will work on Server 2003 the same as it works on XP. It is a much simpler fix than setting up a new server, promoting it and restoring from tape.

 

[boston33]

I booted from the Win2003 cd and selected setup. It did find the existing installation. The setup > repair worked. I can get to the desktop.

The recovery/test server is showing errors about finding the domain.(There are two production domain controllers. I might have to break the domain replication on the recovery/test server?).

If you get a chance, could I get the steps you used for the "HAL Trick" ?

Thanks for the assistance.

 

[FloDiggs]

It's about the same as running a repair, but at some point you used some advanced options and select Advanced Configuration and Power Interface (ACPI) PC HAL. Unfortunately, I no longer work where I learned this technique, so I do not have access to the document as easily. Let call in a favor and see if I can get the How To.

 

[FloDiggs]

I checked with my old company and they can't find the document they created. Basically, it's like I said before, but when it asks you to press F6 for special drivers, you press F5. Yes, F5, not a typo. Then you just have to make sure that you select the appropriate HAL for a basic PC, multi or uniprocessor systems.