Using the Administration Workspace in Operations Manager

 

Updated: May 13, 2016

Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager

In the System Center 2012 – Operations Manager Operations console, the Administration workspace is the primary workspace for administrators. You use the Administration workspace to configure a management group and its managed objects.

When you first open the Administration workspace or when you click Administration in the navigation pane, the Administration Overview opens, which displays task links for any required or optional configuration steps that have not been completed yet.

The sections below describe the different options in the Administration workspace and link to more detailed information about the task or option.

Connected Management Groups

You can connect management groups to enable the forwarding of alerts and other monitoring data from a connected management group to the local management group. Tasks can be initiated from a local management group to run on managed objects of a connected management group.

Use Connected Management Groups in the Administration workspace to connect a management group or to edit the properties of a connected management group.

For more information, see Connecting Management Groups in Operations Manager.

Device Management

You can use Device Management in the Administration workspace to perform configuration of specific management servers, agent-managed computers, agentless-managed computers, UNIX servers, and Linux servers. The following table summarizes the uses of the items in Device Management and provides links to more detailed information.

Item

Use

For more information

Agent Managed

To modify the configuration of agent-managed computers, such as:

  • Change the primary management server for agent-managed computers.

  • Repair the agent installation.

  • Uninstall an agent.

  • Override the management group agent heartbeat settings on a specific agent. A heartbeat is a periodic pulse from an agent to its management server.

  • Configure an agent-managed computer as a proxy for agentless-managed computers.

Agentless Managed

To change the proxy agent for an agentless-managed computer. The proxy agent can be any agent-managed computer in the management group configured to be a proxy.

Agentless Monitoring in Operations Manager

Management Servers

To modify the configuration of management servers, such as:

  • Override the management group heartbeat failure setting and configure the number of missed heartbeats a management server will allow for an agent before it changes the state of the respective computer to critical.

  • Override the Management Group Manual Agent Installs setting and configure a management server to reject or put in Pending Management agents installed with MOMAgent.msi.

  • Configure a management server as a proxy for agentless managed computers.

  • Configure the Internet proxy settings for a management server.

Pending Management

To approve or reject an agent that was installed with MOMagent.msi if the management group for the agent is configured to Review new manual agent installations in pending management view but not Auto-approve new manually installed agents. Agents pending approval are displayed for this item.

Process Manual Agent Installations

UNIX/Linux Servers

To modify the configuration of agent-managed UNIX and Linux servers.

Management Packs

When you select Management Packs in the Administration workspace, you see a list of all management packs imported into your management group. When you right-click an individual management pack in the results pane, you can view its properties, delete it, or export any customizations to another management group. You can use links in the tasks pane to create, import, and download management packs.

For more information, see Using Management Packs.

Network Management

You can use Network Management in the Administration workspace to discover network devices and managed discovered network devices. The following table summarizes the uses of the items in Network Management and provides links to more detailed information.

Item

Use

For more information

Discovery Rules

  • To create rules for discovering network devices

  • To modify existing discovery rules

How to Discover Network Devices in Operations Manager

Network Devices

To view properties of discovered network devices

Monitoring Networks by Using Operations Manager

Network Devices Pending Management

To retry or reject discovered network devices that are pending management

How to Discover Network Devices in Operations Manager

Notifications

Notifications generate messages or run commands automatically when an alert is raised on a monitored system. By default, notifications for alerts are not configured. For Operations Manager users to be notified immediately when an alert is generated, you need to configure a channel for notifications, add subscribers, and then create a notification.

In Notifications in the Administration workspace, you can create channels, subscribers, subscriptions, and modify the channels, subscribers, and subscriptions that you create. For more information, see Subscribing to Alert Notifications.

Product Connectors

Product connectors are used to synchronize Operations Manager data with other management systems such as those that monitor non-Windows computers or create trouble-tickets. Product connectors can integrate a deployment of Operations Manager into another management platform or connect other management systems into a full Operations Manager management solution. Any product connectors that you integrate with Operations Manager will be displayed in this section of the Administration workspace.

When you install Operations Manager, two internal product connectors are installed. These are used by Operations Manager.

For more information, see Connecting Operations Manager With Other Management Systems.

Run As Configuration

You can use Run As Configuration in the Administration workspace to manage Run As accounts and profiles. The following table summarizes the uses of the items in Run As Configuration and provides links to more detailed information.

Item

Use

For more information

Accounts

To modify the credentials and distribution for Run As accounts.

Managing Access in Operations Manager

Profiles

To add, edit, and remove Run As accounts associated with a Run As profile.

Managing Access in Operations Manager

Security

In Operations Manager, operations such as resolving alerts, running tasks, overriding monitors, viewing alerts, viewing events, and so on have been grouped into user roles, with each user role representing a particular job function. Role-based security allows you to limit privileges that users have for various aspects of Operations Manager. In Security in the Administration workspace, you can add and remove users to specific user roles. You can also modify the properties of user roles that you create.

For more information, see Implementing User Roles.

Settings

The following table summarizes the settings you can manage in Settings in the Administration workspace.

Item

Use

For more information

Agent Heartbeat

Agents generate a heartbeat at specific intervals to ensure they are operating properly. You can adjust the interval.

How Heartbeats Work in Operations Manager

Alerts

  • To configure alert resolution states.

  • To configure automatic alert resolution.

Database Grooming

To configure how long different types of data should be retained in the operational database.

Maintenance of Operations Manager

Privacy

To modify the settings for the following programs:

  • Customer Experience Improvement Program (CEIP)

  • Operational Data Reporting

  • Error Reporting

Sending Data to Microsoft in the Deployment Guide

Reporting

Configure the path for the reporting server.

Using the Reporting Workspace in Operations Manager

Web Addresses

Designate web addresses for the Web console and online company knowledge.

How to Connect to the Web Console

Server Heartbeat

Configure the number of missed heartbeats before the management server pings the agent-managed computer.

How Heartbeats Work in Operations Manager

Server Security

Specify how the management server should handle manually-installed agents.

Process Manual Agent Installations