Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error (2927) - (Unknown error (0x803380e4)) when trying to add a Host or Cluster to System Center Virtual Machine Manager


View products that this article applies to.

Home users: This article is only intended for technical support agents and IT professionals. If you're looking for help with a problem, please ask the Microsoft Community.

↑ Back to the top


Symptoms

Adding a Hyper-V Host or Cluster to a System Center Virtual Machine Manager (SCVMM) server generates the following error message:

Error (2927)
A Hardware Management error has occurred trying to contact server <FQDN_Name>. 
(Unknown error (0x803380e4))
 
Recommended Action
Check that WinRM is installed and running on server <FQDN_Name>. For more information use the command "winrm helpmsg hresult".

↑ Back to the top


Cause

Some reasons this error can occur are:
  • A possible issue with WinRM in Windows Management Framework 4.0 and lower. See the Resolution section below for details.
  • Another reason is that the WinRM Trusthost policy of the SCVMM server is set to blank. The default is TrustedHosts = *. To determine the WinRm Trusthost setting, run the following command on the SCVMM server from an elevated command prompt:

    winrm g winrm/config

    Here is a snippet from a Host where the WinRM Trusthost policy is set to blank:

    DefaultPorts
    HTTP = 5985
    HTTPS = 5986
    TrustedHosts
    Service
    RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)

    Here is a snippet from a Host where the WinRM Trusthost policy is set to the default setting:

    DefaultPorts
    HTTP = 5985
    HTTPS = 5986
    TrustedHosts = *
    Service
    RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GA;;;S-1-5-21-2210657229-244641257.

↑ Back to the top


Resolution

  • To make sure the issue is not with WinRM, install WFM 5.1. You can download the version of WMF 5.1 that applies to your operating system from https://msdn.microsoft.com/en-us/powershell/wmf/5.1/install-configure.
  • To resolve issues caused by the WinRM Trusthost policy of the SCVMM server is set to blank, run the following command from an elevated command prompt with Administrative rights on the SCVMM server:

winrm set winrm/config/client @{TrustedHosts="*"}

↑ Back to the top


More Information

The issue described above can be created by deploying a Windows Remote Management (WinRM) AD Group Policy and then removing it, leaving the server in an unknown state once the policy is removed.

GP Policy vs. Preference vs. GP preferences: http://blogs.technet.com/b/grouppolicy/archive/2008/03/04/gp-policy-vs-preference-vs-gp-preferences.aspx

Local Group policy setting found running gpedit.msc:

Local Computer Policy -> Computer Configuration -> Administrative Templates ->Windows Components -> Windows Remote Management (WinRM) -> WinRM Client

↑ Back to the top


Keywords: kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 2668596
Revision : 7
Created on : 10/19/2018
Published on : 10/22/2018
Exists online : False
Views : 631