AD概述及客户端常见问题.pptVIP

Think of Inter-Site Replication in Layers. Each of these is configured differently and are mostly independent, but all have interrelationships that affect the other layers. This is a conceptual model only and does not physically exist. 1. Phyxical Network - This assumes a well routed, well connected WAN. 2. Site Model. Sites, Site Links, Connections, link costs, subnets, site servers and transports are used to build a site topology that closely represents or models the actual physical network. This is up to the administrator and depends on his/her knowledge to build an accurate model. 3. Domain Structure - this is the structure of Parent/child domains in the enterprise - Domains, OUs, users, groups, etc. Remember this is a naming context that behaves somewhat differently in the site model than the Configuration or Schema NC (will see how later). Each DC stores a writeable copy of the active directory database AD Database is stored in one physical file – NTDS.DIT Made up of 3 logical partition replicas – Schema, Configuration Domain Schema – class and attribute definition for the forest Configuration – replication configuration, sites, topologies…etc for the forest Domain – all the objects stored by the domain – 1 domain partition for each domain in the forest Schema Configuration = Forest-wide, Domain = Domain-specific Each DC will store a full replica of the schema, configuration as well as the domain that it belongs to Global Catalogue server – full replica + partial replica of all other domains in the forest Partial replica – subset of attributes, read-only Replicas are also know as Naming Context or NC RPC – synchronous, SMTP – asynchronous Within site – always use RPC over IP Between sites, either RPC over IP or SMTP over IP SMTP is only supported for DC of different domains If domain spans sites, synchronous RPC must be available RID Pool Allocation - one domain controller is responsible for assigning “pools” of relative Ids to other domain controll