Skip to content
INSIGHTS & GUIDES · NETCLOUD24

Introducing Windows LAPS with controlled password retrieval

Deploy Windows LAPS through a narrow AD pilot, separate schema and account prerequisites from rotation policy, delegate retrieval and decryption deliberately, and verify backup and recovery without exposing administrator secrets.

Read the article ↓
Editorial illustration: How to Deploy Windows LAPS for Local Administrator Password Management

Platform: Windows Server 2019, 2022 and 2025, with the version and hosting restrictions described below.

Design the retrieval boundary as carefully as rotation

Windows LAPS gives managed devices distinct, regularly changed local administrator passwords and backs them up to an approved directory. Its main operational value is reducing shared local credentials while preserving a controlled emergency-access path. A deployment that rotates successfully but lets an unnecessarily broad group retrieve every password has not established a narrow administrative boundary.

Netcloud24 prepares the local-access and recovery arrangements for the managed environment. Customers should use the agreed access route and support process rather than circulate shared administrator passwords. This guide covers an authorised team deploying Windows LAPS to AD-joined member servers, with a pilot OU and delegated retrieval. Domain-controller DSRM management is a separate deliberate scope.

Check Windows LAPS rather than legacy assumptions

Windows LAPS is distinct from the older Microsoft LAPS client and schema. Supported patched Windows Server 2019 and 2022 systems receive the Windows component through updates, while Windows Server 2025 includes newer capabilities. Confirm actual update level, cmdlets and policy templates. Installing the legacy MSI is not the normal prerequisite for the new component.

A migration can run side by side only under the supported design, including targeting different accounts. Do not let old and new policies compete to rotate the same password. Inventory the existing CSE, policy and stored attributes before changing anything. Decide whether the backend is AD DS for this scope; Microsoft Entra scenarios have a different setup and should not be assumed interchangeable for every Windows Server role.

AD password encryption requires the appropriate domain functional level, at least Windows Server 2016. Establish whether encryption and any password history are supported before choosing policy. Newer automatic account-management features are version-specific; do not assume a Server 2019 client creates or enables a missing local account simply because LAPS policy names one.

Prepare AD schema and a small server scope

Extending the forest schema is a permanent directory change requiring the approved schema-administration process, backups and replication health. Do not describe unlinking a GPO as undoing the schema. Use the Windows LAPS schema cmdlet once through that process, then allow replication to converge before pilot clients write attributes.

Import-Module LAPS
# Forest change: run only through the approved schema procedure.
Update-LapsADSchema
$pilotOu = 'OU=LAPS-Pilot,OU=Servers,DC=corp,DC=example'
Set-LapsADComputerSelfPermission -Identity $pilotOu
Find-LapsADExtendedRights -Identity $pilotOu

Computer self-permission lets managed machines update their own required attributes in the scoped OU. Inspect extended rights and existing delegated groups before granting retrieval. Moving a computer into the OU changes the policy and permission context, so do it as part of a reviewed pilot rather than a bulk directory reorganisation.

Delegate reading and reset rights separately

Create narrowly owned groups for retrieving passwords and requesting expiration/reset, and grant only the appropriate role. The example names are illustrative. Review existing broad extended rights and inherited administration paths; adding a small reader group does not remove older excessive access.

Set-LapsADReadPasswordPermission -Identity $pilotOu `
  -AllowedPrincipals 'CORP\LAPS-Server-Recovery'
Set-LapsADResetPasswordPermission -Identity $pilotOu `
  -AllowedPrincipals 'CORP\LAPS-Server-Reset'
Find-LapsADExtendedRights -Identity $pilotOu

Where encrypted password backup is enabled, retrieval permission and the authorised decryption principal are related but distinct. Configure the intended encryption principal and confirm membership ownership. Use a controlled group if multiple approved roles need decryption, rather than assuming every domain administrator must be the routine operator. Audit access and changes to these groups.

Configure policy for an account that actually exists

Create a dedicated Windows LAPS GPO scoped to the pilot. Select AD backup, the approved password length, complexity and age, and supported encryption settings. Choose the managed local account deliberately. Leaving the custom account-name setting unset can target the built-in administrator by its well-known identity even if it was renamed; a named custom account must exist under the supported client behaviour.

Password management does not automatically make that account enabled or grant every remote-logon right on older releases. Keep account state and remote-access policy aligned with the recovery plan. Do not enable unnecessary administrative access merely to make a password retrieval demonstration easier.

Configure supported post-authentication rotation actions only after assessing their session and availability effects. Automatic account creation, randomised names and newer password options need their own OS support checks. Keep the initial pilot policy limited to capabilities present across its actual Server 2019, 2022 or 2025 members.

Process policy and verify backup without exposing the secret

On the pilot member server, apply policy and request LAPS processing. Inspect the operational log and metadata in AD. Do not print retrieved passwords into transcripts or a shared result file. A successful rotation event should correspond to a recent directory backup and the intended managed account.

# On the pilot member server:
gpupdate /target:computer /force
Invoke-LapsPolicyProcessing
Get-WinEvent -LogName 'Microsoft-Windows-LAPS/Operational' -MaxEvents 30
# From an authorised recovery administration session:
$result = Get-LapsADPassword -Identity 'APP-PILOT01'
$result | Select-Object ComputerName,Account,PasswordUpdateTime,ExpirationTimestamp,Source

Inspect supported object properties for the installed module if metadata names differ. Keep the password protected in its returned secure form unless the approved recovery action specifically requires disclosure. Test authorised retrieval and an unauthorised denial, then conduct a controlled logon/recovery exercise under the agreed process.

Diagnose missing or stale backups by stage

If policy is absent, inspect GPO scope, filtering, inheritance and client update support. If processing reports missing schema, check extension and replication. If writes fail, inspect computer self-permissions and directory connectivity. For encryption errors, check functional level and principal resolution. A named account that does not exist is an account-management prerequisite, not an AD read-permission fault.

If retrieval fails, distinguish read ACL, decryption authority and target identity. Do not broaden the OU to Everyone or output plaintext passwords as a diagnostic shortcut. Preserve LAPS events and relevant directory evidence without exposing the credential. Confirm the legacy product is not simultaneously managing the same account.

Retire policy without stranding recovery access

Before removing LAPS scope or delegated groups, establish how the server’s current local password will remain recoverable. Unlinking a policy does not restore an old shared password and does not erase the schema. Avoid deleting backed-up attributes or reader access before an approved replacement path exists.

Document account scope, OU, encryption principal, reader/reset groups, audit handling and emergency retrieval. Monitor stale rotations and test the recovery procedure periodically. The managed outcome is individualised local credentials with a controlled, available recovery path, not a new secret store whose access and lifecycle nobody owns.

Further reading


Was this answer helpful?

« Back
Contact

Write to us

Do you have questions about our services or need a quote? Write to us and we will respond as soon as possible.

Contact form

Fields marked * are required.