ADM Enhanced for Discovery

Quan Nguyen
Tera Contributor

‎01-20-2023 11:03 AM

I am having an issue with ADM Enhanced probe for discovery working for windows servers on San Diego.

 

When I run a discovery against  my server 10.141.245.200.
I notice the input for ADM Enhanced probe, theres no TCP connection info for this connection below. This is when I run a netstat I can see the connection is established.


TCP 10.141.245.200:445 10.141.18.205:49774 ESTABLISHED 4

 

If I disable ADM Enhanced, the TCP connection is visible in the Windows ADM probe but never populates the TCP Connection table.

I do notice on 10.141.18.205, there is a TCP connection record back to 10.141.245.200.

 

There has to be logic or bug on why its not returning in the ADM enhanced probe and Windows ADM probe not getting populated in TCP connections table when input has the connection record.

 

Any insight or troubleshooting tips would be helpful.

0 Helpfuls
  • 1,362 Views
2 REPLIES 2

Quan Nguyen
Tera Contributor

‎01-20-2023 11:06 AM

I also see there are two properties that aren't documented well.

mid.adme.max_result_size

max.adme_result_payload_size

Anyone know default values and steps to implement them?  

 

0 Helpfuls

doug_schulze
ServiceNow Employee
ServiceNow Employee

‎01-23-2023 11:14 AM

The ADME probe run in two parts. on initial discovery it leaves a script behind to collect the data then on another discovery it picks it up... try running the discovery a few more times to see if it returns.

0 Helpfuls