Tombstone
object classes and attributes
Active Directory Recycle Bin helps minimize directory service downtime by enhancing your ability to preserve and restore accidentally deleted Active Directory objects without restoring Active Directory data from backups.By default, Active Directory Recycle Bin in Windows Server 2008 R2 is disabled. To enable Active Directory Recycle Bin, your environment must meet the requirements to completed scenarioused to restore object deleted form AD or restore Multi OUs.
The tombstone lifetime in an Active Directory forest determines how long a deleted object - aka a 'tombstone' - is retained in Active Directory. The tombstone lifetime is determined by the value of the tombstoneLifetime attribute on the Directory Service object in the configuration directory partition.Tombstone Lifetime assists in removing objects from replicated servers and preventing restores from reintroducing a deleted object. Actually when an object is deleted from Active Directory, it is not physically removed from the Active Directory for some days. Instead, the Active Directory sets the 'isDeleted' attribute of the deleted object to TRUE and move it to a special container called 'Tombstone'. The default Tombstone Life time period is 60 days in Windows Server 2003 But the default Tombstone Lifetime period has been changed in Windows Server 2003 SP1 and later to 180 days. The tombstone lifetime attribute remains same on all the domain controllers and it is deleted from all the servers at the same time. This is because the expiration of a tombstone lifetime is based on the time when an object was deleted logically from the Active Directory, rather than the time when it is received as a tombstone on a server through replication.Reconfiguring Tombstone Lifetime: Default period of Tombstone Life time is 180 days in Windows Server 2003 SP2 or later. This is because the value of tombstoneLiftetime object is The default Tombstone Lifetime can be modified through ADSIEDIT console, if necessary. the longer tombstone lifetime decreases the chance that a deleted object remains in the local directory of a disconnected DC beyond the time when the object is permanently deleted from online DCs. This attribute is located in the below path: cn=Directory Service,cn=Windows NT,cn=Services,cn=Configuration,dc=To Change the Value, go to:Run > ADSIEDIT.mscExpand: Configuration > CN= Configuration > CN=Services > CN=Windows NT > and right click on CN= Directory ServiceYou will get an attribute window, Drill down to tombstoneLiftime, and double click it. You will get a field to type down the value, type the value you intended and click OK.
A: A printer share
lingering object
Object
The number of days before a deleted object is removed from the directory services. This assists in removing objects from replicated servers and preventing restores from reintroducing a deleted object. This value is in the Directory Service object in the configuration NIC by default 2000 (60 days) 2003 (180 days)
Domain controller is the physical object.
It is the Relative Identifiers (RID) & Security Identifiers (SID) that uniquely identifies an object throughout the Active Directory Domain. On page 85
schema attributes
acl
The Active Directory schema defines the kinds of objects, the types of information about those objects, and the default security configuration for those objects that can be stored in Active Directory. The Active Directory schema contains the formal definitions of all objects, such as users, computers, and printers that are stored in Active Directory. On domain controllers running either Windows 2000 or Windows Server 2003, there is only one schema for an entire forest. This way, all objects that are created in Active Directory conform to the same rules. The schema has two types of definitions: object classes and attributes. Object classes such as user, computer, and printer describe the possible directory objects that you can create. Each object class is a collection of attributes. Attributes are defined separately from object classes. Each attribute is defined only once and can be used in multiple object classes. For example, the Description attribute is used in many object classes, but is defined only once in the schema to ensure consistency.