Home > Troubleshooting Agent Install > Typical Agent Install Issues

Typical Agent Install Issues



Push Problems:


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.

  1. September 19, 2011 at 10:10 pm

    This is SCOM 2007 R2 but it is the Authoring console – it can’t be done from the Authoring tab of the monitoring console.

  1. July 21, 2011 at 6:03 pm

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: