Link to home
Start Free TrialLog in
Avatar of alexfarias
alexfariasFlag for Brazil

asked on

problems to Migrate Windows 2003 domain to Windows 2008

In need to migrate my Domain Controller to Windows 2003 R2 to Windows 2008 R2 I followed the nice tutorial, written by TigerMatt: # a22052091

I did everything step-by-step, no hurry, however when I disabled the old DC to verify that the new dc was functional, the AD did not rise. and the following message appears:

Naming information cannot be Located because...

Then I click OK and the AD is empty.
Then I click change domain controller, Active Directory users and computers and the same is empty, do not seem to be connected anywhere, when what I expected, is that he was the Operations Master, and Domain controller after all the main steps followed in the aforementioned tutorial.

Some have a clue?

Avatar of Adrian Cantrill
Adrian Cantrill
Flag of Australia image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
it looks like at the very least that the DNS server either isnt available, or doesnt have any SRV records...

Can you use DNS manager, and connect to the new server and show is the forward and reverse zone information?

specifically that it has

Forward Lookup Zones/Domain_Name/_msdcs/dc/_sites/Default-First-Site-Name/_tcp
Forward Lookup Zones/Domain_Name/_msdcs/dc/_tcp
better still, follow the guides here and verify that your DNS server (should be AD integrated) is working. If it is, then we can look at the FSMO role stuff, if its not then potentially either the DNS hasnt moved correctly, or you have missed a step.
Avatar of alexfarias


I think I got it!
I checked the new DC, the PDC and Infrastructure were still with the old server as a master of operations.
So I went in the old server, Operations Master and changed pointing to the new server.
deactivated the old DC and went to the new dc. In the new DC, when I opened the AD found that he was still "empty", clicked change Domain controller and found that they had to appear in the list the DC's assets was written: Type the directory server name. I typed the name of the new DC and it connected!

Want to know what was the problem? Too lazy to read. LOL

Thanks for the support
Yep - though as much. For problems as you describe its also a FSMO placement, or a DNS issue. Glad i could help.
always , not also :)
if the issue is sorted please close & award and ill remove it from my list :)
Here is the first problem you should never just shutdown a DC.

First thing check your DNS settings on the servers they should be pointing to themselves as primary in TCP\IP settings for DNS. There should be no external DNS servers listed.

Make sure your new DC is a Global Catalog. Make sure the new DC holds on FSMO roles.

Run dcdiag post results.
I thought the problem was "PDC and Infrastructure master" still on the old server, if so, i mentioned that as my first post ? why close, rather than award points ?
changed...sorry, my bad....