Agentless Monitoring Part 2

Standard

In Part 1 of agentless monitoring I explained how to configure Agentless Monitoring. In this Part I will explain Agentless Exception Monitoring(AEM).

Agentless Exception Monitoring is an extension of Dr. Watson. Dr Watson is responsible for capturing application errors and the forward the to Microsoft if needed. When you are a home user this could be a viable option. When you are working in a organisation , the data that is collected by Dr Watson is could contain insight information of the organization that you don’t want to share with Microsoft.

When you implement Agentless exception Monitoring, Dr Watson collects the application errors and stores them in on the AEM infrastructure that is hosted by your organization.

AEM Relies on two configuration options to Function:

  1. Run the configuration Wizard from the System Center Operations Console
  2. Create a Group Policy to configure the Clients

Run the configuration Wizard from the System Center operations Console

  1. Start the System Center Operations Manager Console 2007 r2
  2. Select the "Administration" workspace
  3. Expand "Device Managed" and select "Management Servers"
  4. Right click the RMS and select"Configure Client Monitoring"

    ConfigureClientMonitoring

  5. On the "Introduction" page, click "Next"
  6. On the "CEIP Forwarding" page, click "Yes, use the selected management server to collect and forward CEIP data to Microsoft", Clear the "Use Secure Socket Layer (SSL) protocol" and click "Next"

    CustomerExperienceImprovementProgram

  7. On the "Error Collection" page, Fill in the "File Share Path", Check of the "Collect error from Windows Vista-based or later clients" is checked and clear the "Use Secure Sockets (SSL) protocol" check box. In the Organization Name type the name you want to Use

    ErrorCollection

  8. On the "Error Forwarding" page, Click "Next"
  9. On the "Create File Share" page, Click "Other user account(will not be saved)" and fill in a domain administrator account
  10. On the "Create File Share: Task Status" page, click "Next"
  11. On the "Client Configuration Settings" page, Select a location where you want to store the administrative template and click "Finish"

Create a Group Policy to Configure the clients

  1. Start the Group Policy Management Console
  2. Browse to the Organizational Unit where you want to create the Group Policy
  3. Right click the Organizational Unit and click "Create a GPO in this domain, and link it here…"
  4. Give the New GPO a name and click "OK"
  5. Edit the GPO
  6. Navigate to "Computer Configuration, Policies, Administrative Templates"
  7. Right click "Administrative Templates" and click "Add/Remove Templates"
  8. On the "Add/Remove Templates" dialogue click "Add" and select the created template from above click "Open". Click "Close"
  9. Navigate to "Computer Configuration, Policies, Administrative templates, Classic Administrative Templates(ADM), Microsoft Application, System Center Operations Manager (Scom)"
  10. Select "Scom Client Monitoring CIEP Settings", Open "Configure CEIP (Customer Experience Improvement Program)" click "Enable" and configure the CEIP Settings "http://rms.ms-opsmgr.eu:51907/" Click "Apply", click "OK"
  11. Select "Scom Monitoring", Open "Configure Error Reporting for Windows Vista and later operating Systems" , click "enable" and verify that the correct settings are configured and click "Apply" and click "OK"
  12. Select "Scom Monitoring", Open "Configure Error Notification", click "Enable" and verify that "ShowUI" in unchecked and "DoNotDebugErrors" is checked. CLick "Apply" and "OK"
  13. Navigate to "Computer Configuration, Policies, Administrative templates, Classic Administrative Templates(ADM), Microsoft Application, System Center Operations Manager (Scom), Scom Monitoring"
  14. Select "Advanced Error Reporting settings", open "Application reporting settings (all or None)", "Enable" check if all options are selected and Click "Apply" and "OK"
  15. Select "Advanced Error Reporting settings", open "Report Operating System Errors", "Enable" check if all options are selected and Click "Apply" and "OK"
  16. Select "Advanced Error Reporting settings", open "Report unplanned shut-down events, "Enable" check if all options are selected and Click "Apply" and "OK"
  17. Navigate to "Computer Configuration, Policies, Administrative templates, Classic Administrative Templates(ADM), Microsoft Application, System Center Operations Manager (Scom)"
  18. Select "SCOM Client monitoring for Office 10.0 Applications" open "Configure Error Notification, "Enable and make sure that the Option "ShowUI" is not selected. Click "Apply and "OK"
  19. Close the Group Policy Management Console

Now the configuration is done. Time to do some testing and see if it’s working. You can add a registry key to a client computer to add the feature to generate a crash.

  1. Start the registry editor on your windows test system
  2. browse to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters"
  3. Create a new DWORD Value. Name the new key "CrashOnCtrlScroll", and set value 1
  4. Restart the computer

When you computer is up and running again, you should be enable to generate a blue screen by holding down the right Ctrl key and click Scroll Lock twice.

When you open the System Center Operations Manager Console and you select Agent less acceptation Monitoring. You could select a view to see the alerts generated

MonitoringAgentless

Big thank’s to Pete Zerger and Anders Bengtsson who wrote a great article on Agent less Exception Monitoring. This can be found at System Center Central

Leave a Reply

Your email address will not be published. Required fields are marked *