copy dhcp settings

Is there a way to seamlessly move our DHCP from our NT4 domain to our
Win2003 domain?
we have trusts relationships setup between the 2.

thanks

CR

Yup

http://support.microsoft.com/default...b;en-us;325473

"MS-News" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is there a way to seamlessly move our DHCP from our NT4 domain to our
> Win2003 domain?
> we have trusts relationships setup between the 2.
>
> thanks
>
> CR
>

There is nothing to move unless you run a bunch of Reservations or have a
ton of Scopes on the DHCP. Just configure the New one correctly and
shutdown the old one,..and you are done.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"MS-News" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is there a way to seamlessly move our DHCP from our NT4 domain to our
> Win2003 domain?
> we have trusts relationships setup between the 2.
>
> thanks
>
> CR
>
>

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. Recreating the scopes and
options is an exercise in drudgery and doing the whole cut the lease time
down, wait, deactivate old, activate new, wait, up lease time, wait, now you
are there, process is a pain.

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.

By copying the database you eliminate the all the potential lease conflict
issues, and the drudgery of recreating the scopes. As a bonus it gets the
task done in a few minutes.

There is an MS utility , i beilive it is called dhcp move, or you can copy
the dhcp database from one server to another using jetpack.

"Phillip Windell" wrote:

> There is nothing to move unless you run a bunch of Reservations or have a
> ton of Scopes on the DHCP. Just configure the New one correctly and
> shutdown the old one,..and you are done.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "MS-News" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Is there a way to seamlessly move our DHCP from our NT4 domain to our
> > Win2003 domain?
> > we have trusts relationships setup between the 2.
> >
> > thanks
> >
> > CR
> >
> >
>
>
>

"Manny Borges" <(E-Mail Removed)> wrote in message
news:71D46465-9135-4829-9186-(E-Mail Removed)...
> 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

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" <(E-Mail Removed)> wrote in message
> news:71D46465-9135-4829-9186-(E-Mail Removed)...
> > 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
>
>
>

"Manny Borges" <(E-Mail Removed)> wrote in message
news:C774CFBF-40A8-437C-9FED-(E-Mail Removed)...
> In all due respect that answer is irresponsible.

That doesn't sound very "all due respectful".
People usually say "with all due respect" just before they insult you. You
are free to disagree with my post or to ignore my posts, but insulting me is
a bit different.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

My initial string of "with all due respect" means that I am not trivializing
your technical knowledge. You obviosly have a grasp of the mechanics.

I never ridiculed *you*; I ridiculed your advice. I stand by my remarks.

NOW I will ridicule you. Let it go, you are wrong. I thank the lord daily
that I don't have reckless and pig headed techs on my team. If you ever want
to step up and play with the big boys you need to be able to consider all
aspects of an issue and be able to humbly accept when you are incorrect.

You can disagree if you want, but since you are nice enough to list out all
your impressive certs for me I can do the same. I won't post who i work for,
but i gaurantee you probably use our equiptment.

Manny Borges
MCT MCSE 2003,2000,nt 4.0 +security,MCSA, MCP ,MCDST,
Net+,A+,Security+.Inet+,Proj+,Serv+ CCNA, CIWCT, 3rd period hall monitor.

"Phillip Windell" wrote:

> "Manny Borges" <(E-Mail Removed)> wrote in message
> news:C774CFBF-40A8-437C-9FED-(E-Mail Removed)...
> > In all due respect that answer is irresponsible.
>
> That doesn't sound very "all due respectful".
> People usually say "with all due respect" just before they insult you. You
> are free to disagree with my post or to ignore my posts, but insulting me is
> a bit different.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

Manny, try losing the attitude.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

My apologies Todd, I was in a bad mood. I did not intend to be so abrasive. I
am not taking back anything I said, only admitting that I may have used
provocative language. I have no patience when it comes to pig headedness.



"Todd J Heron" wrote:

> Manny, try losing the attitude.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>