---
title: "Microsoft DHCP - Service Locations"
canonical: "https://docs.infoblox.com/space/UniversalAssetInsights/1710195971/Microsoft%20DHCP%20-%20Service%20Locations"
format: markdown
---
- In the **Service Location** step of the **Configure Discovery** wizard, configure the following:
  - Click **Add** and configure the following:
    - **Universal Agent**: Choose the Universal Agent from the drop-down.
    - Click **Add** and configure the following:  
The **DHCP Server** field is used to define the IP address of the DHCP server you want to connect to, while **Resolved IP** refers to the final resolved address of that DHCP server. Although the fields allow direct IP input, it is strongly recommended to specify the **FQDN (Fully Qualified Domain Name)** of the DHCP server instead of using a raw IP address. Using the FQDN enables proper domain-based authentication and service resolution, which in turn allows the system to use **Kerberos authentication** rather than falling back to **NTLM**. Kerberos is more secure, supports mutual authentication, and is the preferred method in Active Directory environments, whereas NTLM is older, less secure, and often used only when the system cannot identify the target through domain-based name resolution.
      - **DHCP Server**: Specify the IP address of FQDN of the DHCP server. It is recommended to specify the FQDN for this field. You can add multiple DHCP servers.
      - **Resolved IP**: Specify the resolved IP of the DHCP server you want to manage.
    - **Credentials**: Choose the credentials from the drop-down. For more information on creating new credentials, see *[Creating Active Directory Credentials](https://infoblox-docs.atlassian.net/wiki/spaces/UniversalAssetInsights/pages/1693876284)**. *Assign the credentials to the `DHCPadmins` group in the Active Directory Server.
  - Click **Save**.
- Click **Next**.