P2V image of a Windows 2003 domain controller Hyper-V

Hi,

I have a windows 2003 domain controller which hold the FSMO roles. I have taken a P2V image of this server and has mounted this into a Hyper-V virtual server. The Hyper V server is 64 bit windows 2008 and the domain controller is 32 bit.

The server begins to load and sits on preparing network connections for some time. It then applys computer setting and this too takes hours. I finally get presented with a Ctrl Alt and Del prompt, try to log in, but this takes a long time and never gives me a desktop to do anything.

I can get in the server in safe mode with and without network connections, but I never see the networks connections Nics.

Any advice or help please?
monarchitAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
monarchitConnect With a Mentor Author Commented:
yes
0
 
kevinhsiehCommented:
You need to load the integration components to use the synthetic NIC. You may want to also add a legacy NIC and see if that gets you farther until you cab load the Integration Components. Do you have another domain controller?  If you do, and there is DHCP available your DC should be able to get on the network and contact another DC via the legacy NIC. Once you have networking running it should be able to boot normally.
0
 
monarchitAuthor Commented:
It was actually some HP services stopping the server from loading.
0
 
kevinhsiehCommented:
Can you disable those services?
0
 
monarchitAuthor Commented:
stop HP services
0
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.