question

VclavJandek-9281 avatar image
0 Votes"
VclavJandek-9281 asked AmitS-0540 commented

SCOM 2019 - Agent Error ID 20070

Hello,

I have an issue with my agent. I installed it through console and first thing which I noticed was that I can't see version of agent.

So I went to Event Viewer on Agent and I found error 20070:
The OpsMgr Connector connected to MS, but the connection was closed immediately after authentication occurred. 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. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.

First of all, device is on same domain and they are in trusted relationship.

I have tried to manually installed agent but same results.

On MS I found a lot of 20000IDs. It seems that old agents are still trying connect to Mangement Server. I choose to reject new manually installed agents but they keep trying to connect and it's creating lot of warnings and reqeusts.

Thank you for any tip,
Vaclav




msc-operations-manager
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

2 Answers

VclavJandek-9281 avatar image
0 Votes"
VclavJandek-9281 answered

Resolved by re-creating new VM for SCOM.

5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RogerXue-3369 avatar image
0 Votes"
RogerXue-3369 answered AmitS-0540 commented

Step 1 try the following
i) uninstall SCOM agent
ii) remove all SCOM folder in agent machine
iii) reinstall SCOM agent again
If not work
Step 2)

i) Make sure you are able to ping the SCOM management server and DNS Resolution also works from the monitored Server.
ii) Make also sure port 5723 is open from your monitored Server to the SCOM Management Server. You could use the command:
telnet managementserver.domain.com 5723
iii) Make sure the SCOM Management Group Name in the Agent control Panel is written exactly as you defined it when you installed the Management Group, this Name IS case sensitive! The MG name you can find on top left of your SCOM console.


Roger

· 1
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AmitS-0540 avatar image AmitS-0540 ·

Hi Roger,

Would you be able to provide any MS documentation about the Management group name being Case-sensitive?
I have tested this and did not found an issue with case-sensitivity. I doubt it maybe the case with SCOM 2007R2 but have not seen this in SCOM 2012R2 or SCOM 2019

Thanks,
Amit

0 Votes 0 ·