Tracking Linux and UNIX computers is an ask I get frequently from customers leveraging Service Manager 2012 R2 (SCSM) for asset tracking. A common trait of these customers is the next question they ask:
“How can I add Linux and UNIX computers to my CMDB?”
Because SCSM was actually originally derived from the System Center Operations Manager (SCOM) platform, SCSM can utilize class definitions from SCOM management packs (MPs). Here, I will quickly show you how to add a generic UNIX / Linux Computer class for tracking assets, even when you do not use SCOM for monitoring Linux and UNIX computers in your environment.
Earlier in the SCOM 2012 release cycle, Microsoft added Universal Linux and UNIX computer monitoring to support additional distributions, like CentOS. The SCOM management packs that implement this monitoring include definition of a generic UNIX / Linux Computer class that makes the perfect foundation for “light” UNIX / Linux Computer asset tracking when no automated collection process is in place.
Retrieving the Management Packs
The first two in the list below come on the SCOM installation media in the \ManagementPacks folder
The rest come from the \Universal folder in the extract of this download, “System Center 2012 Monitoring Pack for UNIX and Linux Operating Systems”
Importing the MPs into Service Manager 2012
To add a generic UNIX / Linux Computer class, import these SCOM management packs into SCSM in the order shown:
The result is a distribution and version agnostic class named simply “UNIX/Linux Computer”.
You will find you can create a custom view in the Configuration Items area of the SCSM Console and create and view instances as you wish. The result is a usable class definition that will enable light asset tracking for orgs without Operations Manager 2012 monitoring in place for Linux and UNIX computer classes. You can also add properties to this class to support more detailed UNIX and Linux computer tracking if you wish. A few of the UNIX/Linxu Computer class properties are shown in the screenshot below.
And if you do have SCOM…
If you do have SCOM monitoring in place, you should look at how you can add custom classes easily through a process called “Whitelisting”. See articles on whitelisting SCOM CI classes in SCSM HERE.