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

Archive for November, 2014

SCSM Dashboard – Expit EnSight – Part 1: Introduction

As was requested by one of my subscribers, the following is a series evaluating the SCSM Dashboard “Ensight” by Expit.

To start, here’s an introduction.

What is Expit EnSight?

An Advanced Dashboard and analytics platform  for Microsoft System Center Service Manager.

Service Manager data analysis is simplified with Expit EnSight. Expit EnSight for Service Manager 2012 provides a comprehensive analysis and monitoring platform for events in Service Manager tailored for IT managers and NOC facilities.

Using EnSight, users can easily sort tickets by source, category, support group or the status of every ticket during the current month or within a specific time range. The dashboard also gives decision makers team workload viewing capabilities to monitor team workload distribution.

In the next article, I’ll walk through the download process, since it isn’t very straight forward.

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).

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.

Tag Cloud

%d bloggers like this: