Home » System Center Operations Manager 2007 » Agentless Exception Monitoring (AEM)


Welcome to contoso.se! My name is Anders Bengtsson and this is my blog about Azure infrastructure and system management. I am a senior engineer in the FastTrack for Azure team, part of Azure Engineering, at Microsoft.  Contoso.se has two main purposes, first as a platform to share information with the community and the second as a notebook for myself.

Everything you read here is my own personal opinion and any code is provided "AS-IS" with no warranties.

Anders Bengtsson

MVP awarded 2007,2008,2009,2010

My Books
Service Manager Unleashed
Service Manager Unleashed
Orchestrator Unleashed
Orchestrator 2012 Unleashed
Inside the Microsoft Operations Management Suite

Agentless Exception Monitoring (AEM)

Operations Manager client monitoring mode enables the administratorsto monitor operating systems and applications for error. Client monitoring configures clients to send error reports to an Operations Manager Management Server insted of Microsoft. With the reporting function client monitoring mode can then generate reports based on these errors. Error reports can be send from the Ops Mgr server to Microsoft. Two good things about AEM are that clients dont need a agent and all client settings are controlled by a group policy.

Windows Error reporting is a feature of Windows XP and Windows 2003 server. If you are running Windows 2000, this is a function included in applications, for example Office.

A great benefit of this are that administrators can get a report about application problems within the organisation. This information can be foundation for software upgrade, software updates and purchase of new software. This information will help administrators to get a overview of software problems within the organisations, and that can help the organization to maintain the productivity instead of fighting with software filled with problems.



EAM Errors.

This is not post a complete step by step guide about configure AEM, if you are having problem with this, please contact me in a news group and I will help you. Here is a general overview how to setup AEM (step by step guide will be uploaded later…)

  1. Enable client monitoring mode on management server in the Administration part of the Console. This will start a wizard where you will input for example a directory to store the client monitoring mode data. You can also replace Microsoft and enter your own organization name, this will be in the dialog box when a application crash at a client. During this wizard a ADM file will be created, including all GPO settings that you need to control clients.
  2. In a GPO, import your ADM file created during step 1, then enable all policies from that ADM file. Some settings will be set to disable even if you set them to enable. You will have to “show GUI” within them to keep them enable, but you dont have to do that, it will work anyway.  

That should do it! Now your management server will recive errors and you can see reports about applications with errors. You can look at this in the console, under monitoring and Agentless Exception Monitoring. There are a number of defaul views

  • Application Error Events, all applications from all machines
  • Application View, state view that lists applications
  • Crash Listener View, management servers listening for failure/errors
  • Error Group View, applications errors by error group
  • System Crash View, computers that have an OS failure

Under Administration/Settings/Error Transmission you can setup everything about forwarding errors to Microsoft. Don´t forget to setup this.

If you want to test your AEM settings there are a couple of good ways, first a KB how to generate blue screens and then BANG.

This post was written in collaboration with Björn Axéll, thanks for good discussions and tips.

1 Comment

Comments are closed.