none
Unable to add Hyper-V Host RRS feed

  • Question

  • I have VMM 2008 R2 running on Windows 2008 R2, SP1.  It was managing a host running Hyper-V on Windows 2008 R2, SP1 Server Core.  For some reason, the VMM lost communication with the host.  I tried removing the host, but that did no good as I am unable to re-add it.  It gets the usual error: "Failed to configure the WS-Management service".  There is nothing that should indicate a WinRM problem.  I can run PowerShell remotely from VMM on the host, same with WinRS and Server Manager.  I checked that the listener was okay and I ran "winrm /qc" over again, but of course it was already configured. 

    I am confused about the line in the error message that says to make sure there are no Group Policy settings affecting WinRM.  There *is* a GPO with a related setting, which has been in place for over a year: "Allow automatic configuration of listeners", with IPV4 and IPV6 filters of "*".  This is the reason it *has* worked up until now.

    I have disabled the Windows Firewall on both servers and disabled TCP Offload on Windows and on each NIC on both servers. 

    I am out of ideas.  Looking at the Event Logs on the VMM, it seems that this did begin to happen after these Windows Updates were installed:

    Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 R2 x64 Edition (KB2559049)
    - Security Update for Windows Server 2008 R2 x64 Edition (KB2567680)
    - Security Update for Windows Server 2008 R2 x64 Edition (KB2563894)
    - Security Update for Windows Server 2008 R2 x64 Edition (KB2536276)
    - Update Rollup for ActiveX Killbits for Windows Server 2008 R2 x64 Edition (KB2562937)
    - Windows Malicious Software Removal Tool x64 - August 2011 (KB890830)
    - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2539635)
    - Security Update for Windows Server 2008 R2 x64 Edition (KB2560656)
    - Security Update for Windows Server 2008 R2 x64 Edition (KB2556532)
    - Update for Windows Server 2008 R2 x64 Edition (KB2563227)
    - Update for Windows Server 2008 R2 x64 Edition (KB2570791) 

    I also see this in the Windows Remote Management Event Log: "WSMan operation SignalShell failed, error code 995", but I don't know when that started. 

    I am out of ideas.  Is there anything else to check? 

    Thanks.

    Sunday, October 16, 2011 3:47 AM

Answers

  • After wasting hours on this problem, I uninstalled VMM, then reinstalled using the media with SP1 slipstreamed and chose a new database.  I had no problems at all adding back the hosts and libraries.  Not a good solution for an organization with lots of hosts and library servers, but it worked for me.
    Sunday, December 4, 2011 3:19 AM

All replies

  • Do you have the specific error log for the WinRM error? What is the user context under the "Identity" section?

     


    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Sunday, October 16, 2011 5:12 PM
    Moderator
  • Thanks for the reply.  The log I mentioned is the Windows Remote Management Event Log under Applications and Services Logs.  I'm not sure if that answers your first question.  I'm not sure where to look for the Identity section, but I am running the VMM tasks as the Domain Admin. 

    This is a test environment and I only have that one Hyper-V server, so I don't know if the same would happen with others, but the information below probably suggests it would:

    - The Hyper-V server that the VMM lost communication with was also a Library server.  I removed it as a Library server and I am also not able to add it back, which is probably not surprising.

    - If I go to Administration > Managed Computers, the VMM itself, which is a Library server, shows Agent Status: Not Responding, and I am running the VMM Console local to the VMM.

    The VMM was managing the Hyper-V host for over a year with no problems before it suddenly lost communication.

    Thanks for any help with this.

     

     

    Wednesday, October 19, 2011 3:49 AM
  • Any ideas as to what is going on with this?  Is the fact that the local VMM Server shows "Agent Status: Not Responding" telling of where the problem may lie?  Or is that insignificant?

    Thanks.

    Wednesday, October 26, 2011 2:13 AM
  • PS-Remoting enabled on the Port as well?

    What does the following key show when the firewall is enabled?

    HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\WINRM-HTTP-In-TCP


    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Friday, October 28, 2011 10:49 PM
    Moderator
  • Dear Friend,

    Please ensure that you DNS server is running and check you host of server 2008 r2 core is able to ping with the domain controller according to the domain name. for example, consider your domain name is test.com, so to host server 2008 r2 core and put the command ping test.com and check the result, whether you are able to communicate with dc as per domain name (Test.com).

     

    the same problem was happened with me and i resolved the problem by starting the dns service from the dnsmgmt.msc console.

    try it.


    Kamal Sharma
    Saturday, November 12, 2011 1:41 PM
  • Thanks for the reply.

    I checked the DNS resolution for the domain from both the Hyper-V and VMM servers and it resolved the domain name to the DC's IP addresses as expected.

    Thursday, November 17, 2011 3:28 AM
  • After wasting hours on this problem, I uninstalled VMM, then reinstalled using the media with SP1 slipstreamed and chose a new database.  I had no problems at all adding back the hosts and libraries.  Not a good solution for an organization with lots of hosts and library servers, but it worked for me.
    Sunday, December 4, 2011 3:19 AM