Re: copy dhcp settings
- From: Manny Borges <MannyBorges@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Jun 2005 10:15:06 -0700
In all due respect that answer is irresponsible.
Any disruption of service that occurs that *can* be avoided yet is not is
ridiculous.
It is also fiscally irresponsible to use the resources or one or more admins
to run the whole simple yet time consuming process already documented here
when it can be done in a matter of minutes with a tool.
Then to waste time cleaning up you mess afterward? Sure its a simple fix in
your eyes, but to an enduser its a major pain in the tush; it makes them
unhappy. When the users have network issues your reputation as a network
admin takes a hit.
"Phillip Windell" wrote:
>
> "Manny Borges" <MannyBorges@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:71D46465-9135-4829-9186-9032D4FB71B7@xxxxxxxxxxxxxxxx
> > No offense, but there can be a lot to move. A single DHCP server could
> have
> > many scopes and a whole bunch of active leases.
>
> That is what I said.
>
> ".....unless you run a bunch of Reservations or have a
> ton of Scopes on the DHCP"
>
> > My specific issue with your post is that your advice will casue havoc in a
> > network with users that may occasionally work from home. When they log on
> and > get a new address they can could have an instant IP conflict with a
> client
> > who believes it has a valid lease but that the new DHCP server knows
> nothing
> > about.
>
> We've been through all that here. The actual occurances were very few and
> short lived. It certainly was not "havoc". I simply set the lease period
> on the old server to a very short period of time and waited until the new
> period had propagated to all clients. Switch the servers at a low traffic
> period, by the time it hit a high traffic period the leases had long expired
> and everything was fine. Out of our whole system I think I only had one
> conflict,..a quick "renew/release" on the two machines and all was well. The
> new server set the lease period back to what it originally was.
>
> I am not opposed to using the utility when it is needed, I just don't think
> people have to get all worried about it in every instance.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
.
- References:
- copy dhcp settings
- From: MS-News
- Re: copy dhcp settings
- From: Manny Borges
- copy dhcp settings
- Prev by Date: Re: 2003 server NetDiag results
- Next by Date: terminal services
- Previous by thread: Re: copy dhcp settings
- Next by thread: Re: copy dhcp settings
- Index(es):
Relevant Pages
|