So you installed SCOM, imported the Management Packs and started monitoring. Now the real fun starts. How about the so famous 360 degree monitoring? Is it only marketing mumbo jumbo or not? How to get the most out of Distributed Applications? How about creating Classes for your specific monitoring needs? And do both – and more – without taking a deep dive into hard core Management Pack authoring? And when SCOM starts having issues, how to solve them? Where to start? In this session Marnix will show you how to get things done in a fast and easy manner. Also he’ll show you how to start troubleshooting in a consistent manner, pinpointing some common issues and how to solve them.

2. Microsoft NDA Confidential
@MarnixWolf
Marnix Wolf
Senior consultant
Blogger
SCCDM MVP

3. 360⁰ monitoring. How real does it get?
DAs. The nuts and bolts
Custom Classes as coat hangers
Common SCOM pain points & issues
How to monitor and remedy SCOM
Troubleshooting flow

5. OpsMgr 2012 R2
+
GSM
+
System Center Advisor

9. DAs
The nuts & bolts

10. Aggregate Monitors
pitfall

11. Blank (Advanced)
All Contained Objects

13. http://thoughtsonopsmgr.blogspot.nl/2014/02/om12x-
distributed-application-horror.html

14. Custom Classes
As coat hangers

16. REVERSE DISCOVERY
Windows Server Computer
Registry (Filtered)
• BEST PRACTICE

17. Create a Group with required Windows Servers;
Enable the Discovery for the new Class, using the new Group;
Class will be Discovered, resulting in Objects related to the Class
Monitors/Rules/Views can be built now, targeted against that Class

19. Common SCOM pain points &
issues

22. SSC Health Reports
OM 12 Self Maintenance MP

23. Troubleshoo

26. Resources

27. www.blogs.catapultsystems.com/cfuller/
www.blogs.technet.com/kevinholman/
www.scug.be/dieter/
www.bictt.com/blogs/bictt.php
www.blog.tyang.org/
www.smitpj.blogspot.nl/
www.thoughtsonopsmgr.blogspot.com