Install Trend
View Install Data
| Date | Install Count | Change |
|---|---|---|
| 2026-09-09 | 0 | - |
| 134 days of no change | ||
| 2026-04-27 | 46 | -46 |
| 15 days of no change | ||
| 2026-04-11 | 47 | -1 |
| 2026-04-10 | 48 | -1 |
| 3 days of no change | ||
| 2026-04-06 | 49 | -1 |
| 4 days of no change | ||
| 2026-04-01 | 50 | -1 |
| 2 days of no change | ||
| 2026-03-29 | 51 | -1 |
| 1 days of no change | ||
| 2026-03-27 | 52 | -1 |
| 2 days of no change | ||
| 2026-03-24 | 53 | -1 |
| 18 days of no change | ||
| 2026-03-05 | 54 | -1 |
| 33 days of no change | ||
| 2026-01-30 | 57 | -3 |
| 2026-01-29 | 58 | -1 |
| 3 days of no change | ||
| 2026-01-25 | 59 | -1 |
| 1 days of no change | ||
| 2026-01-23 | 61 | -2 |
| 7 days of no change | ||
| 2026-01-15 | 64 | -3 |
| 1 days of no change | ||
| 2026-01-13 | 66 | -2 |
| 1 days of no change | ||
| 2026-01-11 | 68 | -2 |
| 8 days of no change | ||
| 2026-01-02 | 69 | -1 |
| 2026-01-01 | 70 | -1 |
| 2025-12-31 | 71 | -1 |
| 10 days of no change | ||
| 2025-12-20 | 72 | -1 |
| 10 days of no change | ||
| 2025-12-09 | 73 | -1 |
| 48 days of no change | ||
| 2025-10-21 | 72 | +1 |
| 14 days of no change | ||
| 2025-10-06 | 71 | +1 |
| 118 days of no change | ||
| 2025-06-09 | 70 | +1 |
| 20 days of no change | ||
| 2025-05-19 | 69 | +1 |
| 18 days of no change | ||
| 2025-04-30 | 68 | +1 |
| 109 days of no change | ||
| 2025-01-10 | 67 | +1 |
| 71 days of no change | ||
| 2024-10-30 | 65 | +2 |
About
The Cookdown SCOM Connector is the easiest way to integrate Microsoft System Center Operations Manager (SCOM) and ServiceNow, synchronizing Alerts, Incidents, and CIs.
No additional services to install and maintain, or PowerShell scripts to manage. Simply install this Connector app from the store and import the associated Management Pack into SCOM and you’re ready to start syncing.
Key Features
- Control exactly which alerts are sent to ServiceNow using familiar SCOM alert criteria
- Use conditions to choose when to create incidents or other records
- Match alerts to CMDB items when the SCOM object Ids are present
- Full bi-directional sync of SCOM alerts with ServiceNow incidents, for example:
- SCOM Ticket ID populated with ServiceNow incident number
- SCOM Resolution State updated to reflect ServiceNow incident workflow
- Automatically reset SCOM monitor when ServiceNow incident is closed
- High availability out of the box by using SCOM Resource Pools
- Delayed Incident creation with customizable wait rules
- Supports SCOM 2012 R2 and later
- Suppress incident creation when a SCOM server down alert has been raised.
- Support complex scenarios and customizations with advanced scripting.