Share via

AD LDS

  • Article

Applies To: Windows Server 2008 R2

Organizations that have applications that require a directory for storing application data can use Active Directory Lightweight Directory Services (AD LDS) as the data store. AD LDS runs as a service that is independent of a domain's directory service. AD LDS does not require deployment on an Active Directory domain controller. In addition, you can install multiple instances of AD LDS and run them concurrently on a single computer.

Note: AD LDS was previously known as Active Directory Application Mode (ADAM).

Managed Entities

The following is a list of the managed entities that are included in this managed entity:

Name Description

Configuration

If there is a change to the configuration of an Active Directory Lightweight Directory Services (AD LDS) instance, the change must be registered with the instance's internal database as well as with the databases of any replication partners that are configured. Such updates are especially important when replication partners exist, because a local instance cannot receive any updates from its replication partners until the change is registered by the replication partners in their respective databases. The configuration changes that must be recorded and replicated include the following:

  • Host name modification of the server that hosts the AD LDS instance
  • Changes to the network communication port on which AD LDS services are offered
  • Changes to the service account that AD LDS is using

Note: AD LDS provides services by using the security credentials of a user account. A user account that a service uses is commonly known as a service account.

SCP

When Active Directory Lightweight Directory Services (AD LDS) is running on a computer that is joined to a domain, the AD LDS instance creates a serviceConnectionPoint (SCP) object in the domain so that other computers in the domain can locate the AD LDS instance.

Active Directory