RE-POST: This blog is bought to you by Lydia Shu – Content Writer @Squaredup To our SCOM Community – thank you for making the first worldwide virtual SCOM event such a huge success! As co-hosts of SCOMathon 2020 that took place last week, we are happy to have provided a platform for the SCOM community to get together, learn and connect.
Looking to get some REST endpoints monitors quickly? Follow the below steps to setup a could REST monitors in about 15 minutes (weather in this demo).
Looking to get some traction for urgent alerts? If you’ve got fifteen minutes to follow the below steps you can setup an Alert Subscription that sends alerts directly to Slack.
Nathan Foreman, our solutions superstar here at Cookdown, shares his knowledge on how to successfully blend data sources to create a beautifully populated CMDB, as well as tips on how to customise and maintain data quality. Nathan talked us through the process of using ServiceNow’s out of the box Identification and Reconciliation Engine (IRE) to ensure a smooth integration of a multi-source CMDB.
With SCOM 1802/1807 reaching end of life earlier this year and with SCOM 2012 R2 Mainstream support over (at the end of 2017), many of you are looking at your SCOM upgrade options. So what options are there?
Management Packs contain the actual monitoring (the workflows themselves) as well as extend the SCOM platforms functionality and are critical to getting your new SCOM Management Group up and running. The good news is most of SCOM Management Packs that worked with SCOM 2012 R2 work right through to SCOM 2019, so you are safe to import them into your new Management Group.
If you know which MPs your overrides are stored in, then migrating your current effective tuning is as easy as exporting all of your override MPs, and then importing them into your new SCOM Management Group, assuming you have already imported the MPs containing the monitoring itself. As you also know, in most SCOM deployments, this is never reality across the board.
