Here’s a new Knowledge Base article we published today that applies to both VMM 2008 and VMM 2012. This one talks about an error you can get when trying to add a Host or Cluster to System Center Virtual Machine Manager:
=====
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".
This can occur when 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.
To resolve this issue, run the following command from an elevated command prompt with Administrative rights on the SCVMM server:
winrm/config/client @{TrustedHosts="*"}
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
For the most current version of this article please see the following:
2668596 : Error (2927) - (Unknown error (0x803380e4)) when trying to add a Host or Cluster to System Center Virtual Machine Manager
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
I'm having that same exact issue in my environment now. I've applied the winrm command to change TrustedHosts=*, however I am still receiving the same error. This all began after installing the System Center Update Rollup on the SCVMM server.