SCOM is a very powerful tool if deployed and eventually maintained correctly. It is an improvement over MOM 2005. It no longer monitors just a node like MOM 2005 used to do (eg: a server) but it can be made to monitor a whole service.
SCOM is a very powerful tool if deployed and eventually maintained correctly. It is an improvement over MOM 2005. It no longer monitors just a node like MOM 2005 used to do (eg: a server) but it can be made to monitor a whole service.
SCOM 2012 monitors each node and advises you that a particular node is unreachable/down in a very short time. This time a.k.a as the polling time is dependent upon number of nodes, network traffic and the speed of the scom servers and network equipment. Having a short time helps to meet the SLA target.
Unfortunately, when you need to monitor member servers which are not joined to the same domain as the SCOM servers, you need to go through the certificate route (so that you can have the required trust through the certificate). This is very time consuming and very prone to error.
3years.
SCOM requires that all servers are from 2008server upwards. Does not work with Server 2003 or lower. Moreover, the respective service packs need to be installed.
As regards Linux servers, a specific file must be configured so that SCOM is allowed to communicate to.
No particular issues were encountered. If it is allocated the required resources, service pack installed etc, it should have a reasonable performance.
SCOM 2012 was implemented and monitored 300+ servers and various network connections. Issues that were encountered is with respect to servers which were not on the same windows domain as the SCOM servers.
Customer service was fine. However, a trained support team is required so that the SCOM is handled correctly and in a timely manner.
Technical Support:Technical support from Microsoft was always given in a timely manner when required. Technical support advice was analyzed and taken on board when required.
MOM 2005 was used but this supports up to 2003 Server. Having upgraded all servers to Server 2008 upwards necessitated this switch. Finally it proved to be a good choice.
MOM experience helped a lot since the basics are the same. You have to open the required TCP ports and allocate the required resources so that setup succeeds.
It was implemented in-house. A group of engineers designed, planned and implemented SCOM 2012. Their level of expertise was very high and they were MCSE engineers.
The ROI is in the form that the Service Level Agreement (SLA) is met and downtime minimized as possible. This reduced the penalties incurred to us from customers.
Cannot comment on this. I was on the technical aspect of SCOM. However this was given "for free" as part with the SCCM package.
There are various other options, like OP5 and Zabbix but being in a Microsoft environment, SCOM was the way to go.
No comments so far. SCOM has a lot of potential and can give a helping hand in maintaining a healthy network.