Agents authentication issue

Discussion:

(too old to reply)

Sirio

2010-04-19 07:31:01 UTC

Hi all,

agents (AD integration) in domain A could not be authenticated on SCOM MS in
domain B throught firewall but with a forest trust. It's possible the agent
can connect without directly connection to the Config Service (RMS) and
without SCOM GW.

Look up this communication plan.

Loading Image...

.html

Error on SCOM MS

Log Name: Operations Manager

Source: OpsMgr Connector

Date: 15.04.2010 10:06:16

Event ID: 20002

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: Server

Description:

A device at IP 195.x.x.:1859 attempted to connect but could not be
authenticated, and was rejected.

Error on Agent

Log Name: Operations Manager

Source: OpsMgr Connector

Date: 15.04.2010 14:37:12

Event ID: 20070

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: Server

Description:

The OpsMgr Connector connected to Server, 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.

Thanks

Vik

2010-05-10 05:50:15 UTC

Permalink

Yes, you need to use certificates in that case. Those errors are normal -
because the agent can find the Management Group and the Server however
cannot authenticate.

Use the following link to setup certificates.
http://technet.microsoft.com/en-us/library/bb735408.aspx

BTW - how many clients do we have in Domain A?
--
Regards,
Vikramjit Singh (VIk)

Post by Sirio
Hi all,
agents (AD integration) in domain A could not be authenticated on SCOM MS in
domain B throught firewall but with a forest trust. It's possible the agent
can connect without directly connection to the Config Service (RMS) and
without SCOM GW.
Look up this communication plan.
http://www.pic-upload.de/view-5316216/15.04.png.html
Error on SCOM MS
Log Name: Operations Manager
Source: OpsMgr Connector
Date: 15.04.2010 10:06:16
Event ID: 20002
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server
A device at IP 195.x.x.:1859 attempted to connect but could not be
authenticated, and was rejected.
Error on Agent
Log Name: Operations Manager
Source: OpsMgr Connector
Date: 15.04.2010 14:37:12
Event ID: 20070
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server
The OpsMgr Connector connected to Server, 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.
Thanks

Murad Akram

2010-05-24 14:26:01 UTC

Permalink

Serio,
Looks like your agent in communicating with your RMS or MS server, but it's
getting rejected because your Management Group doesn't know anything about
this agent. Did you go thorugh the "Administration node" and actually
accepted this agent into your Management Group? If not, please do so by going
to SCOM console, Administration node, and under "Pending Management" check to
see if you have this device/agent showed up under "Manual Agent Install"
section. If it's there right click and select approve.
--
Murad Akram