Discovery is updating computer locations as people are travelling.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2025 11:00 AM
Discovery is updating computer locations as people are travelling.
Discovery is updating computers locations as part of the scans. (Note: Scans occur every 5.5 days.)
We need to ensure that once a location is set -- by either Discovery or another way -- that Discovery does not update the location.
We had a user travel to another country, and Discovery happened to scan while they were there. The user based in the US had their asset location update to a site Germany. This cannot happen as it creates errors with PC refreshes.
Discovery is updating computers locations as part of the scans. (Note: Scans occur every 5.5 days.)
We need to ensure that once a location is set -- by either Discovery or another way -- that Discovery does not update the location.
We had a user travel to another country, and Discovery happened to scan while they were there. The user based in the US had their asset location update to a site Germany. This cannot happen as it creates errors with PC refreshes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2025 06:59 PM
Not sure if this is helpful, but we don't allow discovery to update our locations. A number of our locations are very large sites, and we don't have all the rooms mapped into the location table (There would easily be over a thousand rooms). As a result, it's hard to determine the location mapped from IP range as the IPs weren't set up that way. We already have the data manually populated, so we got discovery not to map the location from IP (I think this was set in the reconciliation rules(?) for that class).
My question to challenge you would be (And ultimately, I don't know your company), but could you rethink a way to do refreshes? There are many reasons why having the current location of a PC would be very useful - If someone went to Germany for a week or 2, and assuming you refresh every 3 years, could you tweak the refresh policy to check a country of origin etc. so it wouldn't trigger a refresh if the user belong in that country? Obviously, if someone permanently relocated to Germany you would want the location of the device to get updated?
Good luck with your issue!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-06-2025 07:09 PM
Hey, thank you for your answer. And in response to yours, yes we could think of another way to update the location. In this case, do you know if you have any documentation in servicenow to stop the update through discovery?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-01-2025 10:43 PM
No sorry - I don't as I'm not involved in the implementation 🙂