Play for serendipity...
Play for serendipity...
System Center Orchestrator
When passing alerts from SCOM onto a downstream system for notification such as ticketing or email, there tends to be two approaches. Override and disable all alert traffic that isn’t immediately actionable, or Put a process/tool in place to automatically…
When using a runbook to pull traffic out of SCOM 2012 to pass onto a different system or take some sort of automated action, the logical way to start one of those runbooks would be with the ‘Monitor Alert’ activity.…
One possible way of dealing with shipping alert traffic from SCOM to a ticketing system or ECA would be to use subscriptions within SCOM to flag the alerts and then simply have Orchestrator pass all flagged alerts onto the next…
Many SCOM admins and users have scripted solutions to help put their machines into maintenance mode in SCOM 2007. There are a ton of great blogs out there on doing this. For SCOM 2012, however, those same scripts will not…
The OIT is a toolkit provided to help you create custom integration packs for System Center Orchestrator (SCOrch). In this example, I have created a custom DLL that contains code to help get ahold of monitors, rules and management packs…