Win2k Server migration - Old server to new server.

[bevan.lindsey]

Overview: Win2k Server migration - Old server to new server.
Customer has 30 users (mix of 2k pro and XP pro), 1 x Win2000 Server
(sp4) running AD.
Replacement of server driven by old hardware and a very average Win2k
domain implementation.
The existing server seems to work OK but has a long list of errors in
the event logs.

This is the process I have worked through thus far, followed by some
questions.

1. Installed new server Win2000
2. Added SP4 and windows update patches
3. Gave Server Static IP in same subnet as existing server
5. Pointed TCP/IP on new server at the existing Server for DNS
resolution.
3. Joined server to the existing domain
4. Ran dcpromo on the new server and made it another DC in the domain.

So far so good, can access the AD on the domain, can see existing
server and other w/s's on the Lan and vice versa. In the event log of
the new server I notice an error about not being able to create the
sysvol shares. Spent some time reading online, then notice on
the existing server Event log that the FRS service is having trouble
running. Also notice that the same server has some AD/DNS errors. Found
several articles that suggest that the database on the existing server
is possibly corrupt and that I should purge it, allowing the server to
recreate it.

QUESTIONS:
I have all the instructions but How risky is this? Currently the
existing server works and is the only DC, I really don't want to mess
with it and spend more time fixing a server that's going rather than
arriving.
I notice though that the event log on the new server seems to indicate
the AD content has replicated happily to it from the existing server.

With this in mind my plan from here is this:

1. Reboot the new server and bring back up on its own network separate
from the existing network.
2. Check that I can still browse the domain AD, see the users,
computers etc.
3. Setup DNS incl AD integration, also DHCP server
4. DC Promo the server to be the only DC.
5. Patch a workstation from the original network into the new network
and attempt a logon.

QUESTIONS:
Step 4 should sort out the sysvol issues shouldn't it?
Step 5 - Should this work, the SIDs etc?
Is there anything I am missing, do I need to remove references in AD to
the older existing server?

Thanks

 

[Paul Bergson]

You have provided so little info on the errors, it would be almost
impossible to provide any concrete feedback.

4) With out knowing exactly what is wrong there is no way to know what will
fix it.

5) Instead of moving the server to a new network just disconnect the older
server from your WAN to see if it authenticates users, etc... No reason to
put it on a seperate network.



Try running netdiag, repadmin and dcdiag. Look for fail, error and warning
errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /sC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt


See for more details

http://www.microsoft.com/technet/pr...Ref/1d4ce93c-54f2-4069-a708-251509c38837.mspx

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.