Category: Windows Server

Monitoring VMware (ESX/ESXi) with OMS

We all know monitoring Hyper-V and/or SCVMM with OMS is rather straight forward, and native. However, what about VMware (ESX/ESXi)?

In my VMware environment, I am using ESXi Host version 5.5 and vCenter version 6.0.

The following post is to help you monitor your ESX/ESXi environment with OMS.

  • First, you will need to enable the ESXi Shell, or SSH on your ESXi host, see HERE how
  • Next, you will need to configure the syslog(s) on your ESXi host, see HERE how

My ESXi server’s IP, and I will be forwarding the syslog(s) to my vCenter Windows Server IP To be safe, I am going to configure both port 514 UDP and TCP .


  • Remember to disable the firewall(s) on your vCenter Windows server
  • Now on your vCenter Windows Server, you will need to deploy the OMS Agent (Microsoft Monitoring Agent), see HERE how
    • Once your vCenter server is communicating with OMS, we can move on to the next step
  • Within OMS, if you haven’t already, you will need to enable “Custom Logs“; Settings > Preview Features > Enabled Custom Logs


  • Next, set up the following syslog file as your custom log on your vCenter server. In my case, my ESXi hostname is ‘RaviESXi’ and its IP is
  • Followed by importing your syslog into OMS for the first time (see below for instructions)


For me, that path translates to, “C:\ProgramData\VMware\vCenterServer\data\vmsyslogcollector\RaviESXi\syslog.log

In my example, I then created an OMS custom log named “VMwareWin” for ESXi syslog. (By default, _CL suffix will be automatically added, which will result as, “VMwareWin_CL”) If you are unfamiliar with OMS’ Custom Logs, see HERE.

Once you have completed this step, it make take some time for your data to start showing up in OMS. Give it an hour or so…

  • Now we can start creating some custom fields within OMS. For example, ESXi Hostname, vmkernel, hostd, etc. See HERE about OMS’ custom fields in log analytics.
    • If you have done everything correctly, you should have custom logs and custom fields similar to this:



  • Now  you can start creating some dashboards with some custom queries!

For example, here’s one query I tested with and thought was worthy for its own dashboard:

All events and number of occurrences:

Type=VMwareWin_CL | measure count() by VMwareProp_CFDashboard1Example

Of course the number of queries and dashboards is endless at this point. Feel free to let me know your thoughts and some queries/dashboards you have come up with!

Lastly, don’t forget to add some important syslog OMS Data Log Collection, here is what I have configured:




SCOM 2012 | 2012R2 Data Access Service SPN Not Reigstered


You got the alert, now what? To be honest, I won’t even waste my time creating my own post on this, as there are several blogs on this. A blog post I typically have referred to in the past is, Neil Phillips. For the solution to the Data Access Service SPN Not Registered, have a visit HERE.


Deploying OMS Agent for On-Premise Server(s)

This post is intended for monitoring Windows based servers with OMS. For starters I am going to assume the following prerequisites have been met (see below). In addition I am going to assume you are not using SCOM 2012R2 (UR6 or better) at the moment. Okay, so let’s begin!

  1. Azure Environment Setup — Check
  2. Azure Operational Insights Created — Check (see post here)
  3. OMS Workspace Created — Check (see post here)
  4. Monitor On-Premise Servers — See below


For my demo, I am using a Windows 2012R2 server, so I will be making use of the x64 agent. Download the agent on your machine, and begin the installer. Take note (copy the Workspace ID and Key(s)) as you will need them later.


  • Start/Launch the agent installer


  • We will be connecting to Azure (not SCOM)


  • The Workspace ID and Workspace Key can be retrieved from your OMS settings page.




Once the agent install is complete, we can view the OMS/Azure configuration properties within the agent configuration, as seen below:


  • If we go back to our OMS portal, we can now see we have another server we are now monitoring in OMS 🙂


  • At this point we are not really capturing much data, so let’s configure some log data capturing. For now, I just setup Windows event logs, looking for Event IDs 6006 and 6008.


  • About 3 hours later (for me at least) I started to see data being collected. As we bring more agents into OMS and/or couple our on-prem SCOM environment, we will start to see a wealth of data. (Remember 500Mb of data is free, anything more you will need to upgrade your Azure subscription)




Installing System Center Operations Manager (SCOM) 2016 Step by Step (Technical Preview 5)


This post I will be installing System Center Operations Manager 2016 (SCOM) –  Technical Preview 5 (TP5). Technical Preview for both System Center 2016 and Windows Server 2016 was recently released, April 27th.

Here is some of the background information. As this post will concentrate on the installation of SCOM 2016 TP5, I am going to omit the setup and configuration of the Domain Controller, Windows Server 2012R2 for both SCOM Management Server and SQL Server (Please note, I am using SQL Server 2014 SP1, both servers on Windows 2012R2).

Environment:  Virtual; ESX 5.5 Hypervisor

SCOM Management Server:

  • Windows Server 2012 R2 — SCOM2016TP5
  • 4 vCPU (2.00GHz)
  • 12 GB memory
  • 100GB Diskspace
  • 1GB vNIC

SQL Server:

  • Windows Server 2012 R2 — SCOMSQLTP5
  • SQL Server 2014 SP1
  • 4 vCPU (2.00GHz)
  • 12 GB memory
  • 200GB Diskspace
  • 1GB vNIC

Service Accounts:

Domain\Account Description
RAVILOCAL\scom_aa SCOM Action Account
RAVILOCAL\scom_da SCOM Data Access/SDK Account
RAVILOCAL\scom_sql_read SCOM SQL Reader
RAVILOCAL\scom_sql_write SCOM SQL Writer
RAVILOCAL\scom_admin SCOM Administrators Group
RAVILOCAL\sql_sa SQL Service Account
RAVILOCAL\sql_ssrs SQL Service Reporting Services Account


Let’s begin:



I will not be installing Reporting on this server, as I will install this on the SQL Server (I will create a post for this later…)


Well, looks like I will need to install the Report Viewer Controls and need to install some IIS components for the Web Console.

  • For the Reports Viewer Controls prerequisites, you can visit the following post for the instructions, HERE.
  • For the Web Console/IIS components prerequisites,  you can visit the following post for the instructions, HERE.


Looks like I still need to meet a few more prerequisites…


You will need to apply the following commands (unfortunately I could not execute in PowerShell, so you will need to use Command Prompt (as Administrator)).

  1. cd %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\
  2. aspnet_regiis.exe -r
  4. Reboot your server…

Back to to installation…..





Since this is a lab, I installed the databases on the same SQL instance. Best practice, use dedicated instances or better yet, dedicated servers…





Whoops, I forgot to add the SCOM service accounts as local administrators on the SCOM Management Server….


Okay, back to the installation…



I recommend always keeping this off, and manually updating your SCOM infrastructure.



Let this run, go for a break, coffee, smoke, whatever….


Yay! All good!




Right off the bat, looks like there are a new features, like, “Tune Management Packs” I will get into this in another post…


ThoughtsAs you may have noticed, the install is almost identical to the 2012R2 and it appears not much has changed in terms of the install.



SCOM 2012 SP1 to SCOM 2012R2 Upgrade Prerequisites

When upgrading from SCOM 2012 SP1 to 2012R2, you will need to install the following prerequisites:

  2. Microsoft System CLR Types for SQL Server 2012

Of course you can also download them straight from Microsoft. The links are provided below.

SCOM 2016 Technical Preview 5 (TP5)

SCOM 2016 (RTM) along with the System Center 2016 suite and Window Server 2016 are only months away from release. Microsoft just released System Center and Server 2016 TP5 today. Check out the LINK for more information. I will be setting up monitoring with SCOM 2016 TP5 and Server 2016TP5 in the next few days, so feel free to check back in.


Azure Site Recovery (ASR) – Windows 2016 (TP4)

In the event you are running a lab/demo for Azure ASR (Azure Site Recovery) and want to use the latest and greatest Windows 2016… STOP! Turns out Windows Server 2016 – Technical Preview 4 (TP4) is not supported at this time. So, hopefully you read this and don’t waste your time, like me. 🙂 Note, Windows Server 2012 R2 is supported, and works just fine (obviously). I will (soon) be posting a complete Azure ASR setup for Windows Server 2012R2 (VMs) on VMware ESX 6.0.

Of course the ASR Wizard did not indicate any issues at the time of running the installer, but definitely got this error nearing completion.

7 - Install OnPrem Components Wizard (3) 7 - Install OnPrem Components Wizard (Error)