Automatically clear old DHCP reservations

Is there anyway to automatically clear old DHCP reservations from a windows
2003 DHCP server? I've got quite a few scopes with DHCP reservations and I
cant tell if they are stale or no. Preferably I would like to run something
that deletes old reservations based on time unused but not sure if that kind
of granularity exists.

The reason for the reservations are that we need to interface with a static
external DNS database. Thanks all.

"farcry80" <(E-Mail Removed)> wrote in message
news:777C6592-D8CF-43B0-BB10-(E-Mail Removed)...
> Is there anyway to automatically clear old DHCP reservations from a
> windows
> 2003 DHCP server? I've got quite a few scopes with DHCP reservations and
> I
> cant tell if they are stale or no. Preferably I would like to run
> something
> that deletes old reservations based on time unused but not sure if that
> kind
> of granularity exists.

Kind of a good reason to not have so many. The idea with reservations is to
only have a few,...if you have a lot,..then just statically assign the
machines in the first place and forget it.

As to your question, no, sorry, I do not know of any way.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Phillip,
Thanks for the reply.

I do wish I can get it away from this setup but the problem is that the DHCP
entries have to mirror an external static DNS database that is not AD
integrated and does not support DDNS. I would prefer to use leases where the
entries remain fresh but I can't think of a way to keep the exisiting good
DHCP entries static so they correspond to the external DNS database (which
have to be bulk loaded every few months manually).

"Phillip Windell" wrote:

>
> "farcry80" <(E-Mail Removed)> wrote in message
> news:777C6592-D8CF-43B0-BB10-(E-Mail Removed)...
> > Is there anyway to automatically clear old DHCP reservations from a
> > windows
> > 2003 DHCP server? I've got quite a few scopes with DHCP reservations and
> > I
> > cant tell if they are stale or no. Preferably I would like to run
> > something
> > that deletes old reservations based on time unused but not sure if that
> > kind
> > of granularity exists.
>
> Kind of a good reason to not have so many. The idea with reservations is to
> only have a few,...if you have a lot,..then just statically assign the
> machines in the first place and forget it.
>
> As to your question, no, sorry, I do not know of any way.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"farcry80" <(E-Mail Removed)> wrote in message
news:BFC9B78C-0624-4EC3-B812-(E-Mail Removed)...
> Phillip,
> Thanks for the reply.
>
> I do wish I can get it away from this setup but the problem is that the
> DHCP
> entries have to mirror an external static DNS database that is not AD
> integrated and does not support DDNS. I would prefer to use leases where
> the
> entries remain fresh but I can't think of a way to keep the exisiting good
> DHCP entries static so they correspond to the external DNS database (which
> have to be bulk loaded every few months manually).

I don't see how DHCP has anything to do with that at all.

If the goal is to just have the LAN Clients be able to resolve the Names
listed in the external DNS Server then do a Zone Transfer with the external
DNS Database. Then your internal AD/DNS would remain "aware" and have a
"copy" of the contents of the external DNS. Then the external DNS changes
its contents the AD/DNS would pickup the change the next time the Zone
Transfer updates.

Then:
> (which have to be bulk loaded every few months manually).

That sounds like a disaster all by itself. Someone needs to revisit why any
of that is done the way it is done to start with.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------