- Agent based monitoring
- Agentless monitoring
- Server monitoring
All our environments are automated to automatically install the SCOM agents across different domains which helps us to check the health of the server, to get the server details like IIS, app pools, Performance counters like CPU, Memory, Disk usage, etc.
SCOM needs improvement in phasing out the Silverlight based web platform and instead provide web access for all browsers using HTML5 probably. The API and the knowledge base needs to be improved by Microsoft.
I've used it for two years.
We've had no issues with deployment.
SCOM server needs periodic maintenance to make sure the disk/database has enough space and a lot of alerts across a big environment might come fairly quickly. At times it needs server and service restarts.
We've had no issues with scalability.
I implemented SCOM on my own. You can use SCOM C# SDK or VSAE or GUI to implement SCOM management packs.This was the first monitoring solution we used, but we have moved out the URL monitoring away from SCOM to StatusCake and VictorOps as StatusCake has an easy REST based endpoint for monitoring and VictorOps provides us on call support. We are continuing with SCOM as we need agent based monitoring for our SAAS solutions.
The initial setup is fairly simple if you read the installation documents beforehand and install all the prerequisites properly, otherwise it can be a fairly long task.
I implemented SCOM on my own. You can use SCOM C# SDK or VSAE or GUI to implement SCOM management packs.
It has a good ROI.
Pricing and licensing is fairly OK. If you have a MSDN license, then your dev environments can be set up for free as you can get a dev SCOM license from MSDN. You only have to pay for production SCOM server if you have a MSDN license.
Implement a prototype management pack on the dev environment and analyze all the pros and cons before buying the product. You can get a free six months trial on this also.