Manual Migration of Active directory? Help needed!

[Craig N.]

I am working with a company, roughly 300 users, and the
entire network is crashing constantly, especially citrix.
We have decided to rebuild the entire network from
scratch, and not do any automated migration, since that
is what was done last time right before the network went
to crap.

Anyways, I have manually added all the users onto a new
domain controller, and I have set the domain name as the
same one as the old server.

Here is the problem, I add the computer name manually to
the new domain controller, and move a computer from the
old domain(same domain name)over, it wont connect, unless
I go in to it, and add it to the domain from the
workstation. Can I get around this? I cant go to 300
computers and rejoin them to the domain manually.

SO, the specs of the new domain controller are the same
as the old, same name, same IP's, everything. How do I
manually add the computers into the domain and get it to
work?

Here is my second question, if anyone can help, the login
times on the new domain controller are horrible, like 4-5
minutes. Anyone know what can cause this?

Here is my configuration:
-2 HP DL380 rackmount servers
dual Xeon 3.4 ghz, 2 gig ram, 5 36 gb drives in raid 5
-Windows 2000 Server Service Pack 4
-Active Directory, DNS, and DHCP on both servers.
-One server is the primary, the other is acting as a back-
up, like the old PDC/BDC concept.

Please send me an e-mail (e-mail address removed) if you can help
out.

I'm a big 2003 guy now, and love it, but forgeting all my
2000 stuff, and the company thinks 2003 is too unstable
to run.

 

[Danny Sanders]

it wont connect, unless

I go in to it, and add it to the domain from the
workstation. Can I get around this? I cant go to 300
computers and rejoin them to the domain manually.

AFAIK the only way to add the computer to a domain is from the local
computer.

SO, the specs of the new domain controller are the same
as the old, same name, same IP's, everything. How do I
manually add the computers into the domain and get it to
work?

Same name, same IP, but different SAM. Because you did a fresh install the
SAM is different. Different SAM = different domain. Different domain = add
computers to the new domain.

Here is my second question, if anyone can help, the login
times on the new domain controller are horrible, like 4-5
minutes. Anyone know what can cause this?

Improperly configured DNS. The client computer MUST point to the DNS server
set up for AD.
See:
How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675





hth

DDS W 2k MVP MCSE

 

[Guest]

Thanks for the bad news I guess I have a lot of work
ahead of me.

Anyways, as far as the slow login, the clients are on
DHCP, and DHCP is pushing the Primary and Secondary dns
info as the DNS servers running on active directory. Any
other ideas?

 

[Danny Sanders]

Is the DNS server pointing to itself for DNS?
Is it registering SRV records?

From the clients run ipconfig /flushdns followed by ipconfig /registerdns.

Check the logon time

hth
DDS W 2k MVP MCSE

 

[Guest]

The network settings of the server point to both itself,
and the secondary DNS.

Now here is something weird, when logging a user onto the
domain through a win 2000 server, it flies, but on an xp
machine, it is real slow. Make any sense?

 

[Danny Sanders]

Do the clients point to the AD DNS server ONLY?


DDS