When we were setting SCOM 2022 Teams integration in our environment these are some of the issues and fixes we discovered. For the full setup guide for SCOM 2022, or if you are looking for integrations for older versions of SCOM (2012 R2+) or more functionality, such as bi-directional sync, check out our blog on ‘How does SCOM 2022’s native Microsoft Teams Integration Work?’
Possibly the most anticipated feature of SCOM 2022 is Delegated Administrators! It’s not the shiniest of features but it has long been a pain point of SCOM admins, which have only ever been able to use three pre-defined roles to grant to users (plus read only). In SCOM 2022 you now have the ability to create Delegated Administrators, which overcomes some of the pain points previously felt with rigid roles and permissions.
Good news! SCOM 2022 contains a native integration with Microsoft Teams, replacing the old Skype for Business integration! Once setup, you can expect notifications like the below one in Microsoft Teams channels as desired.
If you’re a SCOM Admin these are the questions you should be asking yourself when it comes to measuring your monitoring success! So, here’s how to tackle these challenges and get the best out of SCOM.
In today’s monitoring world most SCOM admins are pulling data from a range of tools and applications, as well as cloud platforms. It can be difficult to sift through all this data, let alone distill it down into a useful format. SCOM is a great resource for making this happen, and if it’s done well can be a superb monitoring hub for your other applications. But how do you get SCOM to consume data from other sources?
Many organizations aspire to a world where everything is in the cloud. But, in reality most IT enterprises still rely on traditional on-prem monitoring technologies. As a market-leading monitoring tool, SCOM is ideally placed for the job; monitoring both on-prem workloads or workloads that link up to the cloud. So, as SCOM is central to most companies’ monitoring, it is essential you understand how to be successful with SCOM!
A Webhook is an API that delivers data from applications when an action or event occurs. When an event is triggered within the source site, it is seen by the Webhook, which collects the data and sends it to the desired application or URL in the form of an HTTP request. Webhooks are also instant, triggering the delivery of data in real-time, this makes them faster and easier to implement than other methods, like polling.
If you’re looking to integrate SCOM with your other IT applications your main drivers are probably centered around; increasing efficiency, improving stakeholder engagement, and smashing your incident response times!
While SCOM is a valuable monitoring tool, you may also be using a suite of monitoring tools, such as SolarWinds to monitor network devices, VROps to monitor VMware, and Nagios to monitor your Linux devices, as all these tools are best in class. But, you don’t want to be looking in numerous different consoles to gather all your monitoring data!
Bi-directional sync enables data to be sent to and from SCOM and your ITSM tools, in the following ways: a) OUTBOUND Notifications (PUSHES alerts from SCOM to another tool) b) INBOUND Notifications (PULLS updates on alerts into SCOM from another tool) This means you can choose which SCOM alerts to send across to your ITSM tools (Cherwell or ServiceNow), they are then raised as incidents, and then using bi-directional sync, info relating to the incidents is pulled back into SCOM (Incident ID, Configurat
