Book Image

Getting Started with Microsoft System Center Operations Manager

By : Kevin Greene
Book Image

Getting Started with Microsoft System Center Operations Manager

By: Kevin Greene

Overview of this book

Most modern IT environments comprise a heterogeneous mixture of servers, network devices, virtual hypervisors, storage solutions, cross-platform operating systems and applications. All this complexity brings a requirement to deliver a centralized monitoring and reporting solution that can help IT administrators quickly identify where the problems are and how best to resolve them. Using System Center Operations Manager (OpsMgr), administrators get a full monitoring overview of the IT services they have responsibility for across the organization - along with some useful management capabilities to help them remediate any issues they've been alerted to. This book begins with an introduction to OpsMgr and its core concepts and then walks you through designing and deploying the various roles. After a chapter on exploring the consoles, you will learn how to deploy agents, work with management packs, configure network monitoring and model your IT services using distributed applications. There’s a chapter dedicated to alert tuning and another that demonstrates how to visualize your IT using dashboards. The final chapters in the book discuss how to create alert subscriptions, manage reports, backup and recover OpsMgr, perform maintenance and troubleshoot common problems.
Table of Contents (18 chapters)
Getting Started with Microsoft System Center Operations Manager
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Agentless monitoring


With agentless monitoring, a management server, or another computer with the OpsMgr agent installed acts as a proxy agent for the agentless device to deliver monitoring data back into the Operations console.

The most common use of agentless monitoring that you'll come across in OpsMgr is where you monitor Microsoft Windows servers that are configured in a cluster and the cluster nodes act as a proxy agent for the virtual cluster object.

For example, let's say you create a Hyper-V Failover cluster with two servers named Node1 and Node2. When you run through the Failover Cluster wizard to initially create the new cluster, you'll be prompted for a virtual cluster name and IP address, which you can name Cluster1. Now, when you deploy the OpsMgr agent to both Node1 and Node2 and enable the Agent Proxy setting on each node, the virtual cluster object for Cluster1 will show up automatically in the Agentless Managed section of the Administration workspace.

In Figure 4.1, you can...