Monday, December 1, 2014

Triggering Manual Replication in Active Directory

Hi Guys this post let you how to trigger the manual replication in Active Directory…
So we all know in Active directory replication is very important without replication data will not be sync throughout the AD environment.  When  you troubleshooting AD replication issue, you may wish to manually force replication between two domain controllers in an attempt to correct any inconsistencies or errors that you have found. You may also wish to force replication to occur when you make changes, such as disabling user accounts that you wish to replicate immediately throughout the enterprise without waiting for the next replication interval.
 
In this kind of scenario you can Force Manual Replication, below are the steps you can perform so before going force manual replication you should log on to the domain controller or an administrator workstation that has the Active Directory Administrative Tools installed.
 
Steps:
1.Start---> Run--->  in the Run box you can type dssite.msc then hit enter you will see Active Directory sites and Services (This is shortcut)    or   Click Start--->     Administrative Tools ---> Active Directory Sites and Services will open.
2.Expand the Sites, followed by the site that contains the connection for which you wish to force replication.
3.Locate the server in the Servers container that provides the connection object.
4.Click NTDS Settings in the console tree.
5.In the details pane, right-click the connection for which you want replication to occur and Select Replicate Now

Now you can log in to the remote site DC to check the replication weather that accounts are replicated or not. If changes are replicated successfully then there is no problem at all in your environment, If changes are not replicated then you need to troubleshoot the error based on the event logs, take the DC Diag, check the DNS connectivity, check the FRS, check ADDS services, Need to check Sysvol and netlogon shares and dependent Services. Once you correct the error it should work otherwise there is a problem in environment.
 
Note : When you manually replicating you should not see the errors or warnings if you see any errors or warnings  it seems there is problem with remote site connection or remote site Domain controller problem, The connection object must be pingable and name resolution has to be resolve. Otherwise manual replication will not allow you to replicate. In the step no.5 when you select replicate now it will not replicate it will pop with errors message, if everything is good then it will pop with successful message. When you troubleshoot this kind of problems the major thing you need to check DNS connectivity, Site links and DC status with DC Diag tool.  If you not able to troubleshoot the problem let me know guys I will help you to correct the problem. We have command line tool to trigger the force replication also that will discuss in the next post. Guys let me know if you have any questions or comments on this post.
 

2 comments:

Unknown said...

Great job I am fully understand

Unknown said...

Great information