Microsoft Windows DHCP Team Blog : PXE/BOOTPhttp://blogs.technet.com/teamdhcp/archive/tags/PXE_2F00_BOOTP/default.aspxTags: PXE/BOOTPen-USCommunityServer 2.1 SP1 (Build: 61025.2)Identify a PXEClient/BootP and assign a shorter leasehttp://blogs.technet.com/teamdhcp/archive/2007/02/12/identify-a-pxeclient-bootp-and-assign-a-shorter-lease.aspxMon, 12 Feb 2007 12:50:00 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:639076teamdhcp2http://blogs.technet.com/teamdhcp/comments/639076.aspxhttp://blogs.technet.com/teamdhcp/commentrss.aspx?PostID=639076http://blogs.technet.com/teamdhcp/rsscomments.aspx?PostID=639076This is quite possible &amp; common scenario that PXEClient/BOOTP client and normal Windows Client exists in the same network and share a single scope of IPaddress. Normally, PXEClient are used only for very limited purpose &amp; short period. Hence limiting...(<a href="http://blogs.technet.com/teamdhcp/archive/2007/02/12/identify-a-pxeclient-bootp-and-assign-a-shorter-lease.aspx">read more</a>)<img src="http://blogs.technet.com/aggbug.aspx?PostID=639076" width="1" height="1">PXE/BOOTPLease Time