A WordPress.com site dedicated to System Center and Cloud Management

Posts tagged ‘Hyper-V’

SCVMM 2012 R2 Compliance Scan Fails With Error 2927

I encountered this issue while writing my article series on Patching Hyper-V Hosts with SCVMM 2012. 

As a reminder, my Hyper-V Host is NOT a member of my Lab domain. Therefore, it is added to SCVMM as a Perimeter Host.

At first, I was actually encountering the following error.

Error (24035)
Compliance scan failed with error: 8024402c.

Recommended Action
Ensure the WinHTTP proxy settings are correctly configured for the communication with WSUS. If WSUS is configured to use SSL, ensure the WSUS certificate is installed in Trusted Root CA for the machine and then try the operation again.

VMM Compliance Error - Error 24035

After laboring over many Google search results, and not coming to a solution, something struck me. The Recommended Action states in part “Ensure the WinHTTP proxy settings are correctly configured for the communication with WSUS.” This got me thinking, “what’s wrong with the communication?” After all, I can successfully PING my Host server from inside the SCVMM virtual machine.

VMM Compliance Error - Host Ping Results

So it made me question the communication/connection from my Host to the SCVMM virtual machine. And that’s when I checked my Host’s network configuration, and discovered that my Host’s Network Connections to my Hyper-V Virtual Switch was disabled. I don’t recall when/why I disabled it, but I re-enabled the Network Connection.

VMM Compliance Error - Host Network Connections

After re-enabling the Host’s connection to my Lab’s virtual network, I re-initiated the Compliance Scan. The result? ERROR! But, this time it was a different error.

Error (2927)
A Hardware Management error has occurred trying to contact server HOST .

WinRM: URL: [https://host:5986], Verb: [INVOKE], Method: [ScanForUpdates], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/UpdateManagement]

Unknown error (0x8033800d)

Recommended Action
Check that WinRM is installed and running on server HOST. For more information use the command “winrm helpmsg hresult” and http://support.microsoft.com/kb/2742275 .

Now we’re getting somewhere. When I Googled the error wording: “VMM A Hardware Management error has occurred trying to contact server”, I was lead to this site: SCVMM 2012 – A Hardware Management error has occurred trying to contact server. Unknown error (0x803381a6). I checked my Host’s WinRM configuration, and the service was already running.

VMM Compliance Error - Host WinRM Config

However, one of the comments pointed me to this site: How to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager. In that Microsoft KB article, it was Step 5: Check the Svchost.exe process of the Windows Remote Management service, that ended up resolving my issue.

Step 5 says in part:

This problem can occur if the shared Svchost.exe process that hosts the Windows Remote Management service is experiencing issues.
To resolve this problem, configure the Windows Remote Management service to run in a separate Svchost.exe process. To do this, open an elevated command prompt, type the following command and then press ENTER.

sc config winrm type= own

Note Make sure that you type the command exactly as it appears here. Notice the space after the equal sign (=) symbol.
If the command is completed successfully, you should see the following output:
[SC] ChangeServiceConfig SUCCESS

 So, I entered “sc config winrm type= own” in a command prompt, and received the expected results of “[SC] ChangeServiceConfig SUCCESS”. I then stopped/started the WinRM service, and started the SCVMM Agent service using the following commands:

Net Stop WinRM
Net Start WinRM
Net Start SCVMMAgent

VMM Compliance Error - WinRM Config and Restart

Finally, after going through all of that, I went back to the SCVMM console, and again, re-initiated the Compliance Scan. The results? This time the scan completed successfully and the Compliance Status is shown!

VMM Compliance Error - Scan Completed

So that’s my experience in using my non-domain joined Hyper-V Host with SCVMM.

SCVMM 2012 SP1 in a LAB – Configuration Guide (Deploy an Agent to an Existing Hyper-V Host)

In our last post we finished installing Forecast Analysis Reporting. Now we will start on the configuration.

Hello everyone, if you have been following along with my guides, you should now have SCVMM installed.

But SCVMM won’t do you any good if it doesn’t know about any Hypervisor/virtualization hosts or VMs, so that’s where we will start as part of these Configuration guides.

First, start by launching the SCVMM console. Click on Fabric in the lower left. Now expand the ‘Servers’ directory. From there, right-click on ‘All Hosts’ and choose ‘Create Host Group’.

Deploy Agent 01

Name your custom Host Group whatever you want. Note, you can rename it at any time if you need to.

Deploy Agent 02

Now right-click on your new Host Group and choose ‘Add Hyper-V Hosts and Clusters’.

Deploy Agent 03

On the Resource Location screen of the Add Resource Wizard, make the appropriate selection for the Windows Computer Location, and then click Next. Note that you can even choose ‘Physical computers to be provisioned as virtual machine hosts’, which would allow you to provision bare-metal systems! For our lab example, since we have an Active Directory domain that the SCVMM server is a member of, we will choose the first option.

Deploy Agent 04

On the Credentials screen, click Browse so that we can add an existing account as the Run As account. Note the information at the bottom of this screen, which reminds us that the Run As account needs to be a Local Administrator on the host machines you want to manage.

Deploy Agent 05

On the Select a Run As Account, click the ‘Create Run As Account’ button, since we don’t have an account already within SCVMM to use.

Deploy Agent 06

On this screen you need to provide the details about the account. You can give it a name (Note that this is NOT the actual username used for the account, but an identifying name), and description. You will need to provide the actual username and password for the account. In my lab example I created an account called SCVMMAdmin, and used that on this screen.

Enter an applicable account on this screen and then click OK.

Deploy Agent 07

Now our newly added account is available to be selected. You will notice in my example that I named the account “Hyper-V Host Administrator Account”. Select your account and then click OK.

Deploy Agent 08

Now the Credentials screen will show the account that we have selected. Now click Next.

Deploy Agent 09

On the Discovery Scope screen, choose the appropriate the scope option. You can use an Active Directory query, or type the names to search for. In my lab example, I just typed the names. Make your appropriate choice and then click Next.

NOTE: You can opt to ‘Skip AD Verification’ however it is best to perform AD verification to ensure the system can be communicated with.

Deploy Agent 10

If there are issues with the wizard not being able to communicate with the Host(s), you may encounter this error. Read the message displayed and then click OK. Perform whatever actions are required to resolve the communication issues, and then re-attempt to add a host system.

Deploy Agent 11

On the Target Resources screen, if the host system(s) are able to be contacted, they will appear here. Select the system(s) that you want to add as hosts, and then click Next.

Deploy Agent 12

On the Host Settings screen, you can assign the selected computers to a specific Host Group (i.e. the one we originally created). You could use the Host Groups to organize hosts based on area/zone (i.e. PROD, UAT, TST, DEV, etc.). For our lab example, just click Next.

Deploy Agent 13

On the Migration Settings screen you can specify how many live migrations (for both storage, and VMs) can be performed simultaneously. For this example in my lab, since I don’t have a second physical host to use for live migrations, I won’t turn this feature on. At  this point, just click Next.

Deploy Agent 14

Review the information on the Summary screen and then click Finish.

Deploy Agent 15

This will open the Jobs screen, and show the progress of adding the host.

Deploy Agent 16

If there are any issues, you will be alerted to them here. Correct any issues, and re-attempt to add the host. Once it has been added successfully, you can close the Jobs window.

You will notice in my lab example, that adding my host completed but with a Warning. This is because my physical host does not have Multipath I/O. This is used in reference to SAN storage, which I don’t have.

Deploy Agent 17

Back in the main SCVMM console your Host will now be present.

Deploy Agent 18

Congratulations, you now have SCVMM installed, along with adding a Host hypervisor (in our case, Hyper-V) system to be managed.

Next we will create host groups and clouds.

ASUS P9X79 WS with Intel 82579V NIC and Hyper-V

Hello Everyone, I wanted to briefly share something that I recently discovered. If you read my last post about OS Installation and Using A Server OS With A Workstation Motherboard you may recall that a little .inf modification is required in order to detect/use the Intel 82579V Gigabit NIC in Windows Server 2012.

After getting this second NIC functional, I then proceeded to install Hyper-V. During the initial role installation, you are prompted to select a NIC as the Hyper-V virtual switch. However, at least in my case, although both NIC are now present to the OS, and functionality had been tested/confirmed, only the Intel 82574L appears in the list of NIC available. Therefore, it is because of this that I made my Intel 82579V NIC my external/Internet connection port, and the 82574L as my Hyper-V NIC.

I emphasize during the “initial” role installation, because after Hyper-V is installed, when you access the Hyper-V Manager and open the Virtual Switch Manager, you can in fact change the external adapter from the Intel 82574L to the 82579V. Now, I haven’t tried this change yet, but I assume it would work on account of it being available in the list.

HyperV Virtua Switch


Once I finish copying all 50 GB of lab software (i.e. OS’s, Middleware ISO’s, etc.) to my new host, I will then be in a position to start creating my lab environment (i.e. AD/Domain, SQL Server, System Center products, etc.). So stay tuned.

Tag Cloud

%d bloggers like this: