Sorry I didn't speficy in the beginning. We are talking about Microsoft DHCP using Windows 2003. I think Michael and Richard pretty much summed it up for me. During the course of my research, I also identified that most of our scopes are setup with a ridiculously short lease duration (3 days), given the fact we have a highly segmented network and use reservations for the vast majority of devices relying on DHCP. Fortunately, the short lease duration will work to my advantage as I start rolling out some options changes.
Thanks to everyone for the responses. - Sean On Mon, Jun 7, 2010 at 3:33 PM, Richard Stovall <rich...@gmail.com> wrote: > When making significant changes to a DHCP scope, I always start way ahead > of time and gradually reduce the lease time to something ridiculously (but > appropriately) short - even on the order of 5 or 10 minutes in some cases. > When the time to flip the big switch rolls around I can be well assured > that all the clients are updated within the lease period after I make the > drastic change. It takes a small amount of planning, but this approach > hasn't failed me yet. > > All that said, I pretty much agree with Ben's response. A DHCP client, is > a DHCP client, is a DHCP client. Whatever implementation of the protocol > that client uses shouldn't change whether its leased IP is either a > reservation or truly dynamic. After all, how would it know? What I hadn't > considered is the notion that a DHCP server might dole out longer lease > times to clients with reservations than to dynamic clients within the same > scope. I guess it's possible, but it pretty much flies in the face of the > rationale for having a DHCP reservation vs a true static IP. I'm pretty > sure the MS DHCP role doesn't do this, but I'm happy to be corrected if > wrong. > > On Mon, Jun 7, 2010 at 7:08 PM, Ben Scott <mailvor...@gmail.com> wrote: > >> On Mon, Jun 7, 2010 at 6:53 PM, Sean Martin <seanmarti...@gmail.com> >> wrote: >> > Do clients with a DHCP reservation go through the same renewal process >> > (check once at 50%, try again at 87.5%, etc.)? >> >> I believe a DHCP reservation is simply a server configuration >> artifact, not something in the actual DHCP wire protocol. >> >> So, that would really depend on the implementation, of both server >> and client. First, it will depend on what the server gives for a >> lease time on reservation. I imagine a server could just use the same >> lease time it does for dynamic IP addresses in the scope, or it could >> issue an infinite lease time. Then it depends on the client. A >> client with an infinite lease time may decide it should check in >> periodically anyway, or restart its DHCP cycle for other reasons. >> >> -- Ben >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
