Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft System Center 2012 R2 Operations Manager Cookbook

You're reading from   Microsoft System Center 2012 R2 Operations Manager Cookbook Learn how to deploy, configure, and maintain System Center Operations Manager with 50 recipes designed to help you meet the challenges of managing a complex IT system

Arrow left icon
Product type Paperback
Published in Apr 2015
Publisher Packt
ISBN-13 9781782176244
Length 406 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (13) Chapters Close

Preface 1. Architecting System Center 2012 R2 Operations Manager FREE CHAPTER 2. Deploying System Center 2012 R2 Operations Manager 3. Configuring System Center 2012 R2 Operations Manager 4. Operating System Center 2012 R2 Operations Manager 5. Maintaining System Center 2012 R2 Operations Manager 6. Monitoring Applications and IT Services with System Center 2012 R2 Operations Manager 7. Authoring Custom Monitoring Solutions with System Center 2012 R2 Operations Manager 8. Authoring Management Packs in Visual Studio 9. Integrating System Center 2012 R2 with Other Components 10. Reporting in System Center 2012 R2 Operations Manager A. Resourceful Links Index

Discovering a new application in MP Author


The ability to provide custom monitoring to different servers is key to the success of SCOM. We are all familiar with the monitoring that is targeted at SQL Servers or IIS Servers, but SCOM is highly extensible and can be configured to discover custom applications and target specific monitoring for them as well.

The key task when developing custom monitoring is to work out the service model that represents your application. A service model is broadly speaking a description of the classes and their relationships. Once you have this, you can work out how you will identify the servers hosting this application as being different from a server that does not host the application. For example, a SQL Server is identified by the existence of a registry key HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\110\Machines. Later scripts can be used to identify the specific components of SQL that are installed. The registry is used because this is the most efficient...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image