How do I fix SolarWinds Agent polling that does not return a Location

john.davis.asrs

Due to security concerns we are switching out polling for SolarWinds from WMI to Agent based on some of our Windows Servers.  They are a mix of Windows Server 2008 R2 (soon to be retired) and Windows Server 2012 R2 and Windows Server 2016.

From the Windows Server 2016 server and one of the Windows Server 2012 R2 servers the LOCATION is populating as expected.

From the Node Details view this is what I see

From the Windows Server 2008 R2 and one of the Windows Server 2012 R2 servers the LOCATION is blank.

From the Node Details view this is what I see

How is the LOCATION is determined and updated?  How can I get the Agent to populate this information correctly?

mesverrum

For Windows nodes the using WMI it usually populates the location with it's AD Site, for example one of my labs has all the servers showing with 'Default-Fi​rst-Site-N​ame' because we didn't specify anything more useful when we stood up the environment.

Presumably all these nodes are actually joined to the domain and associated with a site in AD, right?

Not sure off hand how the agent deals with the location, any chance that the nodes where you have a value were already in orion and got changed over while the ones with it missing were never added with WMI?

Another place that MAYBE could be a source for the data would be if someone had gone through and actually set up the windows SNMP service with a location.  Not sure if the agent has a preference for the SNMP value or the WMI.