2008 R2 Hyper-V VM hangs after logging in

Posted on 2014-09-17
Last Modified: 2014-11-12
Microsoft's great Hyper-V has completely screwed me again.  I have a 2008 R2 virtual machine and I was running 4 VM's.  I just got a new server and installed 2012 R2 and moved all the VM's over.  This one VM in particular (which is running 2008 R2 and Exchange 2013 Standard) would not start the Exchange Transport service on the new server.  So I tried deleting the NIC from the VM when it was on the original server and shutting it down and THEN moving it to the new server (export feature apparently doesn't work going from 2008 to 2012...thanks MS for letting us all know that BEFORE we purchase your over priced software).  And now either the new server or old I am completely screwed, I can log into the VM but pretty much after that it's a horrible SLOW performance.  So slow that when I immediately try to right click on Network and go to Properties it just hangs.  I've tried adding a new NIC to the VM, I've tried deleting the NIC from the VM and starting up with no NIC.  The problem may be Exchange, but how do I fix it?  I can't believe Hyper-V is THIS friggin unstable!!!!
Question by:tphelps19
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3

Author Comment

ID: 40329590
So if I restart in safe mode with networking then Windows installs the NIC ok and I can even get a ping to respond from the outside.  Problem is as soon as I restart in regular Windows it freezes again as soon as I try to go to into Network Properties.  Also if I do an ipconfig it shows a regular windows IP.

Assisted Solution

by:Dash Amr
Dash Amr earned 200 total points
ID: 40329597
lets get to this Step by Step but before PS: honestly you shouldn't modify the actually working VM by removing the NIC at least you had exchange working - and You can't blame MS for that :) anyway,

ON the Old Server log into your Host if you can and add the NIC back to the VM from the Hyper V management console

That should at least get your Exchange back up and running - try this or maybe let us know more about the situation to get a clear picture.

Expert Comment

by:Dash Amr
ID: 40329603
I assume its Exchange 2010 or above so  let me know how did Exchange Transport service stopped

After and update ?
before an update ?
have you installed or uninstalled a specific software ?
Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.


Accepted Solution

tphelps19 earned 0 total points
ID: 40329620
I think I got it working!!  Get this....  I tried everything and the network properties window kept freezing so finally just said screw it and went and got something to eat and when I came back (like 45 min later) it finally had unfroze and there was a balloon window in the bottom right saying windows had installed a new virtual adapter NIC and then I just gave it an IP and restarted, and viola!

However I did do ONE thing that may have contributed to fixing it.  I disabled every Exchange service and then restarted so they were all disabled upon restart.  I was convinced that's what was causing the hanging but when it didn't that is when I Just left and went to eat.  Weird...weird...weird.

Expert Comment

by:Dash Amr
ID: 40329635
Must have been a delicious meal !!!   all good glad you got it working :)


Author Comment

ID: 40330404
One note though in case anybody follows this thread, the ORIGINAL problem was still there which was the Exchange Transport service was not starting.  Quick note about Exchange 2013:  if you move it to another server via VM, you HAVE to manually re-add the bindings for DNS lookups.  I know it's so stupid and I remember dealing about this with MS back when I first got Exchange 2013.  It's under the Admin Center > Servers > DNS Lookups.  By default it's set to "All available IP v4 Addresses" but apparently that's another gotcha from MS because that excludes VM's.  For VM's you have to specifically specify the Microsoft Virtual Host Adapter on both internal DNS lookups and external DNS lookups.

Author Closing Comment

ID: 40338626
Because I figured out the solution myself before anybody else did.

Featured Post

MS Dynamics Made Instantly Simpler

Make Your Microsoft Dynamics Investment Count  & Drastically Decrease Training Time by Providing Intuitive Step-By-Step WalkThru Tutorials.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A safe way to clean winsxs folder from your windows server 2008 R2 editions
In previous parts of this Nano Server deployment series, we learned how to create, deploy and configure Nano Server as a Hyper-V host. In this part, we will look for a clustering option. We will create a Hyper-V cluster of 3 Nano Server host nodes w…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question