ITIExperts1
asked on
"preparing network connections" after Disk2VHD conversion.
I did a Disk2VHD conversion of an SBS2003 server.
Now when i boot it a a virutal machine it stays on "preparing netowrk connections"
I have enable and disabled the network connections of the virtual server but it did not help.
It is running on Win 2008 SP2 Hyper-V
Now when i boot it a a virutal machine it stays on "preparing netowrk connections"
I have enable and disabled the network connections of the virtual server but it did not help.
It is running on Win 2008 SP2 Hyper-V
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
murgroup
I agree with jimmy. Let it sit for an hour or so. It should hit the cnt-alt-del screen but takes time. Then you can fix the network issue. It probably needs the hyper-v tools installed so SBS will pickup the NIC driver. You can do that once you login.
ASKER
it has been about 1 hour now,
It is the AD and DNS server for the network
It is the AD and DNS server for the network
I understand. It gets pretty stressful when this is a production box.
Ok. Here is what i recommend then.
Boot to Directory Services Restore Mode (DSRM). At this point we are doing this simply to bypass AD.
Once you get in, pay attention to any notifications that pop up (new hardware found), etc. Then check your network settings. Make sure the server is looking to itself for DNS. Make the the IP and all other settings are what you would want them to be.
Boot to Directory Services Restore Mode (DSRM). At this point we are doing this simply to bypass AD.
Once you get in, pay attention to any notifications that pop up (new hardware found), etc. Then check your network settings. Make sure the server is looking to itself for DNS. Make the the IP and all other settings are what you would want them to be.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Any updates on this or did you go back to your production box?
ASKER
Did the HyperV intergration in Safemode and diabled some HP Services and it logged in.
Thank you.
Thank you.
I love this site. Between the zillion HP services and Symantec AV Control Centre the virtualized server wouldn't ever get past the "preparing network connections". Unfortunately I stumbled across this during one of the many reboots of the virtual server from safe-mode but it turned out to be spot on.