"DisplayName"="Standard IDE/ESDI Hard Disk And I only had to change the Start and/or Tag entries. This is where I need to make the registry changes. "ImagePath" and "DisplayName" are different and ignore theĪdditional amd64 refs as they are okay (On another server this could be different "Tag" were different and thus the problem. Ones though, existed but I noticed that the "Start" and Service for me but all four were in the CriticalDeviceDatabase key so this was You need to verify these entries, ControlSet001. To edit, which we do next to fix the drivers. The hard drive recovery now that it sees windows, which makes the registry hard GOOD REASON to not reboot, is if it's successful you can no longer boot from Now the system should at least try and boot windows and give you a blue screen I would not reboot yet or close command, but in effect Select partition 2 (this is recovery partition) Type the following commands in the order below: To reassign the drive letter for the recovery partition which is likely If (as in this example) partition 3 is the C: drive then you will need Recovery mode from the hard drive, enter the administrator, and choose repairĭrive letters (TESTSERVER specific but a good baseline for others)įirst we have to run diskpart and then select disk 0 Repair, choose image recovery and restore all drives or whatever options youĪfter restore has completed the system will reboot. Was originally used to build your SBS 2011 server.īoot from the cd, select language etc, then choose
#Restore a backup from windows 2011 install#
Start VM using the Boot disk or ISO for the install that In my environment we only use a fraction of the space available on the physical box, so thin provisioning worked great. This means that if you have two physical drives that are 4 TB in size, then create two drives with 4 TB each. The drive sizes match to the new VM drive quantity and size. Make sure that the number of physical drives match and How to restore an SBS 2011 Windows Backup to a Virtual The regular backup which is taken offsite is the answer. But I wanted an option in case their hardware tanked or was stolen. The reason I did this was because the systems get backed up regularily and they are not ready to virtualize yet. Have done it twice now following the steps below. I had to bumble around quite a bit before I got it to work. I will post below exactly my steps to do this in case anyone else is ever looking for it. Was successfully able to restore to both VMWare and to Hyper-V environments.
#Restore a backup from windows 2011 how to#
I found an article that described how to do it.