Choice of two useful Tools to monitor AD replication.

• First is Active Directory Replication Status Tool.
• Second is REPADMIN.

> Examples below are run in an AD Forest named “Contoso.ca”, composed of 1 domain and 2 DCs (GC2K7 and E2010) with no errors.

Repadmin gives something similar to:

PS C:\Users\Administrator> repadmin /showrepl * /csv

showrepl_COLUMNS,Destination DSA Site,Destination DSA,Naming Context,Source DSA Site,Source DSA,Transport Type,Number of

Failures,Last Failure Time,Last Success Time,Last Failure Status

showrepl_INFO,SITE1,GC2K7,"DC=Contoso,DC=ca",SITE1,E2010,RPC,0,0,2013-09-23 11:48:03,0

showrepl_INFO,SITE1,GC2K7,"CN=Configuration,DC=Contoso,DC=ca",SITE1,E2010,RPC,0,0,2013-09-23 11:48:03,0

showrepl_INFO,SITE1,GC2K7,"CN=Schema,CN=Configuration,DC=Contoso,DC=ca",SITE1,E2010,RPC,0,0,2013-09-23 11:48:03,0

showrepl_INFO,SITE1,GC2K7,"DC=DomainDnsZones,DC=Contoso,DC=ca",SITE1,E2010,RPC,0,0,2013-09-23 11:59:12,0

showrepl_INFO,SITE1,GC2K7,"DC=ForestDnsZones,DC=Contoso,DC=ca",SITE1,E2010,RPC,0,0,2013-09-23 11:48:03,0

showrepl_INFO,SITE1,E2010,"DC=Contoso,DC=ca",SITE1,GC2K7,RPC,0,0,2013-09-23 12:01:53,0

showrepl_INFO,SITE1,E2010,"CN=Configuration,DC=Contoso,DC=ca",SITE1,GC2K7,RPC,0,0,2013-09-23 11:57:33,0

showrepl_INFO,SITE1,E2010,"CN=Schema,CN=Configuration,DC=Contoso,DC=ca",SITE1,GC2K7,RPC,0,0,2013-09-23 11:57:33,0

showrepl_INFO,SITE1,E2010,"DC=DomainDnsZones,DC=Contoso,DC=ca",SITE1,GC2K7,RPC,0,0,2013-09-23 11:59:27,0

showrepl_INFO,SITE1,E2010,"DC=ForestDnsZones,DC=Contoso,DC=ca",SITE1,GC2K7,RPC,0,0,2013-09-23 11:57:33,0

ADRST gives the following :

Exportable as an Excel table as well:

Sam.

Just a reminder for me (Extrace.exe is an internal tool used for deep debugging).

extrace.exe -c -v ExchangeDebugTraces.etl >TraceOut.csv

We have to use the Microsoft.Exchange.Diagnostics.dll matching the Exchange build where the trace come from. To check your Exchange server build, checkout the following link:

http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx

Sam.

First, as my colleague Rhoderick wrote in a nice and easy-to-read “Troubleshooting Content Indexing” article, we can use the Troubleshoot-CI.ps1 script to try detect other potential issues such as deadlocks (threads blocked and search is waiting on these to continue to index), corruption (not likely here as the state is “Healthy” for the indexes), stall (usually a one time issue that a restart of the Exchange Search service solves), backlog.

In case the above troubleshooter is not identifying any issues, we can proceed to the below steps.

First, check that any File-Level anti-virus exclude the scan of any Exchange Index files (as well as DB files, and other Exchange files).

Then, rebuild the symbolic links for each language that the SP may have striped out, and reset the index:

-> Open Exchange Management Shell by right-clicking the shortcut and selecting “Run as Administrator”.

-> Navigate to the Scripts folder from Exchange Management Shell.

-> Run the command, ".\Repair-ExchangeSearchSymlinks.ps1" and check that it is completing successfully.

-> Run the command, ".\ResetSearchIndex.ps1 -force "Mailbox Database" and check that it’s completing successfully.

Then disable TCP Chimney, RSS and NetDMA that may be a cause for this issue as well

-> Open Command Prompt and run the following NetSH commands:

Disable TCP Chimney (the functionnality to offload the network packet processing from the CPU to the Network Card)
=> netsh int tcp set global chimney=disabled

Disable RSS
=> netsh int tcp set global rss=disabled

Disable NetDMA (Network Direct Memory Access)
=> Opened Registry Editor and navigated to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
=> Right click Parameters and add a new DWORD (32-bit) EnableTCPA and set the value to 0.

Information for TCP, RSS, NetDMA/EnableTCPA can be found on http://support.microsoft.com/kb/951037/en-us

Optionnally, you can also disable IPV6 as well:
=> Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
=> Right click Parameters and add a new DWORD (32-bit) DisabledComponents and set the value to 0xffffffff in Hexadecimal.

More information on http://technet.microsoft.com/en-us/network/cc987595.aspx

Finally, reboot the Exchange server to apply the above changes.

I recommend you test this procedure on a Lab first to get familiar with it, and to validate it in your environment before implementing these into production.

Sam.