How to replace a Server 2003 domain controller with a new, better,faster piece of hardware?

  • Thread starter Thread starter rosevilleca
  • Start date Start date
R

rosevilleca

We were planning to replace an older Windows 2003 server that is
functioning as both a domain controller and a file server with a new
server that is faster, has more storage space and is better in every
way. There are also 2 other domain controllers in the domain.

We thought we could just do a complete backup pf the old server with
system state, install the OS on the new server and restore the system
state, but we found out that only works if the new server has the same
hardware.

So, what's the best method to move this old machine to a brand new
server?
It is not only a domain controller, but many network shares the users
need to access are on the old server.
 
Hello (e-mail address removed),

Install the new machine, promote to DC, make it DNS and GC. Give time for
replicating domain/dns infos. Move all data with robocopy from MS.

Export and import the regkeys:
From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

After everything is done run "dcdiag /v", "netdiag /v", "repadmin /showrepl"
and "dnslint /ad /s localhost" without the quotes to check for errors.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
Hello (e-mail address removed),

Install the new machine, promote to DC, make it DNS and GC. Give time for
replicatingdomain/dns infos. Move all data with robocopy from MS.

Export and import the regkeys:
From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

After everything is done run "dcdiag /v", "netdiag /v", "repadmin /showrepl"
and "dnslint /ad /s localhost" without the quotes to check for errors.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
Click to expand...

Sounds good.
By the way, the new hardware will need to have the same computer name
as the old server, so I assume than means we would need to depromote
the old server as one of the domain controllers and power it off or
disconnect it from the network before following the instructions
above.

To do the robocopy, they both need to be on the network at the same
time, so, to avoid the conflict of having two servers with the same
name on the network at the same time, do we need to name the new
machine something else and rename it to the old server's name after
robocopy is complete or rename the old server first?

Is there a log that shows when replication is complete or do you just
check accessing random AD objects after a few minutes? All the DCs
are physically in the same building.
I assume that since we do not need to import the system state from the
old machine, it doesn't matter if the new server has a new servicer
pack than the old server before dcpromo.
Do we need to do anything else such as manually add fsmo roles to the
new server?
 
I have an article that should help you out on decommissioning a dc

http://www.pbbergs.com/windows/articles.htm
Select Decommission a DC

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hello (e-mail address removed),

Install the new machine, promote to DC, make it DNS and GC. Give time for
replicating domain/dns infos. Move all data with robocopy from MS.
Click to expand...

Is there any reason why the new server needs to be a DNS server now if
the old server wasn't?
 
Hello (e-mail address removed),

see inline

Best regards

Meinolf Weber
Sounds good.
By the way, the new hardware will need to have the same computer name
as the old server, so I assume than means we would need to depromote
the old server as one of the domain controllers and power it off or
disconnect it from the network before following the instructions
above.
Click to expand...

Using the same name, makes it more complex. Important step is to demote the
server to member server. Then export the share regkey to have it saved. After
that rename it to whatever, reboot and check in DNS that all old name entries
are removed, if not do it by hand, then rename the preinstalled new server
to the old servername. After this is rebooted use robocopy to copy all data
including security to the new machine, then add the regkey with the sharenames.
To do the robocopy, they both need to be on the network at the same
time, so, to avoid the conflict of having two servers with the same
name on the network at the same time, do we need to name the new
machine something else and rename it to the old server's name after
robocopy is complete or rename the old server first?
Click to expand...

See above.
Is there a log that shows when replication is complete or do you just
check accessing random AD objects after a few minutes?
Click to expand...

With repadmin /showrepl you can control the replication between the machines
and also with replmon from the run line.
All the DCs
are physically in the same building.
I assume that since we do not need to import the system state from the
old machine, it doesn't matter if the new server has a new servicer
pack than the old server before dcpromo.
Click to expand...

Because you still have to DC's available and running no need to use system
state backup. Also it has to be the same SP/Patch level to use it. Don't
use it.
Do we need to do anything else such as manually add fsmo roles to the
new server?
Click to expand...

Before demoting the old server, make sure that one of the running DC's has
all 5FSMO roles and at least one of them is Global catalog server, in a single
forest domain better make all DC's Global catalog. Also you must have a running
DNS server.

See here about moving FSMO roles and add additional GC:
http://support.microsoft.com/kb/324801 http://support.microsoft.com/?id=31399
 
If you are speaking of copying non-dc related files then it would not be
related.

I am unclear on your reference to robocopy, is this in dealing with user
file shares? If so I would try and leave them on this machine as a member
server and find a different location to store users files.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
 
If you are speaking of copying non-dc related files then it would not be
related.

I am unclear on your reference to robocopy, is this in dealing with user
file shares?  If so I would try and leave them on this machine as a memberserverand find a different location to store users files.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008,2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.






- Show quoted text -
Click to expand...

The old server is going away and files that were copied with robocopy
to new server will be reshared on the new server. The new machine
will be a direct replacement for the old and will be named with the
same computer name. The users should not even be aware there is a new
server.

I think the other person's reply above will handle this problem.
 
Now, here is another related scenario.

What if the DC is moving to a "new" server that's the same brand and
model and the only hardware difference is different type hard drive
controllers and drives?

Would you then be able to just install the OS on the new server and
import the system state from backup and have it work as if it was the
orginal server?
 
On Jun 25, 9:39 am, Meinolf Weber wrote:
, then rename the preinstalled newserver
to the old servername. After this is rebooted use robocopy to copy all data
including security to the new machine, then add the regkey with the sharenames.
Click to expand...

Is this preinstalled server now already a domain controller at this
point or is at a member server and you run dcpromo after you import
the regkey from the first server?
I thought it wasn't a good idea to rename a domain controller.
Can you even rename it at all if the domain is Windows2000 mixed?
 
Back
Top