whenCreated attribute in Active Directory: How to view and report

Last updated on:

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.

whenCreated at a glance

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.

What the whenCreated attribute is used for

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:

  • Account age and onboarding: Determine how long a user, group, or computer has existed, and correlate with joiner records.
  • Stale object cleanup: Combine creation date with last-logon data to find old, unused accounts.
  • Security investigations: Spot recently created accounts that could indicate a backdoor or unauthorized provisioning.
  • Audit and compliance: Evidence object creation timelines for reviews and change reconciliation.

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
  • PowerShell
  • ADManager Plus
  • Troubleshooting
  • Why ADManager Plus
  • FAQ
 

How to view the whenCreated attribute using ADUC

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.

  1. From the ADUC menu, select View > Advanced Features. This unlocks the Object and Attribute Editor tabs.
  2. Right-click the object and select Properties. Select the Object tab to see the Created date in local time.
  3. For the raw value, select the Attribute Editor tab and locate whenCreated. It appears as a Generalized-Time string.
  4. Note that the field cannot be edited; it reflects the system-set creation time.

Limitations of using ADUC to view attributes

  • Read-only: The value cannot be changed; it reflects the creation time only.
  • One object at a time: There is no way to list creation dates across many objects in ADUC.
  • No filtering by age: ADUC cannot select objects created within a date range.
  • No export: Creation dates cannot be exported for reporting from ADUC.

How to read the whenCreated attribute using PowerShell

Request whenCreated with -Properties; the Active Directory module returns it as a local DateTime that you can filter and sort.

View the current value

Get-ADUser -Identity jdoe -Properties whenCreated |
Select-Object Name, whenCreated

Displays the creation date and time for the user jdoe.

Report on accounts created in the last 30 days

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.

Find the oldest accounts

Get-ADUser -Filter * -Properties whenCreated |
Sort-Object whenCreated |
Select-Object -First 20 Name, whenCreated

Lists the 20 earliest-created user accounts in the domain.

Read the value on any object type

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.

Common PowerShell errors

  • Attribute is not writable: Attempting to set whenCreated fails, because it is system-only and read-only.
  • Attribute not returned: It is absent from output unless you request it with -Properties whenCreated.
  • Time-zone confusion: The module shows local time while the stored value is UTC; account for the offset in reports that span regions.

Limitations of PowerShell

  • Read-only: You can read and report on the value but never change it.
  • Not indexed: Date-range filters scan objects rather than using an index, so large queries can be slow.
  • Scripting knowledge required: Age reports assume familiarity with the Active Directory module.
  • No native delegation: Giving help desk staff a safe, scoped way to run these reports means building and securing wrapper scripts.

How to work with the whenCreated attribute using ADManager Plus

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.

View the creation date for a single user

  1. Navigate to Management > User Management > Modify Single User.
  2. Search for and select the user account.
  3. Review the object details, where the creation date is shown.
  4. Use a report instead if you need the value for many users at once.

Report on recently created and aging accounts

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.

  1. Navigate to Reports > User Reports > All Users.
  2. Select the desired domain and click Generate. The user list along with the When Created field will be displayed.
Generating the All Users report in ADManager Plus to view the whenCreated attribute.

Report using last-logon data for cleanup

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.

  1. Navigate to Reports > User Reports > Inactive Users under Logon Reports.
  2. Select the domain and time period, and then click Generate. The user list along with the When Created field will be displayed.
  3. Use the Action drop-down to select your preferred management action and click Go.
  4. Review the user list on the next screen and click Apply.
Inactive Users report in ADManager Plus showing the When Created field.

Delegate reporting to non-admins

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.

  1. Navigate to Delegation > Help Desk Roles and click + Create New Role.
  2. Enter a Role Name and Description.
  3. Select the appropriate task, for example, select the AD Reports tab > User Reports > All Users.
  4. Save the role and assign it to the operator's account, scoped to the relevant OU.

Automate inactive user cleanup

Use the Automation feature to run inactive user reports on a schedule and trigger follow-up actions or notifications.

  1. Navigate to the Automation tab and click + Create New Automation.
  2. Enter the automation name and description, select User Automation as the category, and choose your domain.
  3. Under Tasks to automate, select Disable users.
  4. Under Select objects, choose the Inactive Users report.
  5. Set the execution time, then click Save.
Configuring an automation task to clean up inactive users in Active Directory using ADManager Plus.

Security and access considerations

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:

  • Monitor new account creation: Regularly review recently created accounts, since unexpected new objects can signal unauthorized provisioning or persistence.
  • Corroborate with audit logs: Pair whenCreated with directory change auditing to see who created an object, which the attribute itself does not record.
  • Account for restores: A recovered or re-created object carries a new creation time, so do not treat whenCreated as an immutable record of original account age.

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.

Troubleshooting

1. The whenCreated attribute cannot be changed

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.

2. whenCreated shows a newer date than expected

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.

3. whenCreated values across domain controllers

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.

4. Time differences in ADUC

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.

5. whenCreated does not appear in PowerShell results

Request the attribute explicitly using -Properties whenCreated, as it is not included in the default property set returned by Active Directory cmdlets.

Related attributes

  • whenChanged: The last time the object was modified. It is maintained per domain controller and is not replicated, so it can differ between domain controllers.
  • createTimeStamp: A constructed attribute that returns the same creation time as whenCreated, computed rather than stored.
  • modifyTimeStamp: A constructed attribute for the last-modified time, the computed counterpart to whenChanged.

Report on whenCreated and every other Active Directory attribute from one console

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.

Frequently asked questions

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.

Manage whenCreated and any AD attribute at scale with ADManager Plus

The one-stop solution to Active Directory Management and Reporting
Email Download Link Email the ADManager Plus download link