Improving SolarWinds SAM and Agent Monitor Usage , Problems getting "Location".

Hi everyone,

I hope you’re doing well.

I’d like to start a discussion about an issue we’ve observed with the SolarWinds SAM module when using Agent Monitor on servers with multiple domains. According to SolarWinds support, the "Location" value is retrieved from the last DNS query made.

However, in a recent case, we noticed the following results from PowerShell:

• NCOSOLB1 - "Location" value not obtained.
• NCOSOLB2
• NCOSOLB3
• NCOSOLB4 - "Location" value not obtained.

This suggests that the "Location" value retrieval is not working as expected in some situations.

Topics for discussion:

1. Is this a common issue when using the SAM module with agents in multi-domain environments?
2. What configurations or best practices can ensure that values like "Location" are retrieved correctly?
3. If the issue persists, how can we manually set the "Location" value to ensure it applies properly?

Any previous experience or suggestions would be very helpful to improve the use of the SAM module and ensure accurate monitoring data.

Thank you all for joining this discussion. Looking forward to your input!