• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 3284 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't start the windows 2008 R2 in virtual machine and BMR

shanmugaprakash
over 6 years ago

windows 2008 r2 server was protected by Quest, But suddenly the Windows 2008 r2 server had a HDD issue  and it is down now. Hence, we tried to create one-time export as virtual machine, the export was successful but it failed to boot on windows 2016 server hyperV. So, we also tried BMR in another machine and it was successful too but it didn't boot as well .

Parents
  • 0 over 6 years ago
    The first thought I have is make sure you pick the correct virtual hardware when you do the export or when you manually create the VM. Assuming that the original did not use EFI you will want to select gen1 in Hyper-V so that you don't get a VM template with EFI. Same with ESXi, on restore day older VM hardware is better.
Reply
  • 0 over 6 years ago
    The first thought I have is make sure you pick the correct virtual hardware when you do the export or when you manually create the VM. Assuming that the original did not use EFI you will want to select gen1 in Hyper-V so that you don't get a VM template with EFI. Same with ESXi, on restore day older VM hardware is better.
Children
No Data