Wednesday, October 20, 2010

EventID 10: Active Directory Helper Objects Installation unsuccessful. MSI was not found at the specified location

Got this EventID in the OpsMgr event log on all DCs reporting to a SCOM R2 Gateway Server.

As it turned out, the AD Helper Object (OOMADs.msi) was missing on the DCs. The SCOM R2 Gateway Server did not have this file in place so it never arrived on the DCs to be monitored by SCOM.

This resulted in many Warnings in the SCOM R2 Console. So it was time to solve the issue at hand and in such a manner that it would not return ever again. This is what I did:

  1. Corrected the SCOM R2 Gateway Server
    Copied the file OOMADs.msi from the installation media of SCOM R2 (~\HelperObjects\<ARCHITECTURE>) to the installation folder of the SCOM R2 Gateway Server (~:\Program Files\System Center Operations Manager 2007\HelperObjects).

  2. Corrected the Agent Staging Folder
    Copied the file OOMADs.msi from the installation media of SCOM R2 (~\HelperObjects\<ARCHITECTURE>) to the Agent Staging folder of the SCOM R2 Gateway Server (~:\Program Files\System Center Operations Manager 2007\AgentManagement\<ARCHITECTURE>).

  3. Copied the AD Helper Object to the Agent
    Copied the file OOMADs.msi from the installation media of SCOM R2 (~\HelperObjects\<ARCHITECTURE>) to the installation folder of the SCOM R2 Agent (~:\Program Files\System Center Operations Manager 2007\HelperObjects).

  4. Corrected the Agent
    Stopped the HealthService, removed the cache file (~:\Program Files\System Center Operations Manager 2007\Health Service State), installed the AD Helper Object manually and restarted the HealthService. Checked the OpsMgr event log for EventID 10. It did not return. Closed the Alerts (based on a Rule) in the SCOM Console per fixed DC and the Alerts did not come back.

Now all is well and the DCs are monitored in a proper manner. No more Alerts in the SCOM R2 Console.

No comments: