ServiceNow Discovery Location

[Ashish Kathait]

I have a discovery scheduled for a particular location Server abut not sure why it is showing wrong location. Some Serer showing previous correct location and then rest showing some other.  How to proceed for troubleshooting and can't check with Serve team as they came up to me that this is not correct Location. 

[MaxMixali · Accepted solution]

Hi, hop tha can help, if you like check this as solution

1. Discovery Schedule Location ConfigurationCheck your Discovery Schedule(s):

Navigate to: Discovery > Discovery Schedules

Open the schedule discovering these servers

Verify the Location field is set correctly

Check if multiple schedules are running for the same IP ranges with different locations

Key Point: The location field on the discovery schedules will update the locations on the CIs discovered during the run ServiceNow Community.

2. Multiple Discovery Schedules ConflictCommon Issue: You may have overlapping IP ranges across multiple Discovery Schedules with different location values.To verify:

1. Go to Discovery > Discovery Schedules

2. Check all active schedules

3. Look for IP range overlaps in Discovery > IP Range Items

4. Identify if different schedules have different locations setWhat happens: If Server A is discovered by Schedule 1 

(Location: DataCenter-A), then later discovered by Schedule 2 (Location: DataCenter-B), 

the location will change based on which schedule ran last.

3. Reconciliation Rules & Data Source PrecedenceReconciliation rules determine which data sources can update CI attributes. Data sources with highest priority determine what an attribute value will be ServiceNow Community.Check Reconciliation Rules:

Navigate to: Configuration > CI Class Manager

1. Search for "Server" (or cmdb_ci_server)

2. Open the CI Class

3. Click on "Reconciliation Rules" tab

4. Look for rules affecting the "Location" field

5. Check data source prioritiesPotential Issue: If you have multiple data sources (Discovery, Manual Entry, SCCM, etc.), 

reconciliation rules might be allowing lower-priority sources to overwrite location data.

4. Assigned User Location OverrideCritical Discovery Behavior: If the CI has an Assignee (assigned_to field), discovery can source the location from the user's Location field post-update ServiceNow.To check:

1. Open the affected server CIs

2. Check if they have an "Assigned to" user

3. If yes, check that user's location field (User record)

4. This user location might be overriding the Discovery Schedule locationSolution: Either:

Remove the assigned user from CIs where location should come from Discovery

Ensure assigned users have correct location set

Modify the discovery sensor to not use user location

5. IRE (Identification & Reconciliation Engine) TimingThe IRE processes discovery payloads and applies identification and reconciliation rules. Sometimes timing issues cause inconsistent updates.