dhcp migration.. need to move ip address of the old server to new server

[compaq]

We're planning to migrate from NT4 servers to Windows 2003 servers.
The
current NT4 primary domain controller (which is also primary Wins,
DNS &
DHCP server) will be replaced by a brand new machine, and so, it will
not be
reused after the upgrade. Therefore, briefly said, the new Windows
2003
machine will be installed from scratch and will be synchronised with
our
current backup domain controller via Active Directory. But next, we'll
have
to migrate the Wins, DNS & DHCP functions from the NT4 platform to the
Windows 2000 platform as well.
We cant afford for the clients not to have network connectivity and
the IP address of DHCP server needs to be moved to the new dhcp
server.... any ideas how we can do this?

 

[Richard G. Harper]

http://www.microsoft.com/downloads/...26-81f0-478a-836c-b31ed463af5e&DisplayLang=en

DHCP Import/Export tool, from the Windows 2000 Server Resource Kit. Allows
you to move DHCP from WinNT to Win2K, or from Win2K to Win2K. Can be used
to move between WinNT servers also, but not from Win2K to WinNT.

 

[Guest]

I am having the same situation as "compaq", other than dhcp migration, the operations master role also have to migrate, and so on, can some one help me what are the necessary operation to be done.

TQ

http://www.microsoft.com/downloads/...26-81f0-478a-836c-b31ed463af5e&DisplayLang=en

DHCP Import/Export tool, from the Windows 2000 Server Resource Kit. Allows
you to move DHCP from WinNT to Win2K, or from Win2K to Win2K. Can be used
to move between WinNT servers also, but not from Win2K to WinNT.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

We're planning to migrate from NT4 servers to Windows 2003 servers.
The
current NT4 primary domain controller (which is also primary Wins,
DNS &
DHCP server) will be replaced by a brand new machine, and so, it will
not be
reused after the upgrade. Therefore, briefly said, the new Windows
2003
machine will be installed from scratch and will be synchronised with
our
current backup domain controller via Active Directory. But next, we'll
have
to migrate the Wins, DNS & DHCP functions from the NT4 platform to the
Windows 2000 platform as well.
We cant afford for the clients not to have network connectivity and
the IP address of DHCP server needs to be moved to the new dhcp
server.... any ideas how we can do this?

 

[Richard G. Harper]

If there is only one server present right now (or have more than one server
and you don't care where the FSMO roles land when you down the old server)
the fast way would be to bring up the new server as an additional domain
controller first.

Then get a copy of the Global Catalog on the new server:

http://support.microsoft.com/?kbid=313994

Next, get DNS configured on the new server and get it running, then figure
out how to get the new DNS server address to your clients. Easy way -
change the DNS server address option in the DHCP range settings, then wait
until all the clients have picked up the new DNS address when renewing their
leases.

Finally, run DCPROMO on the old server and it will transfer all FSMO roles
to the new server as it decommissions itself.

If you have more than one server now and care where the FSMO roles wind up,
read this article and use it to transfer the roles prior to decommissioning
the current server:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;255690

 

[Richard G. Harper]

You're welcome.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thank you, Richard G. Harper,

If there is only one server present right now (or have more than one
server
and you don't care where the FSMO roles land when you down the old
server)
the fast way would be to bring up the new server as an additional domain
controller first.

Then get a copy of the Global Catalog on the new server:

http://support.microsoft.com/?kbid=313994

Next, get DNS configured on the new server and get it running, then
figure
out how to get the new DNS server address to your clients. Easy way -
change the DNS server address option in the DHCP range settings, then
wait
until all the clients have picked up the new DNS address when renewing
their
leases.

Finally, run DCPROMO on the old server and it will transfer all FSMO
roles
to the new server as it decommissions itself.

If you have more than one server now and care where the FSMO roles wind
up,
read this article and use it to transfer the roles prior to
decommissioning
the current server:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;255690

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

I am having the same situation as "compaq", other than dhcp migration,
the
operations master role also have to migrate, and so on, can some one
help
me what are the necessary operation to be done.

TQ

 

[Guest]

Hi Richard,

I have followed exactly you mentioned, but unable to DCPROMO the current
PDC, other than can transfer the FSMO role manually as mentioned in
KB=255690, what other role or services need to be done before I can kill the
old PDC.

You're welcome.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thank you, Richard G. Harper,

If there is only one server present right now (or have more than one
server
and you don't care where the FSMO roles land when you down the old
server)
the fast way would be to bring up the new server as an additional domain
controller first.

Then get a copy of the Global Catalog on the new server:

http://support.microsoft.com/?kbid=313994

Next, get DNS configured on the new server and get it running, then
figure
out how to get the new DNS server address to your clients. Easy way -
change the DNS server address option in the DHCP range settings, then
wait
until all the clients have picked up the new DNS address when renewing
their
leases.

Finally, run DCPROMO on the old server and it will transfer all FSMO
roles
to the new server as it decommissions itself.

If you have more than one server now and care where the FSMO roles wind
up,
read this article and use it to transfer the roles prior to
decommissioning
the current server:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;255690

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


I am having the same situation as "compaq", other than dhcp migration,
the
operations master role also have to migrate, and so on, can some one
help
me what are the necessary operation to be done.

TQ

 

[Richard G. Harper]

If you followed the directions exactly, DCPROMO should demote the former AD
server to a member server. Do you get any error messages during the
process? Have you checked the event log (run EVENTVWR.EXE) to see what
light it can shed on the failure?

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm