Active Directory Domain Services uses pull replication to replicate Active Directory Partitions. This means that the Domain Controller on which replication is started receives the data from the source Domain Controller. It’s like a one way ticket.
If you want to replicate all Domain Controllers, then you have to start replication on each of them separately. This may take a while. To save time, I am going to show you a PowerShell One-Liner to force replication on all Domain Controllers of all Active Directory Sites. Let’s take a look at this One-Liner now.
Force Replication of all Domain Controllers on all Sites
Suppose, you have one Domain with multiple sites. (One Forest and one Forest Root Domain).
Log on to one of your Domain Controllers. Start Windows PowerShell with administrative privileges. The domain name and the domain partition don’t need to be specified. They will be filled automatically by Get-ADDomain. 😉
function Replicate-AllDomainController {
(Get-ADDomainController -Filter *).Name | Foreach-Object {repadmin /syncall $_ (Get-ADDomain).DistinguishedName /e /A | Out-Null}; Start-Sleep 10; Get-ADReplicationPartnerMetadata -Target "$env:userdnsdomain" -Scope Domain | Select-Object Server, LastReplicationSuccess
}
Once completed, you get a nice overview with the computer names of the Domain Controllers and the time of the Last Replication Success.
That’s it.
Have fun replicating your DC’s! More about repadmin here:
https://technet.microsoft.com/en-us/library/cc835086(v=ws.11).aspx
See also
PowerShell: Adding Active Directory Users from Text Files (Bulk)
Windows Server 2016: Configuring Time based Group Membership with PowerShell
PowerShell: Changing Active Directory user logon names (Bulk)
Categories: PowerShell, Windows Server
Thank you for this, simple and efficient
LikeLiked by 1 person
Would be very helpful if you could explain what these powershell-snippets actually do. Such one-liners are often a little hard to read.
LikeLike
You only have to pay attention to the first two lines. Get-ADDomainController receives the Names of all DCs. This names are then piped to Foreach-Object that runs repadmin on all of them with no ouput (Out-Null). Then the script goes to sleep for 10 seconds. Afterwards ReplicationData from all DCs are retreived to view the replication status.
For some it’s hard to read for others not. I love it.
But yes, in complex scripts it’s more useful to use the common script struture.
LikeLike
Thanks. Why is the “Start-Sleep 10” needed?
LikeLike
The purpose of Start-Sleep is to wait a few seconds. You can skip that. It’s just to make sure that Get-ADReplicationMetaData gets the recent results.
LikeLike
Hello Patrick,
Simplicity is the key.
Great article.
LikeLike