Agentless Monitoring 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

System Center 2012 – Operations Manager can gather performance and availability data on a computer that does not have an agent installed by using a proxy agent that is installed on another computer. Use agentless-monitoring of computers when it is not possible or desirable to install an agent on a computer.

An agentless-managed computer is a Windows-based computer that is discovered by using the Operations console. You assign an management server or agent-managed computer to provide remote (proxy) agent functionality for the computers.

Agentless-managed computers are managed as if there is an agent installed on them. Not all management packs work in agentless mode. For more information, see the documentation for the management packs you are running.


Agentless management of a computer will not work if the agentless-managed computer and its proxy communicate through a firewall. A management server will not collect descriptions for events or publishers that are present on an agentless managed computer but are not present on the proxy agent.

For information about configuring an agent-managed computer as a proxy for agentless-managed computers, see How to Configure a Proxy for Agentless Monitoring.


An agentless-managed computer places greater resource requirements on a management server than an agent-managed computer.

To change an agentless-managed computer to an agent-managed computer, do the following:

  1. Delete the agentless-managed computer from the management group by right-clicking the computer in Agentless Managed in the Administration workspace and then clicking Delete.

  2. Deploy the agent to the computer. For more information, see Managing Discovery and Agents.

Agentless Monitoring Compared to Agentless Exception Monitoring

Agentless monitoring provides monitoring of computers without agents by using a proxy agent and applying those management packs that support agentless monitoring. Agentless Exception Monitoring (AEM) redirects hardware, operating system, and application crash information to Operations Manager, which can aggregate, view, and report on error reports that are sent by the Windows Error Reporting service. For information on AEM, see Client Monitoring Using Agentless Exception Monitoring in Operations Manager.

You can monitor a computer without an agent by using either agentless monitoring, AEM, or both.