Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.įor more information, see Help and Support Center at. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. The OpsMgr Connector connected to, but the connection was closed immediately after authentication occurred. On all the client machines (both domain and non-domain), I get EventIDs 20070, 2103 as follows: It appears that the agent installs properly but can't communicate. Requesting Device Name: " These computers are domain machines and ports 5723, 445, 135 have all been verified to be open. I get a recurring EventID 20000 - "A device which is not part of this management group has attempted to access this Health Service.
I thought maybe it was a problem with the certificate, so I went ahead and tried to deploy to additional domain machines. It is sitting there saying "Not Monitored". The DMZ machine agent appeared under "Pending", I approved it and it went to "Agent Managed", but it never said "Healthy". I configured SCOM to require manual approval for manually installed agents. I decided to try to monitor a DMZ machine, so I set up a CA on an W2K3 Enterprise R2 圆4 machine on the domain and created the OpsMgr template per the security guide.Įverything seemed to go smoothly with the certificate and agent deployment. At first, everything went pretty smoothly - I added about 9 machines (mixed workstations and servers) and have been monitoring them ever since. I am currently running an evaluation of OpsMgr R2.
0 kommentar(er)
