question

StonerK-2919 avatar image
0 Votes"
StonerK-2919 asked JamesKing-0419 commented

SCOM 2019 - Agent Disappeared from Agent Managed

HI,

About a month ago, I have noticed that a windows server 2012 r2 Agent managed disappeared from Agent Managed list in Administration, however agent is still visible in Windows Computers (Monitoring) and Agent Health State (Monitoring). I have checked what discoveries are still associated with it and there are quite a number.

Agent was re installed however an error 20070 in event vwr is triggering.

I also read that database tweaks to remove stale objects are not supported.

Any ideas ?

msc-operations-manager
· 1
5 |1600 characters needed characters left characters exceeded

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

I am having the exact same problem. I have a server that shows up in the Windows Computer list. It has an active alert for a stopped service (that is now running.) It is completely missing from the Device Management section of the Administration pane. If I try to re-discover, it says no valid objects found. Re-installing the agent on the server has no effect in the console.

0 Votes 0 ·
AlexZhu-MSFT avatar image
0 Votes"
AlexZhu-MSFT answered AlexZhu-MSFT commented

Hi,

Roger Xue has shared a full solution for error 20070, we may try to see if it helps.
https://docs.microsoft.com/en-us/answers/questions/305205/scom-2019-agent-error-id-20070.html

Alex
If the response is helpful, please click "Accept Answer" and upvote it.

· 2
5 |1600 characters needed characters left characters exceeded

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

Hi,

All steps mentioned in that post have all been done to no avail :(

Thanks

0 Votes 0 ·

Hi,

Since we have gone through all the routine aspects, such as uninstalling the agent manually, telnetting port 5723, checking nslookup, traceing route, etc., we may check other aspects, such as GPO, virtualization platform, etc, as mentioned in the following article. Mostly, Event ID 20070 may relate to netowrk, have we made some changes in network level recently? Also, what is the environment, scom2019 or scom2012r2? The title and content do not match.

http://thoughtsonopsmgr.blogspot.com/2012/03/erratic-behavior-of-scom-eventids-20070.html
Note: this is not from MS, just for your reference.

Alex

0 Votes 0 ·
StonerK-2919 avatar image
0 Votes"
StonerK-2919 answered

Hi,

My problem is not because it just lost connectivity to SCOM, but the agent actually disappeared from the Agent Managed section and still listed under windows computers as grey agents. I have also cleared the cache on all MS however the issue persisted.

SCOM version is 2019
Windows server which has the agent installed on is Windows Server 2012 R2

Thanks
Stoner

5 |1600 characters needed characters left characters exceeded

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

AlexZhu-MSFT avatar image
0 Votes"
AlexZhu-MSFT answered StonerK-2919 commented

Hi Stoner,

Thank you very much for the clarification. In general, the server2012r2 agent has disappeared and now we have difficulties while re-installing it, either from the console or manually.

During the agent installation, the log file Setup(x).log was written in the following location. Could you help to share the latest log file?
C:\Users\<UserName>\Appdata\Local\SCOM\Logs.
<UserName> – This is the name of the account you used to run the SCOM installation.

In addition, even though we can telnet port 5723 (of Management Server) from the sever2012r2, it does not indicating the communication is smooth. For example, the network team changed the policy of the firewall (if there is a one between the agent and the Management Server) and some traffic were dropped. What is our environment? In the same subnet (without network device betwween) or in different subnets?

Alex
If the response is helpful, please click "Accept Answer" and upvote it.

· 1
5 |1600 characters needed characters left characters exceeded

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

Hi Alex,

Thanks for your reply,

The setup.log was latest updated when SCOM was last upgraded, and no info related to this agent is within.

Also confirmed that no networks ports are being blocked, whilst other agents within the same vlan are working fine.

My main issue is that the agent disappeared while still visible in Windows Computers view.

Thanks
Stoner

0 Votes 0 ·
CyrAz avatar image
1 Vote"
CyrAz answered CyrAz edited

Your issue is indeed weird, deleting an agent from "agent managed" should remove every other related object (sometime after a couple of days)... Something may have gone wrong at some point but I guess it's too late to have a look at your logs.

Removing orphaned objects is indeed unsupported if not done under Microsoft's support guidance, so you could call them.

Otherwise, if you finally decide to give it a try by yourself, this is the only recommended way : https://kevinholman.com/2018/05/03/deleting-and-purging-data-from-the-scom-database/

· 1
5 |1600 characters needed characters left characters exceeded

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

Indeed that's what I was reading, in-fact wanted to try all options possible prior opening a case.

Will open a case and update you accordingly.

0 Votes 0 ·