Link to home
Start Free TrialLog in
Avatar of usa12
usa12

asked on

Windows 2008 active directory issue!!!

Hi, I just join windows 2008 server as a domain controller to my existing windows 2003 domain. Now i have all this errors any quick solution that i can perform.
The Active Directory Main Services best practices Analyzers not able to collect data about the domain name of the dns record DcByGuid from the domain controller server1.
server1 is the server that has the error message. is acting as back up domain controller.
Avatar of Pramod Ubhe
Pramod Ubhe
Flag of India image

where do you see the errors on 2003 or 2008?
Is it first 2008 DC? if yes, have you prepared your environment for that? -
http://technet.microsoft.com/en-us/library/cc754670%28v=ws.10%29.aspx
Avatar of usa12
usa12

ASKER

Yes, this is my first 2008 dc, that I have joined into an existing 2003 domain. The error I see it on the 2008 server.
Have you prepared the env. for 2008 dc before?
The prev. link I provided has details about what is needed for 2008 details, mostly this is the most suspicious item in your case I believe.
Avatar of usa12

ASKER

Yes I did prepared the env. Using that same link you provided.
Do the following...
- Open cmd
- type dcdiag /dnsall and dcdiag /v
- Repadmin /replsum (check replication)
- repadmin /showrepl (check replication partitions)
- Check the directory services event logs to ensure that there are no errors

If you are getting error list the Source/ID here.
Avatar of usa12

ASKER

Ok, i ran all this commands that you suggested.. this is the event id 13562   source : ntfrs
Do you still have both DC's in the environment? Or did you transfer the FSMO roles to the new DC and then decommission the 2003 DC?

The event you are referencing is due to a old legacy GUID that no longer exists. See the following link for more detail...
http://social.technet.microsoft.com/Forums/windowsserver/en-US/742da3d2-ecfc-49fd-ad54-0f78177068be/old-server-remaining-in-frs-replication-causing-event-id-13562
Avatar of usa12

ASKER

This is how everything started.
I had a domain with 2 DC, running windows2003 server.
PDC had a hardware failure. I had to virtually restore PDC to domain.
Than I transfer  FSMO from PDC to BDC.
I also did the metadata clean up.
Once I finished that I disjointed the primary DC from domain.
And I gave my windows 2008 server the same name that the PDC had.
Avatar of usa12

ASKER

Yes, I first transfer FSMO roles to existing BDC 2003, than I decommission   the PDC  from domain.
Than I prepared the domain for a windows2008 server.but once I made it a DC it gives me the error that I posted.
ASKER CERTIFIED SOLUTION
Avatar of Santosh Gupta
Santosh Gupta

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