In part 1 we installed LINUX and now it is time to get SCOM 2012 ready for LINUX monitoring. There are several steps we need to do: Set up a Resource Pool Import the management packs Setup name resolution Configure the RunAs accounts Assign the RunAs accounts to profiles.
There are sometimes alerts which might contain some strange id’s which are not as informational as you might would like have. One way to find out what is hiding behind this id is to use a SCOM Powershell command. As an example, today I received an alert that looked like this…
SCOM is a great tool for monitoring cross platform systems as for example Linux or other Unix derivate. Although Microsoft invested a lot in cross platform monitoring, one thing I am missing is a way for dynamic grouping Unix/Linux systems in SCOM. What is the problem? As you might know in SCOM you can create […]