Thin Client and Virtual Machines Thread, Converted 2003 R2 DC Hangs in Technical; I have just converted a 2003 R2 DC using Disk2VHD for use in Hyper-V.
In fact I converted 2 DCs.
28th June 2012, 12:29 PM #1
Converted 2003 R2 DC Hangs
I have just converted a 2003 R2 DC using Disk2VHD for use in Hyper-V.
In fact I converted 2 DCs.
The first DC works fine and I can log in.
The second DC gets stuck on "Applying Computer Settings". Its been stuck for the last 1.5 hours.
It boots up in Safe Mode with Networking fine (takes about 5 minutes to boot)
I have done the following How to remove hidden network adapters from virtual machines
but it still hangs.
This is for a test environment NOT production!!
IDG Tech News
28th June 2012, 01:19 PM #2
Well I wouldnt do this for DC's. I'd just create a new DC on Hyper V environment and transfer roles from old DC alot cleaner and safer.
Also I try and keep DC's physical or at the very least one
28th June 2012, 01:24 PM #3
@irsprint84 This is only for a test environment. I am testing upgrading some software which runs on the DCs. Making a clean DC would not work as I need the DC with all its current bits and pieces installed.
28th June 2012, 01:31 PM #4
Can you log on as a different user, e.g. local administrator or does it never get to the point where you can actually logon?
28th June 2012, 01:31 PM #5
I believe VMWare's advice is that you can convert DCs to VMs OS wise, but you must demote them first, then re-promote them afterwards. You also have to be extra careful that the old one is kept well away from the network once the new fires up! I'm looking to do this with a DC that hosts our Sophos console. I'll have to demote it (which breaks the Sophos console as I dumbly set it to connect to localhost years back), convert, kill the old one, then switch on the VM and repromote.
28th June 2012, 01:35 PM #6
Hasnt got to the point of login yet.
Originally Posted by timzim
@3s-gtech As I previously stated this is only to test upgrading some software it is NOT to virtualise my DC permanently. The virtualised DC is not connected to the network at all.
28th June 2012, 02:33 PM #7
ok fixed it
As the DC existed on a Physical HP Server there were certain Services that were taking up 100% of the CPU hence the very very slow boot up.
Followed the instructions here FIXED – P2V of Windows-based HP Servers – cqmgserv.exe Problem | Heavy Soil
and all is now well with the Virtual DC
By techie08 in forum Windows Server 2008 R2
Last Post: 8th July 2010, 09:37 AM
By jamiesev in forum Windows Server 2008
Last Post: 14th April 2010, 04:43 PM
By cookie_monster in forum Windows
Last Post: 18th June 2008, 09:36 PM
By Simcfc73 in forum Windows
Last Post: 25th May 2006, 10:17 PM
By CM786 in forum Windows
Last Post: 24th May 2006, 08:45 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)