Issues with 2008 Server in Hyper-V / How to replace AD server.

I have a 6 server test environment running with Oracle VM VirtualBox. One server is Windows Server 2008 R2, the others are Windows 2012 server. (The 2012 servers are fine, so they won't be mentioned much more.)

My goal is to move this entire to a machine running Windows 10 (anniversary edition) using Hyper-V. I used the disk management tool in VirtualBox to convert and copy the hard disk files to VHD format. I have the files now attached and all run, except for the 2008 server. It constantly blue screens and does not start of course. It will start in recovery mode, but I have no recovery file. I took the following steps when creating the Hyper-v machine for the 2008 server -

Create New Machine
Select Generation 1 (the existing hard file can not be found if Generation 2 is selected.)
Select dynamic memory (also tried to boot with this unselected)
Connect to external virtual switch (tried other variation also)
Select to use an existing virtual hard disk, (also tried to attach later, made no difference)
Start machine, all works fine except for 2008 server.

Any ideas why this may be. Host machine has all updates applied. Plenty of resources. Hyper-V enabled in bios.

But if I can't get this machine to run, I need to replace the server and promote it to be a DC. I really can't take the other servers out of the domain and add to a new domain without doing major reconfigurations applications running on them. So the dilemma, if I create a new DC, (which is not big problem), how I can convince the existing servers that the new DC is the same as the old DC, as far as SID's etc..

I have no AD backup of the old server.

LVL 21
Walter CurtisSharePoint AEDAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Philip ElderConnect With a Mentor Technical Architect - HA/Compute/StorageCommented:
07B is the disk controller not being found. BTDT.

Attached is a text file with all of the registry settings that is needed to reset on the 07B VM.

You will probably have to mount the VM's VHDX file then mount it's Registry. From there, import this registry file into the _VM's_ mounted registry hive location.

Once that is done the VM should be able to boot.

You may need to boot to a 2008 R2 ISO and use the Repair functionality to fix the boot configuration database (BCD).
Lee W, MVPTechnology and Business Process AdvisorCommented:
I suspect it's a problem with the drivers for the disk controller - or perhaps you used a SCSI disk in virtual box where Hyper-V requires the boot drive to be on IDE if memory serves.

I'd suggest mounting the Hyper-V Integration Tools while the VM is running in Virtual box and install them first.  Then when prompted for the reboot, don't, shutdown and move the hard drive VHD.

Note: Gen2 VMs are for 2012 and later ONLY.
Lee W, MVPTechnology and Business Process AdvisorCommented:
Of course, it would be helpful if you posted the stop error you're getting - a screen shot would say a lot.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Walter CurtisSharePoint AEDAuthor Commented:
Trying now, thanks.

Fingers crossed!
Walter CurtisSharePoint AEDAuthor Commented:
Sorry to say that did not make any difference. Good idea though...

Attached is a screenshot of the blue screen.BlueScreen.png
If you have any other ideas let me know.

Many Thanks
Lee W, MVPTechnology and Business Process AdvisorCommented:
7B is inaccessible boot device.  It's definitely having driver issues with the storage controller.  Most I can offer at the moment.
Walter CurtisSharePoint AEDAuthor Commented:
Dumb questions here - In Virtual box it shows all storage devices connected as SATA. In hype-v they are IDE devices. Any idea if that makes a difference. I do have 5 vm's that made the move fine, so that is in the back of my mind.

Thanks again for the input...
Walter CurtisSharePoint AEDAuthor Commented:
Great information and will let you know results.

I am seriously thinking about aborting my idea of moving my environment and just doing a new install in my new environment. It would be better off. If TechNet was still around I would have done that long time ago instead of trying to recycle old software :-)

Have a good one...
Walter CurtisSharePoint AEDAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.