Site-to-Site Connectivity Scenario Essay

I am troubleshooting replication between the Main Office and Branch Office 1. It seems that changes to user object attributes take a very long time to propagate or do non propagate at all. I am not sure when replication is supposed to occur and contract no idea where to begin testing? Do you have any recommendations, any suggested steps to process me narrow down the riddle? Thank youJunior AdminGood morning Junior AdminIm sorry about the trouble you are having. Active Directory replication by default is pull earlier than push, meaning that replicas pull changes from the server where the change was effected. Because this is an Inter-site set up the replication traffic is difference to be higher. You can use Performance Monitor, Event Log, or Network Monitor to check how ofttimes traffic you are having. The time required to replicate directory data between domain controllers is known as the replication latency. Replication latency can vary depending on the number of domain cont rollers, the number of sites, the accessible bandwidth between sites, replication frequence, and more. Active Directory automatically builds the most efficient intersite replication topology using culture you provide through Active Directory Sites and Services about your site connections.The directory stores this nurture as site combine objects. One domain controller per site is assigned to build the topology this is called the intersite topology generator. The intersite replication topology is updated regularly to respond to any changes that occur in the network. You can control intersite replication through the information you provide when you create your site links. By monitoring replication regularly you will be subject to determine the normal replication latency on your network. With that information, you can easily determine if a problem is occurring.You can also manually force the replication byrunning repadmin /syncall /AdeP or use AD sites and services console. You c an adjust the frequency to match with your specific needs. Be aware that increasing this frequency increases the amount of bandwidth used by replication. I would also recommend that you run dcdiag /q and repadmin /replsum to check the health of DC and replication status in case if errors are reported post the logs. I hope this helps. allow me know if you have any other questions. IT Admin