Thursday, May 26, 2016

Manually install OOMADS on domain controllers

There are already threads in the forum regarding that but they are kind of missleading. So I decided to write a blog post on that – after long time.

There are additional steps required if you install the SCOM agent on domain controllers manually. In case that you miss that you will see alerts in SCOM like that:

Script Based Test Failed to Complete

AD General Response : The script 'AD General Response' failed to create object 'McActiveDir.ActiveDirectory'. This is an unexpected error.

The error returned was 'ActiveX component can't create object' (0x1AD)

The Active Directory Management Pack Objects (OOMADs) components are not installed on the Domain Controller. These components are required for the monitoring scripts to run successfully. See Alert Knowledge for additional details.

These steps are:

  1. Copy oomads.msi from MS: "D:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\AgentManagement\amd64\OOMADs.msi"
  2. Paste it on DC: "C:\Program Files\Microsoft Monitoring Agent\Agent\HelperObjects"
  3. Uninstall any existing “Active Directory Management Pack Helper Object” from Programs and Features
  4. Open an elevated CMD
  5. Run: "C:\Program Files\Microsoft Monitoring Agent\Agent\HelperObjects\OOMADs.msi"
  6. Once finished, check if file exists: "C:\Program Files\Common Files\Active Directory Management Pack Objects\oomads.dll"
  7. Stop agent
  8. Delete folder: "C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State"
  9. Start agent
  10. Check if events/alerts occur again


Read Full Post...