Сводная информация о репликации active directory на вашу электронную почту или командам microsoft

In addition to checking the health of your domain controllers, it can also be used to force replication and pinpoint errors.

Active Directory replication is a critical service that keeps changes synchronized with other domain controllers in the forest.

Problems with replication can cause authentication failures and issues accessing network resources (files, printers, applications).

Below I’ll show you the step by step process with plenty of examples and the results.

Let’s do this.

The continuous monitoring of the health of all your critical IT systems is an essential requirement to help prevent system downtime and mitigate the damage associated with workplace server disruptions.

Monitoring the replication status of the Active Directory (AD) environment ensures that AD performance is optimized, and any errors are identified and fixed as soon as possible.

The network information for Active Directory is being constantly modified or updated. So, when information is updated on one domain controller (DC) of the AD network, all the other DCs in the network need to be updated with the new information. This is done in Active Directory through a process called replication.

The replication process ensures that all the controllers store the same set of information and are in sync with each other. Replication in Active Directory is independent of the forest, tree or domain structure.

Import-Module ActiveDirectory

get-command -module activedirectory -name *ADReplicat*

Get-ADReplicationFailure -Target DC1,DC2

Get-ADReplicationFailure -scope site -target {SITE} | FT Server, LastError, Partner-Auto

Get-ADReplicationFailure -Target "domen.com" -Scope Domain

​​​​​​​Get-ADDomainController -filter * | foreach {Sync-ADObject -Object "cn=Vasya Pupkin ,cn=Users,dc=domen,dc=com" -source DC1 -Destination $_.hostname}

Get-ADReplicationConnection -Filter {ReplicateToDirectoryServer -eq "DC1"}

Get-ADReplicationUpToDatenessVectorTable * | ft Partner,Server,UsnFilter

Methods to check Active Directory Replication

Using Repadmin to check Active Directory Replication

• From the Start menu, right click on CommandPrompt
• Click on Run as Administrator. This opens an elevated command prompt
• Run the ntdsutil command from the elevated command prompt

This command is used to provide the replication status within the Active Directory forest. It also displays the number of replication attempts with respect to the failures. It identifies the domain controllers that have failed replication (both inbound and outbound) and summarizes the results.

This command can be used to get the queue status of the domain controller. It displays the inbound replication requests that must be issued by the domain controller. The number of items in the queue is also displayed. A replication problem is indicated if the queue is very long. Using this command will highlight if there is a problem with replication or if the required replication has just been queued.

This command is used to force the immediate replication of a directory or schema partition from a source domain controller to a destination domain controller. It can be used to check the replication success after any suspected fault conditions are removed. As well as this, it can also be used to check the replication status between two domain controllers.

Here, DSA is used to specify the host name of the domain controller and the Naming Context is used to specify the distinguished name of the directory partition. The flags can be used to perform specific actions. Examples of some of the flags that can be used are:

• /a – Aborts if a server is unavailable.
• /A – Synchronizes all the naming contexts on the home server.
• /d – Identifies the servers by the distinguished names.
• /e – Synchronizes domain controllers across all sites.
• /h – Displays help.
• /i – Iterates indefinitely.
• /I – Runs the repadmin / showrepl command
• /s – Does not synchronize.

Checking Active Directory Replication using PowerShell

This is used to view the replication status information. It displays a replication report using the up-to-dateness vector table. This is maintained by every domain controller and helps keep track of the highest USN from each domain controller in the forest. There are several modifications of this command that can be used for specific purposes.

This command is used to obtain the replication metadata of a specific object in Active Directory.

This command can be used to replicate specific objects between two domain controllers that have partitions in common. However, they need not be direct replication partners.

This can be used to obtain a collection of data that can be used to describe a replication failure. It returns all the failures for a specific domain controller.

$ReplicationSummary = Get-WinADForestReplicationSummary -IncludeStatisticsVariable Statistics
$Body = EmailBody { EmailImage -Source 'https://evotec.xyz/wp-content/uploads/2021/04/Logo-evotec-bb.png' -UrlLink '' -AlternativeText 'Logo' -Width 181 -Heigh 57 -Inline EmailText -Text "Dear ", "AD Team," -LineBreak EmailText -Text "Upon reviewing the resuls of replication I've found: " EmailList { EmailListItem -Text "Servers with good replication: ", $($Statistics.Good) -Color Black, SpringGreen -FontWeight normal, bold EmailListItem -Text "Servers with replication failures: ", $($Statistics.Failures) -Color Black, Red -FontWeight normal, bold EmailListItem -Text "Servers with replication delta over 24 hours: ", $($Statistics.DeltaOver24Hours) -Color Black, Red -FontWeight normal, bold EmailListItem -Text "Servers with replication delta over 12 hours: ", $($Statistics.DeltaOver12Hours) -Color Black, Red -FontWeight normal, bold EmailListItem -Text "Servers with replication delta over 6 hours: ", $($Statistics.DeltaOver6Hours) -Color Black, Red -FontWeight normal, bold EmailListItem -Text "Servers with replication delta over 3 hours: ", $($Statistics.DeltaOver3Hours) -Color Black, Red -FontWeight normal, bold EmailListItem -Text "Servers with replication delta over 1 hour: ", $($Statistics.DeltaOver1Hours) -Color Black, Red -FontWeight normal, bold EmailListItem -Text "Unique replication errors: ", $($Statistics.UniqueErrors.Count) -Color Black, Red -FontWeight normal, bold } if ($Statistics.UniqueErrors.Count -gt 0) { EmailText -Text "Unique replication errors:" EmailList { foreach ($ErrorText in $Statistics.UniqueErrors) { EmailListItem -Text $ErrorText } } } else { EmailText -Text "It seems you're doing a great job! Keep it up! 😊" -LineBreak } EmailText -Text "For more details please check the table below:" EmailTable -DataTable $ReplicationSummary { EmailTableCondition -Inline -Name "Fail" -HighlightHeaders 'Fails', 'Total', 'PercentageError' -ComparisonType number -Operator gt 0 -BackgroundColor Salmon -FailBackgroundColor SpringGreen } -HideFooter EmailText -LineBreak EmailText -Text "Kind regards," EmailText -Text "Your automation friend"
}
$EmailSplat = @{ From = 'przemyslaw.klys@evotec.pl' To = 'przemyslaw.klys@evotec.pl' Body = $Body Priority = if ($Statistics.Failures -gt 0) { 'High' } else { 'Low' } Subject = 'Replication Results 💖' Verbose = $true WhatIf = $false MgGraph = $true
}
Connect-MgGraph
Send-EmailMessage @EmailSplat

New-AdaptiveCard -Uri $TeamsUri { New-AdaptiveColumnSet { New-AdaptiveColumn -Width auto { New-AdaptiveImage -Url "https://evotec.xyz/wp-content/uploads/2021/04/Logo-evotec-bb.png" -Size Large -Style default } New-AdaptiveColumn -Width stretch { New-AdaptiveTextBlock -Text "Replication Summary" -Weight Bolder -Wrap if ($Statistics.Failures -gt 0) { $Summary = "There are $($Statistics.Failures) servers with replication issues. Please take a look and fix ASAP." } else { $Summary = "All servers are in good shape. Keep up the good work!" } New-AdaptiveTextBlock -Text $Summary -Subtle -Spacing None -Wrap } } New-AdaptiveContainer { New-AdaptiveTextBlock -Text "ad.evotec.pl" -Size Medium -Wrap New-AdaptiveTextBlock -Text "" -Subtle -Spacing None -Wrap New-AdaptiveTextBlock -Text (Get-Date) } New-AdaptiveContainer { New-AdaptiveColumnSet { New-AdaptiveColumn { New-AdaptiveTextBlock -Text "▲ $($Statistics.Good) servers with good replication" -Color Good -Spacing None New-AdaptiveTextBlock -Text "▼ $($Statistics.Failures) servers with failing replication" -Color Attention -Spacing None } -Width Stretch New-AdaptiveColumn { New-AdaptiveFactSet { foreach ($Entry in $Statistics.GetEnumerator() | Select-Object -Skip 1 -Last 5) { New-AdaptiveFact -Title $Entry.Key -Value $Entry.Value } } } -Width Auto } } -Spacing None
} -FullWidth

Install-Module PSWriteHTML -Force -Verbose
Install-Module ADEssentials -Force -Verbose
# if you like emails
Install-Module Mailozaurr -Force -Verbose
# if you like teams
Install-Module PSTeams -Force -Verbose

Repadmin Examples

Example 1: Display the repadmin help menu

repadmin /?

 C:\Users\rallen>repadmin /?
Usage: repadmin [/u:{domain\user}] [/pw:{password|*}] [/retry[:][:]] [/csv]
Use these commands to see the help:
/? Displays a list of commands available for use in repadmin and their description.
/help Same as /?
/?: Displays the list of possible arguments , appropriate syntaxes and examples for the specified command .
/help: Same as /?:
/experthelp Displays a list of commands for use by advanced users only.
/listhelp Displays the variations of syntax available for the DSA_NAME, DSA_LIST, NCNAME and OBJ_LIST strings.
/oldhelp Displays a list of deprecated commands that still work but are no longer supported by Microsoft.
Supported commands (use /? for detailed help): /kcc Forces the KCC on targeted domain controller(s) to immediately recalculate its inbound replication topology. /prp This command allows an admin to view or modify the password replication policy for RODCs. /queue Displays inbound replication requests that the DC needs to issue to become consistent with its source replication partners. /replicate Triggers the immediate replication of the specified directory partition to the destination domain controller from the source DC. /replsingleobj Replicates a single object between any two domain controllers that have common directory partitions. /replsummary The replsummary operation quickly and concisely summarizes the replication state and relative health of a forest. /rodcpwdrepl Triggers replication of passwords for the specified user(s) from the source (Hub DC) to one or more Read Only DC's. /showattr Displays the attributes of an object. /showobjmeta Displays the replication metadata for a specified object stored in Active Directory, such as attribute ID, version number, originating and local Update Sequence Number (USN), and originating server's GUID and Date and Time stamp. /showrepl Displays the replication status when specified domain controller last attempted to inbound replicate Active Directory partitions. /showutdvec displays the highest committed Update Sequence Number (USN) that the targeted DC's copy of Active Directory shows as committed for itself and its transitive partners. /syncall Synchronizes a specified domain controller with all replication partners.
Supported additional parameters: /u: Specifies the domain and user name separated by a backslash {domain\user} that has permissions to perform operations in Active Directory. UPN logons not supported. /pw: Specifies the password for the user name entered with the /u parameter. /retry This parameter will cause repadmin to repeat its attempt to bind to the target dc should the first attempt fail with one of the following error status: 1722 / 0x6ba : "The RPC Server is unavailable" 1753 / 0x6d9 : "There are no more endpoints available from the endpoint mapper" /csv Used with /showrepl to output results in comma separated value format. See /csvhelp

Example 2: Summarize the replication status and view the overall health

The first command you should use is replsummary. This command will quickly show you the overall replication health. This command will show you the percentage of replication attempts that have failed as well as the largest replication deltas.

repadmin /replsummary

:\WINDOWS\system32>repadmin /replsummary
Replication Summary Start Time: 2018-03-13 04:44:54
Beginning data collection for replication summary, this may take awhile: .....
Source DSA largest delta fails/total %% error DC1 52m:48s 0 / 5 0 DC2 52m:46s 0 / 5 0
Destination DSA largest delta fails/total %% error DC1 52m:46s 0 / 5 0 DC2 52m:48s 0 / 5 0

Example 3:  Show replication partner and status

In addition, this command displays the GUID of each object that was replicated and its result. This is helpful to identify what objects are failing to replicate.

repadmin /showrepl

C:\Users\rallen>repadmin /showrepl
Repadmin: running command /showrepl against full DC dc1.ad.activedirectorypro.com
Default-First-Site-Name\DC1
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: a4d22a63-1918-492a-bcd6-7fe286941e72
DSA invocationID: a4d22a63-1918-492a-bcd6-7fe286941e72
==== INBOUND NEIGHBORS ======================================
DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-13 03:52:08 was successful.
CN=Configuration,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-13 03:52:08 was successful.
CN=Schema,CN=Configuration,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-13 03:52:08 was successful.
DC=DomainDnsZones,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-13 03:52:08 was successful.
DC=ForestDnsZones,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-13 03:52:08 was successful.

Example 4: Show replication partner for a specific domain controller

If you want to see the replication status for a specific domain controller use this command.

replace <ServerName> with the name of your domain controller.

repadmin /showrepl <ServerName>

C:\WINDOWS\system32>repadmin /showrepl dc2
Default-First-Site-Name\DC2
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408
DSA invocationID: 2eb95693-bfa7-4f3f-b52c-139737aa883f
==== INBOUND NEIGHBORS ======================================
DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUID: a4d22a63-1918-492a-bcd6-7fe286941e72 Last attempt @ 2018-03-14 04:21:02 was successful.
CN=Configuration,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUID: a4d22a63-1918-492a-bcd6-7fe286941e72 Last attempt @ 2018-03-14 03:52:07 was successful.
CN=Schema,CN=Configuration,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUID: a4d22a63-1918-492a-bcd6-7fe286941e72 Last attempt @ 2018-03-14 03:52:07 was successful.
DC=DomainDnsZones,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUID: a4d22a63-1918-492a-bcd6-7fe286941e72 Last attempt @ 2018-03-14 03:52:07 was successful.
DC=ForestDnsZones,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUID: a4d22a63-1918-492a-bcd6-7fe286941e72 Last attempt @ 2018-03-14 03:52:07 was successful.

Example 5: Show only Replication Errors

The showrepl command can output a lot of information. If you want to see only the errors use this command. In this example, DC2 is down, you can see the results are all errors from DC2.

C:\WINDOWS\system32>repadmin /showrepl /errorsonly
Repadmin: running command /showrepl against full DC dc1.ad.activedirectorypro.com
Default-First-Site-Name\DC1
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: a4d22a63-1918-492a-bcd6-7fe286941e72
DSA invocationID: a4d22a63-1918-492a-bcd6-7fe286941e72
==== INBOUND NEIGHBORS ======================================
DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-15 04:19:38 failed, result 8524 (0x214c): The DSA operation is unable to proceed because of a DNS lookup failure. 1 consecutive failure(s). Last success @ 2018-03-14 07:52:08.
CN=Configuration,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-15 04:19:38 failed, result 8524 (0x214c): The DSA operation is unable to proceed because of a DNS lookup failure. 1 consecutive failure(s). Last success @ 2018-03-14 07:52:08.
CN=Schema,CN=Configuration,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-15 04:19:38 failed, result 8524 (0x214c): The DSA operation is unable to proceed because of a DNS lookup failure. 1 consecutive failure(s). Last success @ 2018-03-14 07:52:08.
DC=DomainDnsZones,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-15 04:19:38 failed, result 8524 (0x214c): The DSA operation is unable to proceed because of a DNS lookup failure. 1 consecutive failure(s). Last success @ 2018-03-14 07:52:08.
DC=ForestDnsZones,DC=ad,DC=activedirectorypro,DC=com Default-First-Site-Name\DC2 via RPC DSA object GUID: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408 Last attempt @ 2018-03-15 04:19:38 failed, result 8524 (0x214c): The DSA operation is unable to proceed because of a DNS lookup failure. 1 consecutive failure(s). Last success @ 2018-03-14 07:52:08.
Source: Default-First-Site-Name\DC2
******* 1 CONSECUTIVE FAILURES since 2018-03-14 07:52:08
Last error: 8524 (0x214c): The DSA operation is unable to proceed because of a DNS lookup failure.

Example 6: Show replication Queue

It is normal to see items in the queue. If you have a small environment it will often be at zero because there are few replications that occur. If you notice items sitting in the queue and they never clear out, you have a problem.

Use this command to view the replication queue

Repadmin /Queue

C:\Users\rallen>repadmin /queue
Repadmin: running command /queue against full DC dc1.ad.activedirectorypro.com
Queue contains 0 items.

Example 7: How to Force Active Directory Replication

This will do a pull replication, which means it will pull updates from DC2 to DC1.

repadmin /syncall dc1 /Aed

If you want to push replication you will use the /P switch. For example if you make changes on DC1 and want to replicate those to other DCs use this command.

repadmin /syncall dc1 /APed

C:\WINDOWS\system32>repadmin /syncall dc1 /Aed
Syncing all NC's held on dc1.
Syncing partition: DC=ForestDnsZones,DC=ad,DC=activedirectorypro,DC=com
CALLBACK MESSAGE: The following replication is in progress: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: The following replication completed successfully: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.
Syncing partition: DC=DomainDnsZones,DC=ad,DC=activedirectorypro,DC=com
CALLBACK MESSAGE: The following replication is in progress: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: The following replication completed successfully: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.
Syncing partition: CN=Schema,CN=Configuration,DC=ad,DC=activedirectorypro,DC=com
CALLBACK MESSAGE: The following replication is in progress: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: The following replication completed successfully: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.
Syncing partition: CN=Configuration,DC=ad,DC=activedirectorypro,DC=com
CALLBACK MESSAGE: The following replication is in progress: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: The following replication completed successfully: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.
Syncing partition: DC=ad,DC=activedirectorypro,DC=com
CALLBACK MESSAGE: The following replication is in progress: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: The following replication completed successfully: From: 57a1cfbc-88bb-41da-a1a6-f14f5c9df408._msdcs.ad.activedirectorypro.com To : a4d22a63-1918-492a-bcd6-7fe286941e72._msdcs.ad.activedirectorypro.com
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.

Example 8: Export results to text file

Sometimes these commands can display a lot of information. You can export any of the examples above to a text file, this makes it a little easier to review at a later time or save for documentation.

just add > c:\destination folder\filename.txt to the end of any of the commands

Here are a few examples

repadmin /replsummary > c:\it\replsummary.txt

repadmin /showrepl > c:\it\showrepl.txt

How Lepide Helps with AD Health Monitoring

An alternative, more straightforward method of checking Active Directory replication status is to use the Health Monitoring dashboard within the Lepide Data Security Platform.

The Active Directory Health Check is an integrated feature of the Lepide Solution. It provides a simple and powerful means of keeping track of important elements of your Active Directory to ensure the continuity and health of the AD environment. It provides continuous monitoring and real-time alerts for NT Directory services, DNS Servers, Disk space, CPU, and memory along with service and replication activity.

To display the Lepide dashboard, click the Health Monitoring icon.

The example below shows the Health Monitoring dashboard including replication status:

The twelve elements which are monitored on the Health Monitoring dashboard are:

1. ­Server Availability
2. ­CPU and Memory Usage
3. Active Directory Services
4. ­ESENT Database Performance
5. ­Active Directory Web Services
6. ­DFSR Replicated Folders
7. ­Replication Status
8. ­LDAP Status
9. ­Address Book Status
10. ­Directory Service Status
11. NTDS Performance Counters
12. ­DNS Performance Counters

Types of Active Directory Replication

1. Intra-site Replication: As the name suggests, intra-site replication takes place between domain controllers within the same site. This process is quite straightforward and despite the number of domain controllers, any directory update will be replicated in less than a minute. This replication is performed within a site by means of the ring topology and does not need to be configured manually as it occurs automatically within the site.

2. Inter-site Replication: If Active Directory infrastructure contains more than one site, when a change happens to a domain controller in one site this change needs to be replicated to domain controllers in other sites. This is known as inter-site replication. This type of replication takes place by means of site links and also utilizes the ring topology, but it is different to the intra-site replication. Inter-site replication occurs between two domain controllers called bridgeheads. At least one domain controller within a site is assigned the role of bridgehead. In contrast to the intra-site replication, this inter-site replication must be configured and does not occur automatically.

More examples

Find the last time your DC was backed up

Repadmin /showbackup *

Displays calls that have not yet been answered

repadmin /showoutcalls *

List the Topology information

repadmin /bridgeheads * /verbose

Inter Site Topology Generator Report

repadmin /istg * /verbose

Conclusion

I hope you found this guide useful. If you have any questions leave a comment below. If you liked this article, check out: How to Use NSLookup to Check DNS Records.

Похожее:

Как открыть файл или папку с помощью командной подсказки или power shell в windows 11 В powershell 5 1 как переходить предупреждения из команды удаленного вызова Не перечислять файлы и папки в azure file share Проверьте, что пользовательская лицензия microsoft 365 назначена непосредственно или наследована от группы