Overview
While DHCP is often deployed on domain-joined Windows Servers managed through Active Directory, there are many scenarios where a standalone DHCP server – one that is not joined to a domain – is the right choice. Small businesses, isolated lab environments, branch sites without a domain controller, and test networks all benefit from a lightweight DHCP deployment that does not depend on Active Directory infrastructure.
This guide covers the complete process of installing and configuring the DHCP Server role on a standalone Windows Server: verifying the server’s static IP configuration, installing the role through Server Manager, skipping Active Directory authorization in the post-installation wizard, creating a scope with the New Scope Wizard, configuring scope options (gateway, DNS), activating the scope, and verifying operation from a Windows client using ipconfig and the DHCP console’s Address Leases view.
Step 1 – Verify the Server’s Static IP Configuration
Before installing the DHCP role, confirm that the server has a static IP address assigned. Open a command prompt and run ipconfig to display the current network configuration. Note the server’s IP address, subnet mask, and default gateway – these values will be referenced throughout the scope configuration. A DHCP server must have a fixed IP address; a dynamically assigned address would cause the server’s own IP to change, breaking all client lease renewals.
Step 2 – Install the DHCP Server Role
Open Server Manager from the Start menu. In the Server Manager dashboard, click Manage in the top menu bar and select Add Roles and Features. The Add Roles and Features Wizard opens. On the Before You Begin page, click Next. On the Installation Type page, select Role-based or Feature-based installation and click Next.
Step 3 – Select the Destination Server
On the Server Selection page, ensure Select a server from the server pool is chosen and that your local server appears highlighted in the list. This is the machine that will run the DHCP Server role. Click Next to proceed to role selection.
Step 4 – Select the DHCP Server Role
On the Server Roles page, scroll through the list and check DHCP Server. A pop-up dialog prompts you to add required management tools alongside the role – click Add Features to include the DHCP management console and related tools. Click Next to proceed through the Features page (no additional features are required), then Next again on the DHCP Server information page.
Step 5 – Confirm and Install
On the Confirmation page, review the list of roles and features that will be installed. Verify that DHCP Server and DHCP Server Tools appear in the list. Click Install to begin. The installation typically completes within a few minutes. You can close the wizard while installation runs in the background – Server Manager will notify you when it completes.
Step 6 – Complete the Post-Installation Configuration
After installation finishes, a yellow warning notification flag appears in Server Manager’s notification area. Click the flag and select Complete DHCP Configuration to launch the DHCP Post-Install Configuration Wizard. This wizard handles the final setup steps required before the server can issue leases.
Step 7 – Skip Active Directory Authorization
The Post-Install Configuration Wizard’s key page for a standalone server is the Authorization screen. Because this server is not joined to a domain, it cannot be authorized in Active Directory. Select Skip AD authorization from the radio button options. Click Commit. The Summary page confirms that the DHCP Administrators and DHCP Users security groups were created successfully and that the authorization step was skipped. Click Close.
Step 8 – Open the DHCP Console
With the role installed, open the DHCP management console from Server Manager → Tools → DHCP. The console opens showing the server node. Expand the server to reveal the IPv4 and IPv6 nodes. The server is ready to have scopes configured – notice there are no scopes listed yet under IPv4.
Step 9 – Name the Scope
In the DHCP console, right-click IPv4 and select New Scope. The New Scope Wizard opens. Click Next on the welcome page. On the Scope Name page, enter a descriptive name for the scope and an optional description. The name appears in the DHCP console tree to identify this scope. Click Next.
Step 10 – Set the IP Address Range and Exclusions
On the IP Address Range page, enter the Start IP Address and End IP Address that define the pool. The wizard automatically calculates the subnet mask based on the class of the starting address – verify it is correct for your network and adjust if needed. Click Next. On the Add Exclusions and Delay page, add any IP addresses or ranges that should never be assigned by DHCP – for example, addresses already in use by printers, switches, or other static devices. Add each exclusion range and click Next.
Step 11 – Configure Lease Duration and Scope Options
On the Lease Duration page, set how long clients retain assigned addresses before renewal. The default is 8 days for wired networks. For networks with high device turnover (guest networks, wireless), shorter durations prevent pool exhaustion. Click Next. The Configure DHCP Options page asks whether to configure options now or later. Select Yes, I want to configure these options now and click Next – this allows you to enter the gateway and DNS settings immediately in the same wizard session.
Step 12 – Set the Default Gateway and DNS Servers
On the Router (Default Gateway) page, enter the IP address of the gateway clients will use to reach external networks. Type the IP and click Add. Click Next. On the Domain Name and DNS Servers page, enter the parent domain name and the IP address of the DNS server. Click Add to include the DNS server in the list. Click Next.
Step 13 – Skip WINS, Activate the Scope, and Finish
On the WINS Servers page, WINS (Windows Internet Name Service) is a legacy NetBIOS name resolution protocol. For modern networks, leave this blank and click Next. On the Activate Scope page, select Yes, I want to activate this scope now and click Next. Review the summary and click Finish – the scope is created and immediately begins issuing addresses.
Step 14 – Verify the Scope in the DHCP Console
After the wizard completes, return to the DHCP console. Expand the server node and the IPv4 node. The newly created scope appears listed under IPv4 with its IP range in the node name. Expand the scope to confirm all sub-nodes are present: Address Pool, Address Leases, Reservations, Scope Options, and Policies. The scope is active and ready to serve clients.
Step 15 – Configure the DHCP Client
On a Windows client machine connected to the same network as the DHCP server, open Network Adapter Properties and navigate to Internet Protocol Version 4 (TCP/IPv4) Properties. Select Obtain an IP address automatically and Obtain DNS server address automatically. Click OK. Open a command prompt and run ipconfig /all to verify the client received an address from the DHCP server. Confirm that the IPv4 address falls within the configured scope range, the subnet mask matches, the default gateway is correct, and the DHCP Server field shows the server’s IP address.
Step 16 – View Leases and Create Reservations
In the DHCP console, click Address Leases under the scope. The client’s lease appears in the list showing its IP address, name, and lease expiration. To permanently bind that IP to the client’s MAC address – ensuring it always receives the same address – right-click the lease entry and select Add to Reservation. The entry moves to the Reservations node, confirming the binding is established.
Best Practices for Standalone DHCP
- Use a Dedicated Static IP Outside the Scope – Place the DHCP server’s own IP address below or above the scope range. A server at
192.168.0.1with a scope of192.168.0.100-200is never at risk of the server’s own address being leased to a client - Document the Skip AD Authorization Decision – Administrators maintaining the server later may be confused by the unauthorized status in environments that later join a domain. Document that authorization was intentionally skipped due to the standalone deployment
- Plan for Growth – Size the scope generously from the start. Expanding a scope later requires temporarily deactivating it, which interrupts all active leases during the change window
- Create Reservations for Critical Devices – Use the Add to Reservation feature (or the Reservations node) to bind static-equivalent addresses to printers, servers, and other devices that need consistent IPs, while keeping their configuration managed centrally in DHCP
- Monitor Lease Utilization – Right-click the scope and select Display Statistics regularly. When available addresses drop below 20%, expand the scope or add exclusions for unused ranges to reclaim address space