SCOM and OMS a Love Story Modern Management Meets Traditional Enterprise IT Ryan Andorfer Technology Solutions Professional Microsoft Nathan Foreman SCOM Solutions Engineer C.H. Robinson

Ryan Andorfer Nathan Foreman @randorfer @Nate_Foreman 10+ years in IT 3 Year Microsoft MVP MCSE, MCSA, CCNA 10+ years in IT 10+ Years in IT Food: Pizza, Mac ‘n Cheese Food: Wood Fired Pizza, Sushi

OMS Doesn’t have to replace SCOM OMS Introduction OMS Doesn’t have to replace SCOM It uses many of the same theories and structure People Developing OMS Now were in the SCOM space previously Solutions and Intelligence Packs are added weekly List some of the newest solutions User Voice actually influences the Stories when Sprint Planning occurs Microsoft has a Customer Panel with Monthly Calls to keep people up to date

Nathan’s Background

We are (still) a fully integrated SCOM Shop Previous State We are (still) a fully integrated SCOM Shop 3000 SCOM Agents Less than 15 unresponsive agents Custom Management Pack Authoring Strong change control process Working to increase centralization and strengthen IT processes SCOM IS EVERYWHERE

Modern Management meet Enterprise Enterprises have ‘layers’ Multiple teams to get buy off / in Mature change control process On site comfort Stability (and sleep) is highly valued WE KNOW HOW TO CARE AND FEED FOR SCOM

Hello Enterprise, I’m Modern Management Log Analytics is built on SCOM Uses the SCOM deployment infrastructure Uses the SCOM agent Uses MPB to distribute content Helps with the dirty laundry Real time troubleshooting Reporting Ad-hoc time based environment searches SIEM Is still from Microsoft Enterprises have relationships with Microsoft You still have Premier and PSS Support Microsoft comes in for AD/SQL/Exchange assessments OMS hopes to Strengthen these and make some easier Modern Management

Rubber meets the road Deploying Log Analytics

Need to control bandwidth First Trial Need to control bandwidth Use a proxy! BUG ENCOUNTERED! AGENTS CRASHING!

All hands on deck But this is a POC, not Production Microsoft support and engineering engaged Bug identified and triage steps put into place Microsoft Product Team finds the source Fix rolled into the very next UR (UR9) Stability is achieved

Rolling out the Proof of Concept On boarded a representative sample of servers Intelligence Packs Roadshow Security Active Directory SQL ServiceNow Team Networking Change Management Developers

Learnings from Proof of Concept We only want to use specific Solutions on Some servers Privacy Cost/Volume Prod&Dev How do we know if changes are happening? Following Change Management (ITSM) Deploy to Test BEFORE Production SCOM still holds all the Keys OMS Runs on SCOM Rules Agents get their configs from Mangement Servers Group Population is still in SCOM Pack Downloads and Installs are Via SCOM We know how to control SCOM!

Lets act on what we Learned Well Targeted Overrides Tasks to Replace Rules http://GitHUB.org

Use Support forms and the Community Ongoing Usage Keep Using User Voice! Use Support forms and the Community MS will continue to work on building Solutions on OMS We will continue to use SCOM to collect data Events Perf Alerts Custom Data We will be the Scalpel OMS the Muscle

And Then … Discuss: Evaluations: Ask your questions-real world answers! Plenty of time to engage, share knowledge. Discuss: Evaluations: Please provide session feedback by clicking the EVAL button in the scheduler app (also download slides). One lucky winner will receive a free ticket to the next MMS!