2008 R2 Hyper-V VM hangs after logging in
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!!!!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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 ?
After and update ?
before an update ?
have you installed or uninstalled a specific software ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Must have been a delicious meal !!! all good glad you got it working :)
Cheers
Cheers
ASKER
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.
ASKER
Because I figured out the solution myself before anybody else did.
ASKER