- Management Packs from Microsoft don't support Fedora
- Authentication on VM Amazon are certificate based by default
When SCOM detect Fedora, it stop straight forward:To get the Linux version, SCOM execute this shell script here:By the way, this folder also contains RPM package installed next (daemon). Getting on our goal will need works...
- Create our own Management Pack for Fedora.
- Disguise Fedora as if it was a Red Hat by fooling SCOM.
The first one is the more elegant, but it will take lot of time to get it and then to keep up. So i preferred the second one, as a Fedora is not that far from a Red Hat...
Changes on Linux Amazon EC2
Then you need to set a root password:
Then reload configuration:
Then create a SCOM account:hostname check
By default, the VM got it's internal IP as hostname. SCOM will deploy an RPM to get a daemon running, and will generate a certificate to authenticate.
The RPM package from Microsoft depend at least on this 2 libraries:
I recommend you to copy over the rpm (scx-1.0.4-248.rhel.5.x86.rpm), to check for the good installation result. Else, it will be SCOM that do it during discovery, and error messages are not that explicit.
Moreover, it shows up the name with which the certificate is made:
You can always remove it:TCP Ports
- port 1270 (scom agent)
You will have to set up the Amazon firewall to get these 2 ports reachable. If port 1270 is not reachable, SCOM raise an error about time out, which doesn't help a lot. Traffic to this ports is confirmed by a network trace:/etc/redhat-release
By default, Fedora create a symbolic link from /etc/fedora-release to redhat-release. You must break it and create a true redhat-relase file with this text inside::
Changes on SCOM 2007 R2
Tasks to do:
- Allow WinRM to get basic authentication
- Import Management Packs Linux/Unix generic and Red Hat
- Add a Basic Authentication account to log on Linux (not root)
- Add a Basic Authentication account to log on Linux (Root)
- Link them to profiles "Unix Action Account" and "Unix Privileged Account"
- Discover the VM and sign certificate
Adding the VM is straight forward if you followed the tasks before. So i will cover the problems i met.
At the beginning, the VM is not monitored and seen as unknown:
Here we go, your VM is now monitored by SCOM 2007 R2.
Here are some screenshots once it works: