I am in the process of migrating an existing domain from a Windows 2000 Domain Controller with Exchange 2003 to Windows 2008R2 with Exchange 2010.
I have configured a new Windows 2008R2 Hyper-V Guest onto the network using a static IP, with DNS pointing at the existing 2000 DC and joined the domain. I ran adprep32 /forestprep and /domainprep /gpprep on the 2000 DC (from the 2008R2 media /support folder). I then ran dcpromo on the 2008R2 machine which appeared to run successfully, apart from a message at the end of the process "A delegation for this DNS Server will not be created because the authoritative parent zone cannot be found or it does not support dynamic updates" which I ignored, as a quick search said the message was fine in a single domain.
Now I have the following issues:
Logging on to the 2008R2 machine using a domain account is very slow.
DNS resolution doesn't seem to work correctly - pinging the Windows 2000 DC by name doesn't return the correct IP address (just to confuse things, this site has a AD domain name set the same as their external DNS name, i.e. xyz.com). So pinging windows2000dc.xyz.com returns the external IP address of the web server for the domain rather than the internal IP address. Other 2008R2 member servers ping this internal machine by name just fine. NSLOOKUP returns the prompt "Default Server: UnKnown, Address: ::1" and doesn't resolve internal machine names correctly, but if I enter "server 184.108.40.206" (my 2000DC internal server IP) it resolves fine. Is the strange [inherited] internal IP range causing a problem here? The DNS server address of in the LAN card settings is set to the IP of the 2000DC server, but it's like the system is completely ignoring this.
Event Viewer shows several events on the 2008 machine: DNS Server event 4512 "The DNS server was unable to create the built-in directory partition ForestDnsZones.xyz.com. The error was 9906." and again with DomainDnsZones.xyz.com. I also have NTFRS event 13508 "The File Replication Service is having trouble enabling replication" and Directory Service event 1844 "The local domain controller could not connect with the following domain controller hosting the following directory partition to resolve distinguished names.", both indicating name resolution issues. (Correct, as name resolution doesn't appear to be working properly).
A search on these symptoms seems to reveal some commonality with other 2008R2 systems joining an existing 2000 AD domain, but with no real solutions. Best advice so far has been to transfer the Domain Naming Master FSMO role from the 2000 DC to the 2008 DC, which I have done but with no change so far.
Anyone else done a Windows 2000 to Windows 2008R2 AD migration (or just join) that may have seen any of these issues?