Active Directory Partition Created by –

Satish Pandey
*The active directory database is logically separated into 4 partition.
1.Schema Partition 2.Domain Naming Partition
3.Configuration Partition 4.Application Partition
*Each partition is a unit of replication.
*Each partition has its own replication topology.
*Replication occurs between replicas of directory partition.
*Minimum two directory partitions are common among all domain controllers in the same forest.
The schema partition and
The configuration partitions
*All domain controllers which are in the same domain, in addition, share a common domain partition.
Schema Partition-
Only one schema partition exists per forest. The schema partition is stored on all domain controllers in a
forest. The schema partition contains definitions of all objects and attributes that you can create in the
directory, and the rules for creating and manipulating them. Schema information is replicated to all
domain controllers in the attribute definitions.
Domain Naming Partition-
Many domain partitions can exist per forest. Domain partitions are stored on each domain controller in a
given domain. A domain partition contains information about users, groups, computers and
organizational units. The domain partition is replicated to all domain controllers of that domain. All
objects in every domain partition in a forest are stored in the global catalog with only a subset of their
attribute values.
Configuration Partition-
There is only one configuration partition per forest. Second on all domain controllers in a forest, the
configuration partition contains information about the forest-wide active directory structure including
what domains and sites exist, which domain controllers exist in each forest, and which services are
available. Configuration information is replicated to all domain controllers in a forest.
Application Partition- Continue……..
Application partitions store information about application in Active Directory. Each application
determines how it stores, categorizes, and uses application specific information. To prevent
unnecessary replication to specific application partitions, you can designate which domain controllers
in a forest host specific application partitions. Unlike a domain partitions, an application partition
cannot store security principal objects, such as user accounts. In addition, the data in an application
partition is not stored in the global catalog.
Example of Application Partition:
If you use a Domain Name System (DNS) that is integrated with Active Directory you
have two application partitions for DNS zones.
1. Forest DNS Zones 2. Domain DNS Zones
Forest DNS Zone-
Forest DNS Zones is part of a forest. All domain controllers and DNS servers in a forest
receive a replica of this partition. A forest-wide application partition stores the forest zone
data.
Domain DNS Zone-
Domain DNS Zones is unique for each domain. All domain controllers that are DNS servers
in that domain receive a replica of this partition. The application partitions store the domain
DNS zone in the Domain DNS Zones<domain name>.
Each domain has a Domain DNS Zones partition, but there is only one Forest DNS Zones partition. No
DNS data is replicated to the global catalog server.
Stand For- Active Directory Services Interface (ADSI)
Application programming interface (API).
Lightweight Directory Interface Format (LDIF)

Through Command Line View-

C:\>ntdsutil
ntdsutil : domain management
domain management : connection
server connection : connect to server iijt.net
server connection : quit
domain management : list
 Continue…..
Through Graphical View:
1. First install the Support Tools from Windows server 2003 CD for –
Domain Naming Partition
Configuration Partition
Application Partition
Type the adsiedit.msc into RUN
2. For Schema Partition
Type the command into Run
regsvr32 schmmgmt.dll
Run----MMC----File-----Add/Remove snap in-----Add-----Schema Management-----Add-----Close.