Setting "Location" of a CI via the Location in Discovery Schedule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2010 02:57 PM
I am trying to make use of the "Location" field in a Discovery Schedule to set the "Location" of any discovered CI. It seems to work for some but not others.
Is there documentation somewhere on this feature? I haven't tripped over any yet.
cheers,
robin850
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2010 06:01 PM
Not much there other then the obvious.... If you utilize the location values in the core product you can put the value of your choice in that schedule field and whatever ci you discover in that schedule its location value will be the same...
Pretty handy when you have an IP Range that is known to be in a specific location such as a datacenter or office building...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2010 07:52 PM
Ah, i think i figured it out. I have some checking to do, but I think the CIs that have only been scanned by wmi_discovery.js are the ones that have not yet had their Location fields updated.
thanks for listening.
cheers,
robin850
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2010 08:14 PM
Yep you're right the WMI script does not populate the location value as the agentless discovery does...
But thinking about it, why not have a parameter in the wmi script that you or I could update to fill that value in the xml return...
But how would we know where that computer actually is? VPN user in New york or a desktop in Sheboygan?
Thoughts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2010 05:34 AM
I considered tweaking the script, but I don't want to have to maintain my changes to it if things change with new releases.
As far as knowing where a computer is, that is a bigger question. If they are on part of a corporate network then I can tell by IP network ranges. If they are using a VPN connection all I would know is that they are using a VPN. Physically locating the computer would require some sort of "ip geolocation finder". This of course would only be as accurate as finding the current ISP, but it would get you close (usually within 50-100 miles. it varies widely)
I ran across this link and I am wondering if there is perhaps a way to use it either from within the wmi script or get creative and have something locally installed on the computer that would update a text file or something.
http://www.hostip.info/use.html
the code snippet to get the data looks something like this http://api.hostip.info/get_html.php?position=true
If any of you code gurus think of something, please share.
cheers,
robin850