![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello S Siva1,
Thank you for posting in Microsoft Community forum.
To stop replication from a restored server to other servers, and to ensure that only the Primary Domain Controller (PDC) server replicates to the restored server, you can follow these steps. Please note that these steps are general guidelines and might need to be adjusted based on your specific environment and server setup.
- Stop Replication from the Restored Server:
Log into the restored server.
Open the Command Prompt with administrative privileges.
Disable the replication by using the following command:
repadmin /options <RestoredServerName> +DISABLE_OUTBOUND_REPL
This will prevent the restored server from sending out replication updates to other servers.
We have two connection fields: "Replicate From" and "Replicate To"; we also have two ways to block replication: Inbound and Outbound. We're going to disable Outbound replication on the "Replicate From" servers and disable Inbound replication on the "Replicate To" servers.
We can do this remotely using repadmin:
repadmin /options <Replicate From> +DISABLE_OUTBOUND_REPL
repadmin /options <Replicate To> +DISABLE_INBOUND_REPL
For more information, please refer to the link below (I think the article is better to understand).
Turn on that Scary DC - Microsoft Community Hub
Note: Please test first in lab, and if it works, then you can run the command in production environment.
Before you stop replication from the Restored Server, please make sure PDC can connect to Restored Server (know your AD replication topology in the domain).
2.Ensure Replication from PDC to Restored Server:
On the PDC server, ensure that the replication is directed to the restored server.
Open the Command Prompt with administrative privileges on the PDC.
Use the following command to check the replication status: repadmin /showrepl
Identify the PDC and restored server in the replication list.
If needed, force replication from the PDC to the restored server using the following command: repadmin /syncall <PDCServerName> <RestoredServerName>
Q: and only need to replicate the pdc server to restored server.
A: If your AD replication topology is like this: Restored DC->PDC->DC->DC, maybe only the pdc server can replicate to restored server.
If your AD replication topology is like others, maybe not only the pdc server replicate to restored server, also other DCs can replicate to restored server.
3.Monitor Replication:
Ensure no other servers are replicating to the restored server unless necessary.
Monitor Event Viewer on both PDC and restored server for any replication errors or warnings.
4.Verify Configuration:
Open Active Directory Sites and Services.
Verify the connection objects and ensure that the replication topology reflects your desired replication flow.
5.Testing:
Make sure to test the setup by creating objects on the PDC and verifying that they replicate correctly to the restored server. Please note that these steps are for Windows Server environments.
If you have a different setup or use different systems, the steps might differ. Always ensure that you have backup copies of your critical data before making changes to the replication configuration.
I hope the information above is helpful.
If you have any question or concern, please feel free to let us know.
Best Regards,
Daisy Zhou