Good news! Cookdown Alert Sync 1.0 is now avaliable, allowing ServiceNow incidents to be automatically raised for SCOM alerts That’s great… now who is Cookdown? and how does Alert Sync work?

If you’ve ever worked with SCOM then you’ll know it needs a little love to get the most out of it. Together with Tao Yang MVP, I co-presented a session called “20 Operations Manager Tips in 20 Minutes” at Experts Live USA this year which brings together many of the SCOM tips and tricks we’ve accumulated over the years. That session wasn’t recorded, so we decided to publish the tips here for everyone to benefit from. It’s time to get your SCOM game on.

Have you ever wanted to detect a monitoring condition on an agent (Lets call it ProdWebser-01) and follow up the condition with a custom to either remediate the issue or get additional data for the alert? Great Idea, leveraging the agent is one of the best strengths of SCOM.

As you well know, many organisations are now moving to Office 365 in either a hybrid environment (Exchange on premise with Office 365 integration) or full cloud capacity. Yet, Microsoft still remains unable to provide much detail on how issues or outages impact your resources specifically – it's just not enough to know that globally "Some users or tenants may be affected". Your business needs to know if users are suffering and what proportion are impacted.

If you’re developing a management pack with custom UI and/or .NET modules you’ve gone through the steps of getting your DLL recognized by the engine and loaded as an Assembly or DeployedAssembly depending on the project (here’s an SCSM example). Durning an ongoing project constantly updating the resource mpx file to have the correct QualifiedName can be frustrating, time-consuming, and error-prone.