This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
You're performing an over-the-wire promotion of a new Windows Server 2025 domain controller and want the destination DC to converge the domain naming context from one specific partner ahead of its peers. How do you apply Replication Priority Boost?
On the destination DC, write the setPriorityBoost RootDSE modifier using the form <naming context>:<partner DC GUID>:<boost factor>.
setPriorityBoost
<naming context>:<partner DC GUID>:<boost factor>
On the source DC, lower the site link cost so the partner becomes the least-cost route.
Raise the forest functional level to Windows Server 2025 to unlock per-partner priority.
After you deploy Windows Server 2025 domain controllers, a legacy application that located DCs through NetBIOS mailslot broadcasts can no longer find one. What is the most likely cause?
The BlockNetBIOSDiscovery policy is enabled by default, so DC Locator uses DNS-based discovery only, with no NetBIOS fallback.
BlockNetBIOSDiscovery
The application's subnet was added to the wrong site link.
The configuration naming context hasn't replicated the application's connection object yet.
A destination DC sends its up-to-dateness vector (UTDVEC) to a source DC at the start of a replication cycle. What does the source DC use it for?
To skip changes the destination has already received by another replication path, providing propagation dampening.
To resume from the highest USN the destination previously received from that one source partner.
To decide whether to compress the replication payload for the WAN.
With Bridge All Site Links enabled, how does the KCC combine site link properties along the transitive path NewYork to Chicago to Denver?
Costs are added, the replication interval is the maximum of the links, and options are combined with a bitwise AND.
Costs are averaged, the interval is the minimum, and the schedule is the union of the link schedules.
Only the properties of the highest-cost link apply end to end.
A domain controller is brought back online after being disconnected for longer than the tombstone lifetime. Why can this reintroduce lingering objects?
It still holds objects that were deleted and garbage-collected on other DCs, and its metadata predates the partners' up-to-dateness vectors.
Its invocation ID was reset, so partners ignore all of its updates.
The KCC rebuilds every connection object, which duplicates the domain naming context.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?