Win2k Std Server Move to new HD

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

Guest

Hello,

Running out of space on my C: drive. I have a RAID array, going to add
another hard drive the array and increase space.

This server is:
-Domain Controller
-DHCP Server

Anyone done this process or have any tips?

I also will be purchasing 2 new servers to replace existing servers, I'd
like to do a simple copy to the new servers and have hardware reconfigured.

I guess I'm looking for some general info on this, things other people have
done. Microsoft should really have a simplier method of moving between
hardware.

Thanks for the help!
Andy
 
AndyVM said:
Hello,

Running out of space on my C: drive. I have a RAID array, going to add
another hard drive the array and increase space.

This server is:
-Domain Controller
-DHCP Server

Anyone done this process or have any tips?
Click to expand...

We don't know if the RAID is software or a hardware RAID. We don't know what
RAID type is used.
I also will be purchasing 2 new servers to replace existing servers, I'd
like to do a simple copy to the new servers and have hardware reconfigured.

I guess I'm looking for some general info on this, things other people have
done. Microsoft should really have a simplier method of moving between
hardware.

Thanks for the help!
Andy
Click to expand...

Copying is not an option, there is a much faster and reliable way. From
W2K's perspective, the DCs are computer SIDs replicating in a Domain SID
using secure replication. The only reason a user account, a computer account
and a domain have names is to satisfy human's craving for names. W2K doesn't
care, know or rely on names. Only dns resolution uses names to resolve
ip_addresses.

Join the new servers as member servers in the domain, promote them to DCs,
transfer the FSMO roles to them (critical), complete a replication cycle,
check logs, and finally: demote the old DCs. Thats quite a bit simpler than
copying. Consider using some of the resource kit's replication tools (ADRM,
DomMon, NetDiag, NTDSUtil) and leave demotion for another day (for the old
servers).
The goal here is not to loose the domain's integrity. Thats why a copy or
ghost isn't supported.

The exception in the above procedure is in the case you are upgrading the
domain's OS. Even then, its best to install the prevalent OS on the new
system, join, promote transfer FSMO roles and upgrade the PDC emulator to
the new OS with new CD-media (follow the manufacturer's procedure). Do this
with one of the old DCs offline for domain recovery.

Ive seen client ghosts fail on the exact same hardware just because a given
card was in another slot. Consider the implications of a tcp/ip stack with
an incorrect MAC address. What if the old chipset on motherboard doesn't
match the new? And the list goes on and on. Copying or ghosting a DC is a
recipe for disaster.
 
Back
Top