EventID 7024

Symptom
The SCOM Agent won't run on a monitored system. When one tries to start the OpsMgr HealthService this event is logged:

Log Name: System
Source: Service Control Manager
Date: xx/xx/xxxx xx:xx:xx
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxx.xxx
Description: The OpsMgr Health Service service terminated with service-specific error 2147500037 (0x80004005).

Cause
Most of the times, one or more registrykeys are missing:

1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\State Directory
   This entry points to where the Agent is installed and where the State Directory is to be found. This directory is the repository for the SCOM Agent. When this entry is missing, import it from a system where a working Agent is installed.
   
   
2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Group\<Management Group >\Windows AccountLockDownSD
   This entry is needed by the Agent service to run. When it is not there import it from a a system where a working Agent is installed.
   

The Agent should work now.

26-08-2009 Update: PFE Jimmy Harper also ran into this issue and solved it in a different manner. He also blogged about it, found here.