Thursday, August 23, 2012

Hyper-V Heartbeat: No Contact

Problem
In hyper-v manager i'm seeing Heartbeat: No Contact.

Other symptoms:
1. Network adapter is not detected
2. When logging in with a domain user it says "The security database on the server does not have a computer account for this workation trust relationship"
3. When logging in with a local account it results in "Apply user settings..." loading screen sitting there forever

Solution

I tried multiple things to solve this. Here's all the steps i took in reverse order, so if the last thing i did is actually what solved it then you'll try that first and save lots of time. If it's a combo of all these things then it won't matter what order you do it in.


Solution 1
Apply what this KB says manually: http://support.microsoft.com/kb/2004121

  1. Start->regedit
  2. Navigate to HKLM\SYSTEM\CurrentControlSet\Services\HTTP and create the following Multi-string value: DependOnService
  3. Double click the new DependOnService entry
  4. Type CRYPTSVC in the Value Data field and click OK.
  5. Reboot the server
Solution 2

Remove and re-add the computer to the domain

1. Right-click Computer choose Manage

2. Click on System Properties

3. Click on Computer Name

4. Click Change

5. Click the Workgroup radio group, then type in the domain admin password

6. Restart the computer

7. Repeat sets 1-4, this type add the computer to the domain


Solution 3


1. Start the virtual in Safe Mode - with networking support. To do this keep hitting F8 while it's loading.

2. From Actions select Insert Integration Services Disk

3. Restart

4. While it's restarting keep hitting F8 and choose to restart in Safe Mode - with networking support, otherwise the "Setup configuration blah blah" gets stuck

Solution 4

1. Shut down the virtual machine

2. In Hyper-V Manager right-click and choose Settings

3. Remove the Virtual Network Adapter

4. At the top click on Add Hardware, then choose Legacy Network Adapter

5. Once that's added turn on the virtual machine



References
1. http://support.microsoft.com/kb/2004121

1 comment:

There was an error in this gadget