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

Posts tagged ‘SCVMM’

Applying SCVMM 2012 R2 Update Rollups To Perimeter Hyper-V Hosts


I came across this scenario while writing my How to Add Hyper-V Hosts in a Perimeter Network in VMM 2012 R2 post. After adding my Hyper-V Host to my SCVMM installation, I installed the Update Rollup 3 to VMM. However, when doing so, even though the installation itself was successful, the status of the SCVMM Agent installed on my Host showed “Needs Attention” (since the SCVMM Agent was installed off of the original VMM media).

VMM Primeter Host - 01 - Host Status

If you select the host and click on the “View Status” button, you will see in the Host Properties dialog under Status, that the Host Agent Version shows a Warning status.

The Error Details are displayed as follows:

Warning (20510)
An upgrade is available for Virtual Machine Manager agent version 3.2.7510.0 on the computer HOST.

Recommended Action
Update the VMM agent, and then try the operation again.

VMM Primeter Host - 02 - Host Properties

You might think that we could easily update the SCVMM Agent (similarly to the SCOM Agent) by clicking on the Repair All button. But if you attempt to do so, and take a look at the Jobs workspace, you will see that the Remediate Host Health job actually failed, with the following error.

Error (10436)
Virtual Machine Manager does not support updating or re-associating an agent on a host that is in a non-trusted domain or on a perimeter network.

Recommended Action
If the host is in a non-trusted domain, remove the host (HOST) from VMM in the VMs and Hosts workspace of the VMM console. Then, use the Add Hosts Wizard to add the host and automatically install a new agent.

If the host is on a perimeter network, after you remove the host from VMM, you must manually uninstall the VMM agent from the host computer, install a new agent locally on the host, and then add the host to VMM.

VMM Primeter Host - 03 - Remediate Host Health Job

Notice that the Recommended Action states: “If the host is on a perimeter network, after you remove the host from VMM, you must manually uninstall the VMM agent from the host computer, install a new agent locally on the host, and then add the host to VMM.

So, this means we have to uninstall the local VMM Agent we installed from the original VMM media, and install the updated Agent that includes the Update Rollup. But, how do we do that? Where do we get the update files/updated agent? Is it just an .MSP type of update file?

After Googling, I was alerted to the location of the updated Agent installer, which will be on the VMM Management Server where you have already installed the Update Rollup (in this specific example, UR3). In my lab example, I have installed SCVMM on the E:\ drive. So my location was: E:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\agents\amd64. Notice that there are 2 folders, one labelled “3.2.7510.0”, and another as “3.2.7672.0”. The 3.2.7510.0 folder contains the original media VMM Agent.

VMM Primeter Host - 04 - Updated Agent Installer

If you navigate to the Update Rollup 3 for System Center 2012 R2 Virtual Machine Manager KB article, and check the list of Files that are updated in Update Rollup 3 packages, you will see a reference to the Agent and it’s version of 3.2.7672.0.

VMM Primeter Host - 05 - UR3 KB Article

So now that we know where the updated Agent installer is, what’s left to do? Well, unfortunately, as the instructions indicate, we have to uninstall the existing VMM Agent from the Host, and re-install the Agent using the updated installer (keep in mind that if this is on a Host that is on a perimeter network, then you will have to follow the steps I’ve documented in my How to Add Hyper-V Hosts in a Perimeter Network in VMM 2012 R2 article. As far as I am aware, there is no .MSP-like update that can just be run that will upgrade the Agent. But, if I come across a better method other than uninstall/re-install, I will update this article appropriately.

After you follow those steps for installing the updated VMM Agent, the Host Status should show “OK“, as well as the Host Agent Version.

VMM Primeter Host - 06 - Host Status OK

VMM Primeter Host - 07 - Host Agent Version OK

If anyone has an alternative solution to updating a perimeter Host VMM Agent without uninstall/re-install, please contact me (via the About Me page) and I will include it in this article (with appropriate credit).

Advertisements

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.

How to Add Hyper-V Hosts in a Perimeter Network in VMM 2012 R2


In my home lab environment, I have a single host, which is NOT a member of my lab’s domain. This is due to the fact that I am constantly re-building my lab environment, which includes my Active Directory Domain Controllers. Therefore, I don’t want to add my host to the domain, and then potentially loose access to it when rebuilding (although I could still use the Local Administrator account).

With that being said, I want to add my Host to SCVMM (which is running in a VM on the Host itself). Therefore, I need to be able to add a Host that is not a domain member (aka. a Workgroup host). So, I will be following this TechNet article (http://technet.microsoft.com/en-ca/library/gg610642.aspx), which walks through the process. I will add screenshots to make it easier to follow.

 

You can use the following procedure to add Hyper-V hosts that are in a perimeter network (also known as DMZ, demilitarized zone, and screened subnet) as managed Hyper-V hosts in Virtual Machine Manager. You can only add stand-alone hosts that are in a perimeter network. VMM does not support managing a host cluster in a perimeter network.

NOTE: You can also use this procedure to add a stand-alone Hyper-V host that is in a workgroup and not part of a domain.

Before you can add a host that is on a perimeter network to VMM, you must install an agent locally on the server that you want to add.

To install the VMM agent on the target host

On the VMM product media or network share, right-click Setup.exe, and then click Run as administrator.

SCVMM Workgroup Host - 01 - SetupEXE

On the Setup menu, under Optional Installations, click Local Agent.

SCVMM Workgroup Host - 02 - Optional Installations (Local Agent)

On the Welcome page, click Next.

SCVMM Workgroup Host - 03 - Welcome Screen

Review and accept the software license terms, and then click Next.

SCVMM Workgroup Host - 04 - License Terms

On the Destination Folder page, accept the default location or click Change to specify a different location, and then click Next.

SCVMM Workgroup Host - 05 - Destination Folder

On the Security File Folder page, do the following:

Select the This host is on a perimeter network check box.

SCVMM Workgroup Host - 06 - Security File Folder

In the Security file encryption key box, enter an encryption key, and then enter it again in the Confirm encryption key box.

Security Note: The encryption key is a value that you choose. We recommend that you enter an encryption key that contains a mix of uppercase and lowercase letters, numbers and symbols.

Important: Make note of the encryption key that you use to create the security file. You must enter this same key again when you add the host in the VMM console.

 

Either accept the default location where the encrypted security file will be stored, or click Change to specify a different location to store the encrypted security file.

Important: Make note of the location where you stored the security file. In the “To ensure that the Security.txt file is available to VMM” procedure, you must transfer the security file to a location that is accessible to the computer on which a VMM console is installed.

 

To use a certificate to encrypt communications between the VMM management server and the host, select the Use a CA signed certificate for encrypting communications with this host check box. In the Thumbprint of the certificate box, enter the thumbprint of the certificate.

Note: To obtain the thumbprint of a certificate, open the Certificates snap-in, and then select Computer account. In the Certificates snap-in, locate and then double-click the certificate that you want to use. On the Details tab, select the Thumbprint field. In the lower pane, highlight the thumbprint value, and then press Ctrl+C to copy the value to the clipboard.

When you are finished, click Next.

 

On the Host network name page, specify how the VMM management server will contact the host, and then click Next. You can select either of the following options:

  • Use local computer name
  • Use IP address

If you select Use IP address, click an IP address in the list.

Important: Make note of the computer name or IP address of the host. You must enter this same information again when you add the host in the VMM console.

SCVMM Workgroup Host - 07 - Host Network Name

On the Configuration settings page, accept the default port settings, or specify different ports, and then click Next.

SCVMM Workgroup Host - 08 - Configuration Settings

Important: We recommend that you do not change the default port 5986 for agent communication. The port settings that you assign for the agent must identically match the port setting that the VMM management server uses. By default, the VMM management server uses port 5986 for agent communication with hosts in a perimeter network, and port 443 for file transfers.

On the Ready to install page, click Install.

SCVMM Workgroup Host - 09 - Ready To Install

 

To ensure that the SecurityFile.txt file is available to VMM

On the target host, navigate to the folder where the security file is stored. By default, the location is C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager. The name of the security file is SecurityFile.txt.

SCVMM Workgroup Host - 10 - SecurityFile Location

Transfer the security file to a location that is accessible to the computer on which a VMM console is installed. For example, transfer the file to the computer where the VMM console is installed, to an internal file share, or to a USB flash drive.

 

To add the Hyper-V host in the perimeter network

In the VMM console, open the Fabric workspace.

SCVMM Workgroup Host - 11 - Fabric Workspace

In the Fabric pane, click Servers.

SCVMM Workgroup Host - 12 - Fabric - Servers

On the Home tab, in the Add group, click Add Resources, and then click Hyper-V Hosts and Clusters.The Add Resource Wizard starts.

SCVMM Workgroup Host - 13 - Add Resources - Hyper-V Hosts and Clusters

On the Resource location page, click Windows Server computers in a perimeter network, and then click Next.

SCVMM Workgroup Host - 14 - Add Resources Wizard - Resource Location

On the Target resources page, do the following:

In the Computer name box, enter the NetBIOS name or the IP address of the host in the perimeter network.

In the Encryption key box, enter the encryption key that you created when you installed the agent on the target host.

In the Security file path box, enter the path of the SecurityFile.txt file, or click Browse to locate the file.

In the Host group list, click the host group where you want to add the host.For example, click the Seattle\Tier2_SEA host group.

Click Add.The computer is listed under Computer Name in the lower pane.

Repeat this step to add other hosts in the perimeter network. When you are finished, click Next.

SCVMM Workgroup Host - 15 - Add Resources Wizard - Target Resources

On the Host settings page, in the Add the following path box, enter the path on the host where you want to store the files for virtual machines that are deployed on hosts, and then click Add. If you leave the box empty, the default path of %SystemDrive%\ProgramData\Microsoft\Windows\Hyper-V is used. Be aware that it is a best practice not to add default paths that are on the same drive as the operating system files.

Repeat this step if you want to add more than one path. When you are finished, click Next.

Note: You can ignore the Reassociate this host with this Virtual Machine Manager environment check box. This setting does not apply to hosts in a perimeter network.

SCVMM Workgroup Host - 16 - Add Resources Wizard - Host Settings

On the Summary page, confirm the settings, and then click Finish.

SCVMM Workgroup Host - 17 - Add Resources Wizard - Summary

The Jobs dialog box appears to show the job status. Make sure that the job has a status of Completed, and then close the dialog box.

SCVMM Workgroup Host - 18 - Jobs - Completed

To verify that the host was successfully added, in the Fabric pane, expand Servers, expand All Hosts, expand the host group where you added the host, and then click the host. In the Hosts pane, verify that the host status is OK.

SCVMM Workgroup Host - 19 - All Hosts

Tip: To view detailed information about host status, right-click the host in the VMM console, and then click Properties. On the Status tab you can view the health status for different areas such as overall health, host agent health, and Hyper-V role health. If there is an issue, you can click Repair all. VMM will to try to automatically fix the issue.

Tag Cloud

%d bloggers like this: