---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Device location determination

# Device location determination {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Identify and determine the number of impacted devices based on the location by defining a custom logic.

Identify the number of impacted devices by location by configuring custom logic for location determination. Device location can be set using three predefined configurations. DEX administrators configure this behavior using the sn_dex.location_determination system property. This property controls how DEX determines the location of each device in the \[cmdb_ci_computer\] table, which is used for reporting and alerting.

## default_gateway_determined_location {#location-determination__section_evz_fkf_cgc}

Location determination logic: DEX uses the default gateway of the device to determine the location.

* Identify the default gateway IP address of the device.
* Match this gateway to the switches in cmdb_ci_ip_switch.

{#location-determination__ul_krk_ghg_1gc}

The assigned location of the switch is identified as the device's location. If not, the device is marked as Remote (see Remote location format logic).  
Note:  
When `sn_dex.location_determination` is set to `default_gateway_determined_location` to make the Geomap work on the DEX dashboard:

* Verify that the State and Country fields in the location (`cmn_location`) records associated with the `cmdb_ci_ip_switch` table use standard codes that match the values in the `sys_report_map_source_mapping` table.
* Verify that the latitude and longitude values are populated correctly in the associated location records.
{#location-determination__ul_gdy_3qy_fjc}

## device_user_assigned_location {#location-determination__section_amb_kkf_cgc}

Location determination logic: DEX prefers the device's assigned location and falls back to the employee's location if needed.

* Use the device's location from cmdb_ci_computer.
* If unavailable, use the owner's location from sys_user.

{#location-determination__ul_jvx_xhg_1gc}

If neither of the option is set, the device is marked as Remote (see Remote location format logic).  
Note:  
When `sn_dex.location_determination` is set to `device_user_assigned_location` to make the Geomap work on the DEX dashboard:

* Verify that the state and country fields in the location records associated with the `cmdb_ci_computer` and `sys_user` tables use standard codes that match the values in the `sys_report_map_source_mapping` table.
* Verify that the latitude and longitude values are populated correctly in the associated location records.
{#location-determination__ul_lxk_2qy_fjc}

## geoIP_determined_location {#location-determination__section_gyw_nkf_cgc}

`geoIP_determined_location` is the default option.

Location determination logic: DEX uses GeoIP based on network connectivity to determine the location using the GeoIP data.

When a device is marked as Remote, DEX uses GeoIP to determine the Region or State and Country. With an admin role, you can set the format (Remote, State, Country, or Remote, Country) in `sys_property`
`sn_dex.remote_location_config`.

* The `country` format: Remote, Country (For example, Remote, USA), where the country is determined by GeoIP.
* The `include_state` format: Remote, CA, USA, where state and country are determined by GeoIP.

{#location-determination__ul_mcs_sxh_ggc}  
Note:  
When `sn_dex.location_determination` is set to `geoIP_determined_location`, to make the Geomap work on the DEX dashboard, no manual configuration is required. DEX automatically populates the state, country, latitude, and longitude values.