<div>
Hi durango099! 
 
Glad youve put a new question in mate. You should get more AD experts on this one rather than the exchange ones your original question was aimed at :-) 
 
Anyway, lets look at a starting point from your DCDiag results. 
 
Start with opening AD users &amp;&nbsp;computers and locate the computer object for the new server. Which OU is it in? Does it show errors when you open properties? 
Find it in your primary DNS zone too and confirm it is the right IP.
</div>

<div>
1st, the easy question: 
 
DNS, yes the correct IP is listed. It is also listed as the Start Of Authority , and Name Server - the logs only show it starting and that the zone has finished loading. 
 
The new and old DC's are located in the domain.local, Domain Controllers OU. 
No errors when opening up properties, under NTDS settings connections tab it has the old (file01)2003 DC listed in the replication to &amp;&nbsp;from. 
 
Should I allow DCDIAG to try and &quot;FIX&quot; - I have not run the command you referenced in the Exchange question. 
 
Mark
</div>

<div>
The dcdiag results are showing that your sysvol is not replicating properly. 
 
Have the roles been moved over to the new DC (2008) successfully? 
 
run the following commands... 
- netdom query fsmo 
- netdom query dc 
 
Also try looking at the FRS services on both domain controllers as this is the service a 2003 to 2008 sysvol replication will use. The quickest way to resolve issues like this is to demote and re-promote the DC. I have seen issues with sysvol replication going from 2003 to 2008 DC's. 
 
Will.
</div>

<div>
I have demoted the AD-PDC 2008r2 server and re-promoted it with no change. 
 
Microsoft Windows [Version 6.1.7601] 
Copyright (c) 2009 Microsoft Corporation. &nbsp;All rights reserved. 
 
C:\Users\administrator&gt;netdom query fsmo 
Schema master &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; AD-PDC.dme.local 
Domain naming master &nbsp; &nbsp; &nbsp; &nbsp;AD-PDC.dme.local 
PDC &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; AD-PDC.dme.local 
RID pool manager &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AD-PDC.dme.local 
Infrastructure master &nbsp; &nbsp; &nbsp; AD-PDC.dme.local 
The command completed successfully. 
 
C:\Users\administrator&gt;netdom query dc 
List of domain controllers with accounts in the domain: 
 
FILE01 
AD-PDC 
The command completed successfully. 
 
Regarding FRS - there are FRS errors about SysVol: 
Log Name: &nbsp; &nbsp; &nbsp;File Replication Service 
Source: &nbsp; &nbsp; &nbsp; &nbsp;NtFrs 
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;12/23/2015 12:03:41 PM 
Event ID: &nbsp; &nbsp; &nbsp;13565 
Task Category: None 
Level: &nbsp; &nbsp; &nbsp; &nbsp; Warning 
Keywords: &nbsp; &nbsp; &nbsp;Classic 
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N/A 
Computer: &nbsp; &nbsp; &nbsp;AD-PDC.domain.local 
Description: 
File Replication Service is initializing the system volume with data from another domain controller. Computer AD-PDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. 
&nbsp; 
To check for the SYSVOL share, at the command prompt, type: 
net share 
&nbsp; 
When File Replication Service completes the initialization process, the SYSVOL share will appear. 
&nbsp; 
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers. 
 
C:\Users\administrator&gt;net share 
 
Share name &nbsp; Resource &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Remark 
 
------------------------------------------------------------------------------- 
C$ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; C:\ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Default share 
IPC$ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Remote IPC 
ADMIN$ &nbsp; &nbsp; &nbsp; C:\Windows &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Remote Admin 
The command completed successfully. 
 
I am downloading FRSDiag to see about this issue. 
 
Mark
</div>

<div>
Looking at the 2003 NRS logs: 
 
Event Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Error 
Event Source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NtFrs 
Event Category: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;None 
Event ID: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;13568 
Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;12/10/2015 
Time: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;8:10:20 PM 
User: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N/A 
Computer: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FILE01 
Description: 
The File Replication Service has detected that the replica set &quot;DOMAIN SYSTEM VOLUME (SYSVOL SHARE)&quot; is in JRNL_WRAP_ERROR. 
&nbsp; 
&nbsp;Replica set name is &nbsp; &nbsp;: &quot;DOMAIN SYSTEM VOLUME (SYSVOL SHARE)&quot; 
&nbsp;Replica root path is &nbsp; : &quot;c:\windows\sysvol\domain&quot; 
&nbsp;Replica root volume is : &quot;\\.\C:&quot; 
&nbsp;A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. &nbsp;This can occur because of one of the following reasons. 
&nbsp; 
&nbsp;[1] Volume &quot;\\.\C:&quot; has been formatted. 
&nbsp;[2] The NTFS USN journal on volume &quot;\\.\C:&quot; has been deleted. 
&nbsp;[3] The NTFS USN journal on volume &quot;\\.\C:&quot; has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. 
&nbsp;[4] File Replication Service was not running on this computer for a long time. 
&nbsp;[5] File Replication Service could not keep up with the rate of Disk IO activity on &quot;\\.\C:&quot;. 
&nbsp;Setting the &quot;Enable Journal Wrap Automatic Restore&quot; registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. 
&nbsp;[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run &quot;net stop ntfrs&quot; followed by &quot;net start ntfrs&quot; to restart the File Replication Service. 
&nbsp;[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. 
&nbsp; 
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. 
&nbsp; 
To change this registry parameter, run regedit. 
&nbsp; 
Click on Start, Run and type regedit. 
&nbsp; 
Expand HKEY_LOCAL_MACHINE. 
Click down the key path: 
&nbsp; &nbsp;&quot;System\CurrentControlSet\Services\NtFrs\Parameters&quot; 
Double click on the value name 
&nbsp; &nbsp;&quot;Enable Journal Wrap Automatic Restore&quot; 
and update the value. 
&nbsp; 
If the value name is not present you may add it with the New-&gt;DWORD Value function under the Edit Menu item. Type the value name exactly as shown above. 
 
For more information, see Help and Support Center at <a href="http://go.microsoft.com/fwlink/events.asp" rel="ugc">http://go.microsoft.com/fwlink/events.asp</a>.
</div>

<div>
On the 2003 server I did this and am waiting for results: 
 
The global 
BurFlags 
registry key is found in the following location in the registry: 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup / Restore\Process At Startup 
 
I set this to D4, restarted the FRS service and the event logs now say all is well. 
 
Again, this was done on the 2003 server.
</div>

<div>
Event Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Information 
Event Source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NtFrs 
Event Category: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;None 
Event ID: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;13516 
Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;12/27/2015 
Time: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;10:26:59 AM 
User: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N/A 
Computer: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FILE01 
Description: 
The File Replication Service is no longer preventing the computer DMEFILE01 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. 
&nbsp; 
Type &quot;net share&quot; to check for the SYSVOL share. 
 
For more information, see Help and Support Center at <a href="http://go.microsoft.com/fwlink/events.asp" rel="ugc">http://go.microsoft.com/fwlink/events.asp</a>.
</div>

<div>
Looks like youre getting some good progress there and the old DC may have been refusing to perform the initial replication to the new DC. 
 
Hows it looking now?
</div>

<div>
No update at this point: 
 
Log Name: &nbsp; &nbsp; &nbsp;File Replication Service 
Source: &nbsp; &nbsp; &nbsp; &nbsp;NtFrs 
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;12/27/2015 11:16:26 AM 
Event ID: &nbsp; &nbsp; &nbsp;13565 
Task Category: None 
Level: &nbsp; &nbsp; &nbsp; &nbsp; Warning 
Keywords: &nbsp; &nbsp; &nbsp;Classic 
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N/A 
Computer: &nbsp; &nbsp; &nbsp;AD-PDC.domian.local 
Description: 
File Replication Service is initializing the system volume with data from another domain controller. Computer AD-PDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. 
&nbsp; 
To check for the SYSVOL share, at the command prompt, type: 
net share 
&nbsp; 
When File Replication Service completes the initialization process, the SYSVOL share will appear. 
&nbsp; 
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
</div>

<div>
Any corresponding events on the other DC?
</div>

<div>
No events on the 2003 server, and no new logs on the 2008 server - this is the last log entry: 
 
Log Name: &nbsp; &nbsp; &nbsp;File Replication Service 
Source: &nbsp; &nbsp; &nbsp; &nbsp;NtFrs 
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;12/27/2015 11:16:26 AM 
Event ID: &nbsp; &nbsp; &nbsp;13565 
Task Category: None 
Level: &nbsp; &nbsp; &nbsp; &nbsp; Warning 
Keywords: &nbsp; &nbsp; &nbsp;Classic 
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N/A 
Computer: &nbsp; &nbsp; &nbsp;AD-PDC.domain.local 
Description: 
File Replication Service is initializing the system volume with data from another domain controller. Computer AD-PDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
</div>

<div>
This is an interesting event in the application log: 
 
&nbsp;Log Name: &nbsp; &nbsp; &nbsp;Application 
Source: &nbsp; &nbsp; &nbsp; &nbsp;Microsoft-Windows-EFS 
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;12/27/2015 1:15:31 PM 
Event ID: &nbsp; &nbsp; &nbsp;7002 
Task Category: None 
Level: &nbsp; &nbsp; &nbsp; &nbsp; Error 
Keywords: &nbsp; &nbsp; &nbsp; 
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Domain\Administrator 
Computer: &nbsp; &nbsp; &nbsp;AD-PDC.domian.local 
Description: 
Default group policy object cannot be created. Error 80070043 to open GPO Domain EFS Recovery Policy in domain LDAP://DC=domain,DC=local.
</div>

<div>
Coukd i please check, are you editing the fqdn on these posts? Some servers are listed with the suffix 'domain.local' and some with 'domian.local' fot example. 
Just checking if thats relavent or just a typo :-) 
 
Anyway, probably need to check some basics. Could you please check (and post on here) the following on BOTH DCs and compare the results to see uf we can find where theres an inconsistancy: 
 
Location of the AD objects for both servers. 
 
Object creation/modification dates for both AD objects. 
 
Check FSMO holders on both DCs. 
 
Check replication settings in AD sites &amp;&nbsp;services (open the 'site' and both servers should be listed. Open the 'server' and then &nbsp;open the 'ntds' folder to see connections between servers. 
 
Also, try creating an object in ad (a user for example) and see if it replicates to the other dc's version of AD. Probably worth trying in both directions.
</div>

<div>
Thanks Steve - Yes, I am editing the domain.local name prior to posting. I guess I have missed some. 
 
Both DC are listed in the same Domain Controllers OU, on both 2003 &amp;&nbsp;2008 
 
New user creation from 2008r2 replicated to 2003 - as well creation from 2003 replicated to 2008r2 
 
Both 2003 and 2008r2 report netdom query fsmo as all 5 roles being held by AD-PDC 
 
Net share looks better: NETLOGON and SYSVOL are now both listed. 
<a href="https://filedb.experts-exchange.com/incoming/2015/12_w01/1061349/2003svrprops.JPG" target="_blank" class="file-inline" title="2003 server properties in DC OU (28 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>2003svrprops.JPG</a> 
<a href="https://filedb.experts-exchange.com/incoming/2015/12_w01/1061350/2008r2svrprops.JPG" target="_blank" class="file-inline" title="2008 server properties in DC OU (30 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>2008r2svrprops.JPG</a>
</div>

2003svrprops.JPG

2008r2svrprops.JPG

<div>
I may have located an issue with an OU that referenced a dead/invalid replication partner that was located in a CoLo site - I have delete that OU and things are starting to roll. Will let it sit for a couple hours and see what come of it all.
</div>

<div>
Exchange is now seeing both DC's - which was the original issue I noticed 
 
Things appear to be getting better
</div>

<div>
Thanks for the assist Steve - Everything has settled in nicely and no new errors have popped up. 
 
Mark
</div>

<div>
<div class="content wysiwyg-content">
While working to upgrade out of a Svr2003 network, the first 2008r2 DC has been put online. 
 
The 2003 FSMO DC went through the /forestprep and /domainprep with zero issues and the domain is at 2003 function level. All FSMO roles have been transferred to the new 2008r2 DC (AD-PDC). While working on the upcoming changes for the last 2003 DC to be dcpromo'ed I noticed a lack of connection (netlogin) in Exchange that led to looking into DC functions via DCDIAG. 
 
Attached is a log of the DCDIAG /E test 
 
It has been suggested that I open this new question here to try and find the best result. 
 
I tried to re-run the /forestprep and /domainprep on the 2003 box - both returned nothing to be done...So, what is the best next step? 
 
Mark 
<a href="https://filedb.experts-exchange.com/incoming/2015/12_w52/1059861/dcdiagtest.txt" target="_blank" class="file-inline" title="DCDIAG test with errors (9 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>dcdiagtest.txt</a>
</div>
</div>

dcdiagtest.txt

While working to upgrade out of a Svr2003 network, the first 2008r2 DC has been put online.

The 2003 FSMO DC went through the /forestprep and /domainprep with zero issues and the domain is at 2003 function level. All FSMO roles have been transferred to the new 2008r2 DC (AD-PDC). While working on the upcoming changes for the last 2003 DC to be dcpromo'ed I noticed a lack of connection (netlogin) in Exchange that led to looking into DC functions via DCDIAG.

Attached is a log of the DCDIAG /E test

It has been suggested that I open this new question here to try and find the best result.

I tried to re-run the /forestprep and /domainprep on the 2003 box - both returned nothing to be done...So, what is the best next step?

Mark

DC Upgrade 2003 to 2008 r2 DCDIAG issues

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.