Bạn đang xem bản rút gọn của tài liệu. Xem và tải ngay bản đầy đủ của tài liệu tại đây (790.32 KB, 35 trang )
<span class='text_page_counter'>(1)</span><div class='page_container' data-page=1></div>
<span class='text_page_counter'>(2)</span><div class='page_container' data-page=2>
• Overview of Active Directory Domain Services Replication
• Overview of AD DS Sites and Replication
• How Active Directory Replication Works
• How AD DS Replication Works Within a Site
• Resolving Replication Conflicts
• Optimizing Replication
• What Are Directory Partitions?
• What Is Replication Topology?
• How Directory Partitions and the Global Catalog
Are Replicated
• How the Replication Topology Is Generated
• Uses a multimaster model
• Uses pull replication
• Uses store and forward replication
• Uses loose consistency with convergence
• Addition of an object to Active Directory
• Modification of an object’s attribute values
• Domain controllers notify replication partners when
updates are applied
• For normal updates, the change notification happens
15 seconds after the change is applied
• Notifications for security related changes are
sent immediately
In a multimaster replication model, replication conflicts can
arise when:
• The same attribute is changed on two domain controllers
simultaneously
• An object is moved or added to a deleted container on
another domain controller
• Two objects with the same relative distinguished name are
added to the same container on two different domain controllers
To resolve replication conflicts, AD DS uses:
• In a multimaster replication model, AD DS updates
can be replicated using multiple paths
• AD DS uses update sequence numbers, high watermarks,
and up-to-dateness vectors to ensure that updates
Definitions and rules for
creating and manipulating
objects and attributes
Information about the
Active Directory structure
Information about
domain-specific objects
Information about
applications
Domain A Topology
<b>Domain controllers in </b>
<b>the same domain</b>
<b>Domain controllers in </b>
<b>the same domain</b>
<b>A1</b> <b>A2</b>
<b>A3</b> <b>A4</b>
Domain A Topology
Domain B Topology
<b>A1</b> <b>A2</b>
<b>A3</b> <b>A4</b>
<b>B1</b>
<b>B2</b>
<b>B3</b>
<b>Domain controllers </b>
<b>from various domains</b>
Domain A topology
Domain B topology
Schema and configuration
topology
Global catalog replication
<b>A1</b> <b>A2</b>
<b>Domain controllers </b>
<b>from various domains</b>
•<b> </b>Each domain controller has two replication partners
for each Active Directory partition
• The KCC creates two one-way connection objects
between replication partners to ensure that no two domain
controllers are ever more than three network hops away
• When a new domain controller is added to a site,
the KCC recalculates connection objects
• Connection objects can replicate one or more partitions
In this demonstration, you will see how to create
• What Are AD DS Sites and Site Links?
• Discussion: Why Implement Additional Sites?
• Demonstration: Configuring AD DS Sites
• How Replication Works Between Sites
• Comparing Replication Within Sites and Between Sites
• Demonstration: Configuring AD DS Site Links
• What Is the Inter-site Topology Generator?
• <b>Identify network </b>
<b>locations with fast </b>
<b>reliable network </b>
<b>connections</b>
• Why would an organization choose to implement
additional sites?
• Create sites and subnets
<b>Site</b>
<b>A1</b>
<b>A2</b>
<b>Site Link</b>
<b>Site Link</b>
<b>Site</b>
<b>B3</b>
<b>B1</b> <b>B2</b>
<b>You can configure:</b>
• <b>Replication paths </b>
<b>between sites</b>
• <b>Replication schedules</b>
<b>and frequency </b>
• <b>Replication protocols</b>
<b>Replication Within Sites:</b>
Assumes fast and highly
reliable network links
Does not compress
replication traffic
Uses a change notification
<b>Replication Between Sites:</b>
Assumes limited available
bandwidth and unreliable
network links
Compresses all replication
traffic between sites
• Configure the default site link
• Create additional site links
<b>Inter-site topology generator</b>
<b>Inter-site topology generator</b>
• <b>The inter-site </b>
<b>topology generator </b>
<b>defines the </b>
<b>replication between </b>
<b>sites on a network </b>
<b>Inter-site topology</b>
<b>generator</b>
• <b>Unidirectional replication </b>
<b>ensures that changes to a </b>
<b>read-only domain </b>
• What Is a Bridgehead Server?
• Demonstration: Configuring Bridgehead Servers
• Demonstration: Configuring Replication Availability
and Scheduling
• What Is Site Link Bridging?
• Demonstration: Modifying Site Link Bridges
• What Is Universal Group Membership Caching?
• Demonstration: Configuring Universal Group
Membership Caching
<b>A bridgehead server:</b>
• <b>Sends and receives </b>
<b>replicated data</b>
• <b>Is designated for </b>
<b>each partition in </b>
<b>the site</b>
<b>IP Subnet</b>
<b>IP Subnet</b>
<b>IP Subnet</b>
<b>IP Subnet</b> <b>Bridgehead ServerBridgehead Server</b>
<b>Site Link Bridge</b>
<b>Site Link Bridge</b>
<b>B2</b>
<b>Site Link BC</b>
<b>Site Link BC</b>
<b>Site Link AB</b>
<b>Site Link AB</b>
<b>B1</b>
<b>B3</b>
<b>C2</b>
<b>C1</b>
• Disable site link bridging
<b>Global Catalog Server</b>
<b>Global Catalog Server</b>
• <b>Enables domain </b>
<b>controllers in a site </b>
<b>with no global </b>
<b>catalog servers to </b>
<b>cache universal </b>
In this demonstration, you will see how to:
• Configure universal group membership caching for a site
In this demonstration you will see how to:
• Identify the domain controller holding the ISTG role
• Force the KCC to run, and how to force replication
• Exercise 1: Configuring AD DS Sites and Subnets
• Exercise 2: Configuring AD DS Replication
• Exercise 3: Monitoring AD DS Replication
Logon information
Virtual machine <b>NYC-DC1, LON-DC1, MIA-RODC,</b>
<b>NYC-RAS</b>
User name <b>Administrator</b>
Password <b>Pa$$w0rd</b>
• What additional changes would you need to make to the
AD DS site configuration if you needed to ensure that all
replication traffic in the New-York site passed through
NYC-DC2?
• What additional changes would you need to make if you
implemented another WAN connection between Tokyo and
London, and wanted to use that WAN connection for AD
DS replication instead of routing all replication changes
through NewYork-Site?
• Review questions
• Considerations for configuring AD DS sites and replication
• Beta feedback tool helps:
Collect student roster information, module feedback, and
course evaluations.
Identify and sort the changes that students request, thereby
facilitating a quick team triage.
Save data to a database in SQL Server that you can later
query.
• <b>Overall flow of module:</b>
Which topics did you think flowed smoothly, from topic to
topic?
Was something taught out of order?
• <b>Pacing:</b>
Were you able to keep up? Are there any places where the
pace felt too slow?
Were you able to process what the instructor said before
moving on to next topic?
Did you have ample time to reflect on what you learned? Did
you have time to formulate and ask questions?
• <b>Learner activities:</b>
Which demos helped you learn the most? Why do you think
that is?
Did the lab help you synthesize the content in the module?
Did it help you to understand how you can use this
knowledge in your work environment?
Were there any discussion questions or reflection questions
that really made you think? Were there questions you