Link to home
Start Free TrialLog in
Avatar of zotfarms
zotfarmsFlag for United States of America

asked on

Migrate from Server 2003R2 to 2008R2. Can't find domain if old DC is disconnected.

I just migrated from Server 2003R2 Standard to Server 2008R2 Standard.  I upgraded the old domain to 2003 native mode. Performed forest prep.  When I performed the adprep / domainprep /gpprep I got an error. so I ran just the domainprep switch and got a reply that the changes had already been made. I connected the 2k8 to the domain, set static IP for IPv4 and IPv6, installed Active Directory Domain services, ran DC Promo, allowed install of DNS.  I moved all FSMO roles.  If I run netdom query fsmo all lines show the new DC and it is the primary DC.  Just to check to make sure everything is working, I removed the network cable from the old DC.  When it is disconnected, not even the new DC can find the domain.  I have pointed DNS to the new server including the server itself and all workstations and the old DC. Is this possibly a DNS problem, or did I have a bad migration and should start from scratch.  I only have about 15 users.
Avatar of Pradeep Dubey
Pradeep Dubey
Flag of India image

Have you checked event logs in 2k8 for AD related issues?

Seems something wrong or missed during the migration.

Check the logs once and confirm the same.
Hi

What you mean not even the new DC can find the domain. What is the primary DNS of the 2008 server(set it to 127.0.0.1) also make sure clients Primary DNS pointing to 2008 IP.

Also check in dnsmgmt.msc--msdcs folder--> Pdc-- Dc-- sites--> kerberos and ldap records ip pointing to 2008 server.

Thanks
Jai
Avatar of zotfarms

ASKER

If I disconnect the old DC and then open up Domain Users and Computers on the 2k8, I get an error that the domain does not exist.  When I reconnect the old DC that snapin will work.
Did You check by right click change domain controller option in the snapin and which DC it connected to. make sure it connected to 2008 DC. Also check any errors you are getting in eventvwr. provide screenshot of the error.
User generated imageThis is the screen shot for DC folder. 69thdadc is the new 2k8 server.
Avatar of bgrabbe
bgrabbe

Did you make sure to point the new DC as itself for primary DNS and set the clients for the same? It sounds like you've got the new server and the clients still pointing at the old DC for their primary DNS. Make sure you use the proper IP of the server and not 127.0.0.1. Also make sure you've updated your DHCP scope, as there may be DNS pointers to the old server there.
User generated image
This is the PDC folder.
can you read this article once and check your steps you did to migrate. Seems something you missed.

http://social.technet.microsoft.com/forums/en-US/winserverMigration/thread/547c94ba-3826-4e7a-b9ad-80b308beced4/
User generated image

This is the authentication error that I get from a client machine with the old DC disconnected.  This also shows that the primary DNS points to the new server.
Which one is your dhcp server. Why you manually updated the dns in client machine.? Whether your 2003 DC holding dhcp server.? update the dns in the scopes of your dhcp server.
One other thing that I have noticed is that in the network and sharing center, the network type in the new server is private rather than domain.  Any ideas that would cause that?
Network type change to domain, and then try again.
I ran dcdiag on the new server.  I noticed that there were errors regarding sysvol being synchronized.  I then looked at the shares on the server.  NETLOGON and SYSVOL shares were not created on the new server.  Also the folders Policies and Scripts under C:\windows\Sysvol\sysvol\{domain}\ were not created either.  I moved all the fsmo roles back to 2k3, demoted the 2k8 and then repromoted it, but same result.
Can you do a force replication once and after that run dcdiag, check what other error you are getting..
post that errors here.
ASKER CERTIFIED SOLUTION
Avatar of zotfarms
zotfarms
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I wish there had been a way to preserve the old domain, but with only 10 users, it was more practical to create a fresh AD.