Archive

Archive for the ‘Troubleshooting Agent Install’ Category

On install, the OpsMgr Health Service service terminated with service-specific error 2147500037 (0x80004005)

July 20, 2009 Leave a comment

I have found this useful on a number of occasions – thanks Marnix:
http://thoughtsonopsmgr.blogspot.com/2009/02/eventid-7024.html

Typical Agent Install Issues

July 9, 2009 2 comments

Discovery:
http://blogs.technet.com/momteam/archive/2007/12/10/how-does-computer-discovery-work-in-opsmgr-2007.aspx

http://blogs.technet.com/kevinholman/archive/2007/12/12/agent-discovery-and-push-troubleshooting-in-opsmgr-2007.aspx

Push Problems:
http://blogs.technet.com/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx

Repair:
http://blogs.technet.com/momteam/archive/2009/04/25/to-repair-or-not-to-repair-that-is-the-question.aspx

It has also been reported that another cause of install failures is when the name of the computer (to be managed) found in Active Directory is different than its DNS name (composed of its machine name and DNS suffix).

“For example, machine.name.domain.com was the name found in the AD, and machine.name.hu.domain.com was the DNS name.

The RMS found and approved the agent, but they were unable to contact; because the RMS thought it is managing the machine called machine.name.domain.com. However, that name was impossible to resolve with DNS; further, the agent sent its request with the name machine.name.hu.domain.com, which was unknown for the RMS.

Finally, I had to implement certificated-based authentication and reinstall the agent. The certificate was issued with the DNS as the subject name, as I remember.” – can’t remember who posted this but if you do read it then please let me know and I’ll make the appropriate credit.