<div>
I was always told to set static IP's outside of the scope.
</div>


<div>
No, the static ip's will be labeled as used to the rest of the clients using DHCP. 
</div>


<div>
Also If you have a list of the static ips to computers you can also create reservations if you plan to use IPv4
</div>


<div>
@ all<br />
<br />
Wait, so yes or no? &nbsp;I am not planning on leaving the static addresses permanently. &nbsp;It would just be while I am working to switch the entire network over to DHCP...
</div>


<div>
I believe that by default, there will be conflicts, since the DHCP server assumes it has control over the entire range and does not (by default) verify that an address is free.<br />
<br />
But if you Enable address conflict detection on the Windows Server, that should allow you to keep the fixed IP address machines going without conflict.
</div>


<div>
@ sjklleion42<br />
<br />
Ohh, ok I see. &nbsp;I will give this a try and see what happens. &nbsp;Thanks for the input!!
</div>


<div>
This worked!! &nbsp;Enabled Address Conflict Detection and once DHCP was turned on the existing static addresses were not affected. &nbsp;Thanks!!
</div>


<div>
<div class="content wysiwyg-content">
All clients in my environment are currently configured statically. &nbsp;I am in the process of converting to DHCP on my Windows Server 2008 server. &nbsp;What I am wondering is, if I enable a scope within the same network, will the remaining statically assigned clients conflict with DHCP?
</div>
</div>


All clients in my environment are currently configured statically.  I am in the process of converting to DHCP on my Windows Server 2008 server.  What I am wondering is, if I enable a scope within the same network, will the remaining statically assigned clients conflict with DHCP?

I was always told to set static IP&#39;s outside of the scope.

No, the static ip&#39;s will be labeled as used to the rest of the clients using DHCP. 

Also If you have a list of the static ips to computers you can also create reservations if you plan to use IPv4

@ all

Wait, so yes or no?  I am not planning on leaving the static addresses permanently.  It would just be while I am working to switch the entire network over to DHCP...

I believe that by default, there will be conflicts, since the DHCP server assumes it has control over the entire range and does not (by default) verify that an address is free.

But if you Enable address conflict detection on the Windows Server, that should allow you to keep the fixed IP address machines going without conflict.

@ sjklleion42

Ohh, ok I see.  I will give this a try and see what happens.  Thanks for the input!!

This worked!!  Enabled Address Conflict Detection and once DHCP was turned on the existing static addresses were not affected.  Thanks!!

Will statically assigned clients within a DHCP scope cause a problem?

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.