Monitoring Linux servers with System Center Operations Manager (SCOM) can be a
migraine inducing but monitoring Linux servers in multiple resource pools from your management servers can be outright impossible. Kevin Holman writes a great article detailing all the configurations for monitoring Linux devices but it only uses one resource pool.
While this article works wonderfully for getting the accounts and profiles set up correctly, I ran into issues when configuring the accounts and profiles for multiple resource pools. Our requirements are as follows:
We configured the Built In Run As Profiles with the Pool A and the Pool A Accounts following Kevin Holman’s steps. We ran into some issues when it came time to set up the Pool B and
Pool B Accounts.
To properly setup the Run As profiles to Manage Linux devices we had to follow the below
steps. This was done for each of the three Run As Profiles. I will use the Unix/Linux Action
Account Profile as our example.
What happens next is a little wonky. When Discovering the agent on the linux device for the Pool A Linux objects we can use the Run As Account because it is distributed to all targets.
But for Pool B we will have to specify the account and input it manually. Select “Set Credentials” while setting up the Discovery. Select the Username and Password option and put in your credentials for Pool B.
The Discovery will seem to stall at the end of the discovery. This initial discovery will allow the Linux Server object to be available to SCOM for discovery. Go back to Pool B Linux Servers Group and change the drop down to Unix/Linux Computer | Unix/Linux Core Library. Enter the server name that you just discovered and add it to the Pool B Linux Servers Group to allow it to be discovered and monitored.