The path to become a SCOM Master… Ready to take it to the next level? Cameron Dieter

Principal Consultant Started with MOM 2000 Dallas TX, USA Cameron Fuller

@DieterWijckmans Managing Consultant CDM MVP since 2014 They see me rollin’ Dieter Wijckmans

Motto It’s doing common things uncommonly well that brings success…

House of tails dogs charity All donations go 100% to the charity #MMSGIVEBACK

This is tough!

Community first! Ask questions! Don’t hold back Q&A is not only at the end!

Agenda OM managementExploring new universesVisualization

om management

This is tough? Yes! Done clicking!

Automate things Need to do this more than twice a week? Involves more than 5 clicks? * Room for error? Rule of thumb: * Start counting your clicks! Start automating NOW

Keeping it all running Keep SCOM inline Try to keep it in the background Make alerts clear for non technical people… Increase the image of SCOM

Keeping SCOM up to date UR? Tip: always check community New features released regularly Follow the release cycle

Keeping mp’s up to date Don’t update straight away Read manuals! New feature in SCOM2016! MP update tips

Demo Let’s make this easier!

Explore new universes

Something more to do?

Explore new universes RBAC + groupsSysctr 2016Update or not?

Explore new universes OMS = OMG?ACSAEM?

Demo Let’s get the dust cleared up…

visualization

Visualization Business services?Monitor my SLA’s?Distributed Applications!

Do I have a problem? I’m getting alerts so everything works, right? It’s not me, it’s the users. I have everything monitored so I have 360 monitoring Phase 1: Denial

Do I have a problem? Ok people are complaining that they get too many alerts when something happens… Ok I can’t pinpoint right away the issue… I might have room for improvement… Phase 2: Recognition

Do I have a problem? Hmmm how can I change the way SCOM works to get the users of my back? Maybe I can implement SLA’s and SLO’s to show management. That’s it! I’m ready for a change! Phase 3: Acceptance

What do I get out of it? Find the relationships between objects Less alerts Direct root cause analasys Happy users Instant gains

Start small… Rule 1: Start small Rule 2: Keep asking questions Rule 3: Never believe “documentation” Rule 4: Test, test and test.

Phase 1: Get all the building blocks Take your documentation and get all the components lined up and ready to go. Check the health of the components Check the monitoring of the components to avoid false positives

Phase 2: Build the service DA Create the distributed applicationCreate the object groupsFill the object groups with the objects

Phase 3: Define the relationships Check the relationships of the object groups Define the alert flowCheck your test scenario

Let’s reflect

Visualization Can I get a pretty picture?Am I there yet?OK show me!

Demo Let’s see the light…

Key takeaways Don’t be afraid to try…There’s a solution for all monitoring scenariosCan’t find one? Build one!It’s ok to combine other solutions.

Q&A Q&A? Well euhm the official one!Shoot! * * probably no questions anymore…

Thanks!