3. AD LDS is a hierarchical file- Uses the Extensible Storage
based directory store Engine (ESE) for file storage
ESE
AD LDS can be accessed via The store is organized into
LDAP three partitions types:
Configuration
Schema
Application
4. AD LDS Schema defines the types of objects and data that can be created and
stored in an AD LDS instance using object classes and attributes
Schema Partition Application Partition
Directory objects
Definition for an
based on the
automobile object
automobile object
class
class
Directory objects
Definition for a user
based on the user
object class
object class
5. An AD LDS Instance is a running copy of AD LDS service that contains is own
communication interface and directory store
A Single AD LDS Instance
Interfaces
Directory Service (LDAP,
replication)
Client
Directory Data
Store
(Adamntds.nit)
6. The AD LDS application partition holds the data that is used by the application
A Single AD LDS Instance
Application partition 1
Configuration partition
Schema partition
Multiple application directory partitions can be created in each LDS instance;
however each partition would share a single set of configuration and schema
partitions
7. AD LDS uses multimaster replication:
• All instances are writable
• Changes on one instance are replicated to the other instances
AD LDS servers
Client adds replicate changes Client modifies
“User 2” on to all servers “User 1” display
Server 1 name on Server 2
Server 1 Server 2
Server 3
8. Features AD LDS AD DS
Capable of multiple instances running
on one server
Runs on nondomain controllers
Does not require DNS infrastructure
Group policy
Global Catalog functions
Kerberos V5 Protocol authentication
Full-featured administrator tools
Automatic failover of services
