Discovery Location Update Issue – Need Assistance

[Cristian London]

Hi everyone,

I'm currently facing an issue with the Discovery tool. Here's what's happening:
We had a user travel to another country, and Discovery scanned while they were abroad. As a result, the location of their US assets was updated to a site in Germany. This shouldn't happen because it causes problems with PC updates.

In our company, Discovery runs based on schedules, and each schedule already has a predefined location assigned. That's how locations are normally set. Given the issue I described, I'd like Discovery to stop updating the location if the field is already populated.

I've been trying to set up a reconciliation rule to prevent it, but it’s not working. 

Does anyone have any advice on how I could properly configure this?

Are there specific parameters I should be using?

Or, alternatively, is there a better approach to prevent this from happening in the future?

Looking forward to hearing your suggestions, and thanks in advance!

P.S.: Has this happened to anyone else?

[Gomathi Kannan · Accepted solution]

Hi Cristian, 

I believe, you can configure BR on discovery_device_history table to prevent the update of location from SN Discovery.

See below link for your reference

https://www.servicenow.com/community/itom-forum/change-field-that-discovery-updates-for-location/m-p...