I know you can use a Custom Property to answer most issues with this, but not all...
Ref: Case: 590367 - Location, location, location
The issue we have is that nearly 1/2 of our environment do not return a Location and many of our client's monitored devices are inconsistent in their Location naming.
Windows servers only return a Location value if they are Domain Controllers (see here) and any devices managed by ICMP are always unknown; even if you know exactly where they are.
I am sure I'm not alone on this issue. If only we had some control over it...
So why not use the Location (if present) to populate a new field, a Custom Property, which will only be populated when a device is discovered (or re-discovered) and allow that field to user editable from the node editor or via SQL?
This new CP Location could then be used as the default location field throughout Orion (et al) and would allow you to have consistent location names and therefore making them much more useful, as well as cleaning up the Orion GUI for users.
Just a thought.
