| « New KB: 975057 - Error 623 and One or more management servers and their managed devices are dimmed in the Operations Manager Console of Operations Manager 2007 | Thailand » |
SCOM agent not starting after installation
SCOMToday I was upgrading a number of SCOM agents from SP1 to R2 version (using split monitoring at first).
After the installation the agents refused to start.
After a manual try on the machines to start the service I got the following error:
Windows could not start the System Center Management on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -2147467259.
Alright, so I check the System event log. Nothing to see. So I check the OpsMgr event log and I see it starting and saying it knows of two management groups and will start to try to contact them etc etc and suddenly followed by informationals that it is shutting down again.
Alright, so I found http://blogs.technet.com/smsandmom/archive/2008/04/30/opsmgr-2007-healthservice-service-fails-to-start-with-25362-warning.aspx and checked for the WindowsAccountLockDownSD key in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups\mymanagementgroup .
Sure enough it was not there for one of the two management groups.
So I picked up the value from another machine and tried to merge it with this one.
After merging it the service would not start. Great. 
Solution:
So I removed the SCOM agent completely and discovered the machine again and installed the agent. Checked for the existance of that registry key and it was not there. So I merged the value again for the WindowsAccountLockDownSD and sure enough the service could start right away.
Comment feed for this post
I have tried this but how long do you wait between these processes?
"... I removed the SCOM agent completely "
"...and discovered the machine again "
"...and installed the agent."
It seems some articles are asking for 3 days delay before a machine is completely removed from SCOM!!!
Thanks,
Dom
No wait time is needed in this case.
If the agent itself is installed and you are just missing the registry key you can just place it in there and restart the Healthservice. It should not crash on you (unless something else is wrong as well). It should start reporting itself to the management server. The first time you will see a red event as the MS is denying it at first, but a few minutes later it should start talking to the MS again.
In case you are in a normal process of removing an agent from scom, the x days wait time has to do with the grooming of old agent data out of the databases etc. That is why it can happen that you see the agent twice in the monitoring pane (one will be not monitored). But normally you remove an agent the right way (or delete it from the agent management pane) and wait for an hour. You should see it disappear from the monitoring pane (windows computer state for instance). If it will not go away and appears to be a grey agent there are ways to set the agent to deleted in the database and it will be groomed quite quickly.
If it is the same machine and the same agent and same management group you can just run the discovery and install the agent without waiting.
SO it all depends on your situation.
Let me know if I can help you with anything.