The whenCreated attribute records the date and time an object was created in Active Directory. It has been part of the schema since Windows 2000 Server and applies to nearly every object class through top. The value is set by the system when the object is created, is read-only, and is stored in UTC. Because it is replicated and held in the Global Catalog, every domain controller reports the same creation time for a given object.
This guide covers the attribute end to end: what it stores and where it came from, its exact schema definition, and how to read and report on it. It walks through inspecting it in Active Directory Users and Computers (ADUC), querying it with PowerShell, and reporting on object age in ManageEngine ADManager Plus. Because the attribute is read-only, this guide focuses on viewing and reporting rather than setting it.
| Attribute | Value |
|---|---|
| LDAP display name | whenCreated |
| CN | When-Created |
| Syntax | String(Generalized-Time), 2.5.5.11 |
| OM-Syntax | 24 |
| Attribute ID (OID) | 1.2.840.113556.1.2.2 |
| System ID GUID | bf967a78-0de6-11d0-a285-00aa003049e2 |
| Single- or multi-valued | Single-valued |
| Read-only (system-set) | Yes (set by the system at creation; cannot be changed) |
| Indexed | No |
| In Global Catalog | Yes |
| Replicated | Yes (consistent across all domain controllers) |
| Visible in ADUC | Yes, with Advanced Features enabled; the Object tab shows the raw value in the Attribute Editor |
| Applies to | top (nearly all objects, including user, group, computer, and organizationalUnit) |
| Source schema | Windows 2000 Server |
| Microsoft reference | Win32 ADSchema, Generalized-Time syntax |
Note: Unlike whenChanged, which each domain controller maintains independently and does not replicate, whenCreated is replicated and identical on every domain controller. The value is stored in UTC as a Generalized-Time string (for example, 20230115143000.0Z), so most tools convert it to local time on display. On a restored or migrated object, the value reflects creation in the current directory, which can be later than the account's original age.
The attribute gives a reliable, forest-consistent answer to a simple question: When did this object first appear in the directory? Because it is replicated and in the Global Catalog, it is well suited to age and life cycle reporting across domains.
Common real-world uses include:
Use whenCreated when you need the directory-wide creation time. For the last modification time, use whenChanged, keeping in mind it is per domain controller and not replicated.
ADUC shows the creation date in friendly form on the Object tab and exposes the raw value in the Attribute Editor. It is read-only in both places.
Request whenCreated with -Properties; the Active Directory module returns it as a local DateTime that you can filter and sort.
Get-ADUser -Identity jdoe -Properties whenCreated |
Select-Object Name, whenCreated
Displays the creation date and time for the user jdoe.
Get-ADUser -Filter * -Properties whenCreated |
Where-Object { $_.whenCreated -ge (Get-Date).AddDays(-30) } |
Select-Object Name, SamAccountName, whenCreated |
Export-Csv -Path "C:\Reports\NewAccounts.csv" -NoTypeInformation
Exports every user account created within the past 30 days.
Get-ADUser -Filter * -Properties whenCreated |
Sort-Object whenCreated |
Select-Object -First 20 Name, whenCreated
Lists the 20 earliest-created user accounts in the domain.
Get-ADObject -Filter " objectClass -eq "organizationalUnit" " -Properties whenCreated |
Select-Object Name, whenCreated
Returns creation dates for organizational units, since whenCreated applies to nearly all object classes.
Because the attribute is read-only, ADManager Plus surfaces it through account-age and recently created reports rather than as an editable field. You can review it per user, report across the directory, delegate the reports, and schedule them from one console.
Use the All Users report to list accounts by creation date. Schedule them and export in CSV, PDF, HTML, or XLSX to track provisioning and find aging objects.
Use the Inactive Users report to identify old accounts that have never or rarely been used, then act on them in place (disable, move, or delete) from the same console.
Create a help desk role with access to the relevant user reports. Assign the role to auditors or team leads so they can review creation dates for users in their assigned OUs without needing Domain Admin rights.
Use the Automation feature to run inactive user reports on a schedule and trigger follow-up actions or notifications.
This attribute uses standard default ACLs (schema default security descriptor O:BAG:BAD:S:). It is not confidential and it is in the Global Catalog, so any authenticated user can read it across the forest, and because it is system-only there is no write path to delegate or restrict.
Practical security considerations focus on how you use it:
There is no scenario for extending the schema in place of this attribute; it is a system-maintained timestamp. To capture additional life cycle data (such as a business start date), use a purpose-built custom attribute.
whenCreated is system-generated and read-only. The value is set when the object is created and cannot be modified through ADUC, PowerShell, or ADManager Plus.
The object may have been deleted and re-created, restored, or migrated. These actions can result in a new directory object with a new creation timestamp.
whenCreated is replicated, so the value remains consistent across domain controllers. This differs from whenChanged, which is maintained locally on each domain controller and is not replicated.
The stored value is in UTC. Tools such as ADUC and PowerShell may display it in the local time zone, so the visible time can differ based on the UTC offset.
Request the attribute explicitly using -Properties whenCreated, as it is not included in the default property set returned by Active Directory cmdlets.
ADManager Plus reads whenCreated across your directory and turns it into ready-made account-age and recently created reports, so tracking new accounts and cleaning up aging ones takes no scripting.
String (Generalized-Time) syntax (2.5.5.11, OM-Syntax 24), single-valued, stored in UTC.
Nearly all of them. It is defined on top, so it applies to users, groups, computers, OUs, and more.
Yes to both. Every domain controller reports the same value, and it is available through the Global Catalog (though it is not indexed).
They return the same creation time. whenCreated is a stored, replicated attribute; createTimeStamp is a constructed one computed at read time.
It has been present since the original Windows 2000 Server schema.