> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/platform/user-guide/locations/on-premises-client-detection.md).

# On-Premises Client Detection in SaaS

Advanced setup for on-prem client detection in SaaS

{% hint style="warning" %}
This is an advanced setup guide. If you would like assistance setting up On-Premises Client Detection, please contact our [Support Team](https://adaptiva.com/support).
{% endhint %}

By default, a SaaS installation of OneSite Platform only creates [Internet Locations](/platform/user-guide/locations/internet-locations.md) based on the public IP addresses of any connected device.

The **On-Premises Client Detection** setting enables the SaaS tenant to communicate with specified devices inside your network so that the server can identify if a device is in that network.

This enables you to create locations in the same way as if your OneSite server was on-premises.

## SaaS default location behavior

When a client with a new unique public IP address connects to a SaaS server, the server creates a hidden Internet Location. This internet Location is configured as **Wifi** and includes all devices with a matching public IP.

This behavior is usually acceptable for smaller or mid-sized companies with:

* Simple networks with a single public IP address per network.
* Networks where all devices can communicate and share content with each other.

All devices inside your network will be considered to be part of the same location, and will use the Foreground Adaptive Transport protocol to share content. Any device connecting from outside your physical network, such as a remote client, will have its own Internet Location and will only obtain content directly from the SaaS server.

This behavior may not be suitable for larger companies with any of the following:

* Complex networks.
* Thousands of devices.
* Devices in the same physical location that cannot share content, such as servers and workstations isolated from each other.

In these situations, the default behavior can lead to inefficient content sharing and undue stress on the network. Enable and configure **On-Premises Client Detection** so that you can manually create Locations that are optimized for your network environment.

Review [Location best practices](/platform/user-guide/locations/location-best-practices.md) before creating Locations.

## Set up On-Premises Client Detection

1. Select **Assets** > **Locations** from the side bar navigation.
2. Select **On-Premises Client Detection** from the **More** dropdown.

   ![](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-855be9d7e1eed09b6c88ef23650a109ed0bb04de%2Fon%20prem%20client%20detection.png?alt=media)
3. Configure at least one of the following Client Detection Settings:

   **ICMP Target**

   The client is considered on premises if the server receives an ICMP response.

   1. Select either Hostname or IP address.
   2. Enter the information for a device on the company network that the Adaptiva Client can ping using ICMP.

      ![](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-afc3049e02952ae3c986f82473e4e9594581bb68%2FICMP%20Target.png?alt=media)

   **DNS Targets**

   The client is considered on premises if any of the given DNS names resolve to the given IP addresses.

   1. Enter a DNS Target and click **Save DNS Target**.

      ![](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-b58a8219389a243816fb1387584d2eabd4c211cb%2Fdns%20targets.png?alt=media)

   **Public IP Ranges**

   The client is considered on premises if its public IP address is in any of the specified ranges.

   1. Select **+Create IP Range** to enter the Public IP ranges and click **Create IP Range**.

      ![](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-34fcacde766438f9226fd9b653c759c26aa51145%2Fcreate%20ip%20range.png?alt=media)
4. Click **Save**.

## Add IP range(s) to the Central Office Location

After completing the preceding steps, you must add an IP range to the Central Office Location, or a desired Location. This range should be a central location on the corporate network that every device can reach when they are considered to be on premises.

1. Select **Edit** from the more options dropdown next to the Location in the Locations tab.

   ![](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-ea678def3a4119da65ea95c6b574592a70edc749%2Fcentral-office-edit-button.png?alt=media)
2. Click **+Create IP Range**.
3. Add in the IP Range(s) of the Internet clients created in the On-Premises Client Detection steps above.

   ![](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-34fcacde766438f9226fd9b653c759c26aa51145%2Fcreate%20ip%20range.png?alt=media)
4. Click **Create IP Range**.
5. Click **Save**.

## Related Pages

* [Auto Location Creation](/platform/user-guide/locations/auto-location-creation.md)
* [Internet Locations](/platform/user-guide/locations/internet-locations.md)
* [Network Topology](/platform/user-guide/platform-management/network-topology.md)