Tuesday, September 2, 2014

SCOM 2012x & UX Monitoring. What UX Agents Are Present? And What Version, Build & Architecture?

When using SCOM 2012x to monitor UX based workloads it’s a hard requirement to have the correct UX MPs imported. Simply because these very same UX MPs contain the UX Agents as well. And when you don’t have the correct UX MPs imported, monitoring won’t happen at all because the UX Agents are missing.

So how about a quick check in order to see what UX Agents are available in your SCOM 2012x environment and of what build, version and architecture they’re?

Procedure 01: UX Agent check in SCOM 2012x Console

  1. Open the SCOM 2012x Console with SCOM Admin permissions > Monitoring > Monitoring > Discovered Inventory;
  2. Right click in the middle pane > Change Target Type > select the radio button View all targets > type in the Look for box: unix/linux supported agents. Only one target remains now;
  3. Select UNIX/Linux Supported Agents > OK.
  4. Now you’ll get an overview of all UX Agents present in your current SCOM 2012x environment:
    image

As you can see, my test lab is running behind in the regular update cycle Smile.

This way you have a quick overview of the UX Agents present in your environment.

But this is only one step of a TWO step procedure. Because those very same packages must be present on your Management Servers and/or Gateway Servers as well.

Procedure 02: UX Agent Package check on SCOM 2012x MS/GWs

  1. On a SCOM 2012 R2 MS server: Go to ~:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\AgentManagement\UnixAgents\DownloadedKits and check whether the packages are available;
  2. On a SCOM 2012 R2 GW server: Go to ~:\Program Files\System Center Operations Manager\Gatewa\AgentManagement\UnixAgents\DownloadedKits and check whether the packages are available.

Recap
This is a quick method in order to find out in what shape SCOM 2012x is before you start enabling the monitoring of UX based workloads. This way you know where to start (most of the times it starts with updating the UX MPs which are present by default and adding the required ones, suiting your UX monitoring requirements.

No comments: