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!
- Azure Environment Setup — Check
- Azure Operational Insights Created — Check (see post here)
- OMS Workspace Created — Check (see post here)
- 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)