Changing IP address on DC to replace existing server with new hard

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have just put up a new W2K DC (on new hardware) and I'd like to put it into
place to replace an existing DC with older hardware (which I will remove and
later take out of service, after I'm sure everything works).

Existing servers:
ServerA (old hardware) - 10.10.10.1 - runs MS-DNS and WINS
ServerB (old hardware) - 10.10.10.2 - runs MS-DNS and WINS
ServerC (old hardware) - 10.10.10.3 - runs MS-DNS and WINS

all site clients point "statically" to any two of the above servers.

WINS is configured to use ServeB as the "center" of hub-n-spoke replication
(both server A and server C replicate only to server B not with each other.

The DNS zones are AD-integrated.

New server:
ServerD (new hardware) - 10.10.10.10 - runs MS-DNS and WINS


Here are the steps I was going to follow.

1) Re-Address "old" ServerA from 10.10.10.1 to 10.10.10.55

2) Reboot serverA - then fix up WINS replication between it and ServerB so
WINS replication continues between these servers even though clients will no
longer actually use this machine. Later I'll stop the DNS/WINS services on
this machine, DE-promote it and take it off-line.

3) Re-Address "new" ServerD from 10.10.10.10 to 10.10.10.1 so it answers to
all clients already statically configured to look to "that" address for
DNS/WINS resolution.

4) Reboot ServerD - then fixup WINS replication between it and ServerB.

5) Make ServerD a GC because ServerA was a GC (I'll do this sometime before
I de-promote ServerA). Note there are other GCs in the forest.

questions.

- Will these steps work?

- Am I missing anything?

- What will happen to the WINS records owned by ServerA,
will ServerD eventually take ownership of these records?

- ServerD was automatically configured by netlogon with an NS record for the
AD integrated zones, when I re-address both serverA and serverD will the
netlogin service again automatically change the NS records for each server as
they are re-addressed and rebooted (or will I need to do that manually) to
make sure the NS records point to the correct IP address after the change.

- Should I configure the WINS/DNS clients "on" Servers A & D to point to
server B (since it won't be moving and will always be findable) before I
attempt the re-address them.
 
billmt1 said:
I have just put up a new W2K DC (on new hardware) and I'd like
to put it into
place to replace an existing DC with older hardware (which I
will remove and
later take out of service, after I'm sure everything works).

Existing servers:
ServerA (old hardware) - 10.10.10.1 - runs MS-DNS and WINS
ServerB (old hardware) - 10.10.10.2 - runs MS-DNS and WINS
ServerC (old hardware) - 10.10.10.3 - runs MS-DNS and WINS

all site clients point "statically" to any two of the above
servers.

WINS is configured to use ServeB as the "center" of
hub-n-spoke replication
(both server A and server C replicate only to server B not
with each other.

The DNS zones are AD-integrated.

New server:
ServerD (new hardware) - 10.10.10.10 - runs MS-DNS and WINS


Here are the steps I was going to follow.

1) Re-Address "old" ServerA from 10.10.10.1 to 10.10.10.55

2) Reboot serverA - then fix up WINS replication between it
and ServerB so
WINS replication continues between these servers even though
clients will no
longer actually use this machine. Later I'll stop the
DNS/WINS services on
this machine, DE-promote it and take it off-line.

3) Re-Address "new" ServerD from 10.10.10.10 to 10.10.10.1 so
it answers to
all clients already statically configured to look to "that"
address for
DNS/WINS resolution.

4) Reboot ServerD - then fixup WINS replication between it and
ServerB.

5) Make ServerD a GC because ServerA was a GC (I'll do this
sometime before
I de-promote ServerA). Note there are other GCs in the
forest.

questions.

- Will these steps work?

- Am I missing anything?

- What will happen to the WINS records owned by ServerA,
will ServerD eventually take ownership of these records?

- ServerD was automatically configured by netlogon with an NS
record for the
AD integrated zones, when I re-address both serverA and
serverD will the
netlogin service again automatically change the NS records for
each server as
they are re-addressed and rebooted (or will I need to do that
manually) to
make sure the NS records point to the correct IP address after
the change.

- Should I configure the WINS/DNS clients "on" Servers A & D
to point to
server B (since it won't be moving and will always be
findable) before I
attempt the re-address them.
Click to expand...

Make sure you have a full backup of your system. What do you use to
back it up?

This is the process you need to follow:

1. Install OS on new hardware.
2. Install Service Pack to same level as old hardware.
3. Ensure all hotfixes, etc, etc are installed from WindowsUpdate.
4. Reboot the server into Directory Services Restore Mode (you have
to).
5. Ensure all partitions are created for all your drives that are in
old hardware.
6. Restore full system (C:, D:, etc and System State) except the
following files:

c:\boot.ini
c:\ntldr
c:\ntdetect.com
c:\winnt\system32\hal.dll
c:\winnt\system32\kernel32.dll
c:\winnt\system32\ntdll.dll
c:\winnt\system32\ntoskrnl.exe
c:\winnt\system32\ntkrnlpa.exe
c:\winnt\system32\win32k.sys
c:\winnt\system32\winsrv.dll

If you cannot omit these files (because they are part of system
state), then make sure you have copies of them. Then when you reboot,
you will have to copy these back to the original location. Also, if
you are using an array controller, find out what the .sys file is for
it (eg, compaq usually run cpqarray.sys or cpqcissm.sys). Make sure
you have a copy of this. If the array controller in your new system is
different, you have to do the following:

Eg: cpqcissm.sys in new system, cpqarray.sys in old system.

When you boot new system after restore, it will attempt to load
cpqarray.sys because of the restore. So, copy cpqcissm.sys
cpqarray.sys. The OS will load cpqarray.sys, but you’ve actually got
it loading cpqcissm.sys for your new hardware. This is done at the
same time you copy back the other files, or you can do it prior to
rebooting the system after restore.

Before rebooting, remove your video card and all network cards to save
conflicts and problems when the OS reboots.

If your partition is NTFS, you would need NTFSDOS, ERD Commander, or
the Windows 2000 tool to boot to DOS (it will require the Admin
password prior to joining or creating a domain - eg local admin pwd
not domain admin).

Once you have done this, and rebooted for the first time and logged
in, check the Event Log for errors. The startup process could take a
long time so be patient and don’t reboot. If you do, it’ll get trashed
and you’ll have to start again. After logging in, do not reboot it
else it will get trashed if there are errors in the Event Log and you
have to start again. These need resolving before you reboot. I will
help you with this if you get the errors.

Install your video card and network card drivers once you’ve logged
in, check for errors and report back for resolution. If there aren’t
any, then you will be safe to reboot, but I reckon there will be one
or two. If you don’t already have them, install the Windows 2000
Support Tools, as we will need them if there are errors.
 
Back
Top