- I am posting the documentation I did some time ago because I found that there is not enougth documention with printscreen, so there is it my documentation :-)
- My pritnscreen is with ntbackup, but the goal and idea is the same for Win 2008.
- My printscreen is in french for some parts. When I will get time I will update them.
- I switch from hypervisor version during the documentation, it's not a bug, it's two document merged together.
1 - Always do a snapshot before importing the System State.
2 - Do #1.
3 - Server template should be in your "wallet" before making that procedure.
4 - A server template is for me a simple vanilla server that is pre-activated with a license I have. It is configured in a virtual machine and stored away (burned to a DVD, on a USB stick, etc..). It's ready to be put in any computer and ready to make a "Play"
on it to recover anything. (Personnal note: I did recover a domain that way and temporally used a receptionnist computer to hold the VM until a new physical's server came fast to replace it)
1 - Having different HAL is a nightmare to recover on different hardware. If your DC is 1 core, then recover it to a 1 core VM and if it's multiple core then restore it to a multiple core VM.
1a - If you don't follow my advice, you might fall on STOP error 0x0000007B bluescreen even if your harddisk hardware is the same.
Before anything, you need a System-State backup, there is some small step to show you how to do it.
Click the start menu and select "Run" and type ntbackup :
Click NEXT with the Wizard option selected :
Select to Save file and Settings :
Select Let me Choose what to save :
Select ONLY System-State :
Select to save it to a File, and select where to save it :
Click Finish :
We now wait...
Click Close :
Start an "vanilla" Windows Server template on a hypservisor. There I choosed VMWare, but the documentation was done some time ago.
Select F8 in the startup and choose Active Directory Restore :
Choose the system to start with :
Enter in the system :
Click OK :
Copy the system-state to the VM
Click the startup menu, select Run and type ntbackup :
Click NEXT :
Click Restore Files and settings :
Click BROWSE :
Select your File :
Click System State :
Click Advanced :
Click NEXT :
Click Replace Existing Files :
Chooses thoses options :
Click Finish :
Click CLOSE :
CREATE A SNAPSHOT BEFORE RESTARTING
If the HAL differ from the source-destination then try to erase the Processor in the System panel (see below on where to do it)
Re-install the VM tool to be sure it will boot (see below if it don't reboot).
Restart in Active Directory Restore Mode :
In the command prompt, type :
authoritative restore <ENTER> restore database <ENTER>
Click YES :
Check if the Restore go well :
Go to that Reg key and put BurFlags=d4
When finished click Restart :
After restarting, be ready for a lot of popup ! but the domain login locally will work now :
After the restart the server is almost done :
You now have to make sure you use the same IP, and that all roles are ok.
Now the DNS should popup good :
Update your processor information in your control panel :
Run a dcdiag :
Yagmoth555 edited Revision 12. Comment: almost finished, typo to correct later !