Extend the AD schema and delegate rights before LAPS rollout

Use this document to resolve one bounded operational decision: Extend the AD schema and delegate rights before LAPS rollout. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Get started with Windows LAPS and Windows Server Active Directory from Microsoft supports the following bounded statements:

• The AD-backed Windows LAPS workflow updates the schema and grants managed devices permission to write their passwords. The research record locates this support at Sections: Update the schema; Grant the managed device permission.
• A domain functional level earlier than 2016 cannot use Windows LAPS password encryption. The research record locates this support at Section: Domain functional level and domain controller operating system version requirements.

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios and the conditions the source actually describes.

What the source does not establish

Separate device write rights, password-read rights, and expiration rights during delegation. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Sections: Update the schema; Grant the managed device permission, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section: Domain functional level and domain controller operating system version requirements, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios are in and out of scope?
• Which condition in Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Sections: Update the schema; Grant the managed device permission; Section: Domain functional level and domain controller operating system version requirements. Favor policy exports, directory access-control entries, sanitized client events, rotation tests, retrieval authorization, and exception records, linked to stable identifiers, time, and operator.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• Get started with Windows LAPS and Windows Server Active Directory — Microsoft