Skip to main content

Moving Computers to a New OU Stops Windows LAPS Password Rotation and Locks the Helpdesk Out

High severityActive Directory About 20 minutes to fix

Overview

Computers moved to a new OU stop rotating their Windows LAPS password and the helpdesk is denied access. The rights were on the old OU. Here is how to confirm it and grant them safely.

At a glance

Symptom
Moved computers stop updating their Windows LAPS password, and the helpdesk is denied access to the stored one.
Likely cause
Windows LAPS permissions are inheritable entries on the OU, so a computer moved to an OU without them loses both the right to write…
Impact
The local administrator password stops rotating, and the helpdesk loses supported access to it.
Verification signal
A fixed computer logs event 10018 and the helpdesk can query its password again.
Safe correction
Grant the destination OU the same Self and read permissions the old OU had, test one computer, then move the rest.
Rollback or recovery
Every step adds a permission or a link, and each can be removed without touching the others.

After computers are moved into a new organisational unit (OU), Windows LAPS on those machines can no longer write a new local administrator password to Active Directory, and the helpdesk can no longer read the one that is stored. The cause is that Windows LAPS permissions are not attached to the computer: they are inheritable access control entries (ACEs) on the OU that contains it. A computer moved into an OU that never had Set-LapsADComputerSelfPermission and Set-LapsADReadPasswordPermission run against it, or above it, loses both. The fix is to grant the same two permissions on the destination OU, make sure the Windows LAPS policy still reaches it, and only then move the rest of the computers.

Symptom

Moved computers stop updating their Windows LAPS password, and the helpdesk is denied access to the stored one. The first sign is usually a ticket: someone runs Get-LapsADPassword for a laptop that worked last week and is denied access to query the password. On the moved computer itself, the Windows LAPS log (Event Viewer, Applications and Services Logs > Microsoft > Windows > LAPS > Operational) shows processing cycles that end with:

Event ID 10017
LAPS failed to update Active Directory with the new password. The current password has not been modified

Microsoft describes 10017 as a status event at the end of a failed cycle, so the useful error is earlier in the same cycle, between event 10003 (processing starts) and 10005 (processing failed). Domain Admins can still read the stored password, because they hold query permission by default, which is why the problem can sit unnoticed until someone outside that group needs it.

Why the move looks safe

Moving a computer object feels like housekeeping. It keeps its name, its SID, its group memberships and its trust with the domain. It is easy to assume its LAPS rights travel with it the same way. They do not, and nothing in the move warns you.

Root Cause

Windows LAPS permissions are inheritable entries on the OU, so a computer moved to an OU without them loses both the right to write its password and the helpdesk’s right to read it. Windows LAPS protects passwords stored in Active Directory first with ACLs. Microsoft’s design puts those ACLs on the OU, and they are inherited by the computer objects inside it. Two separate grants matter here:

  • Set-LapsADComputerSelfPermission sets inheritable permissions on an OU so the computers in it can update their own LAPS password.
  • Set-LapsADReadPasswordPermission sets inheritable permissions on an OU so named users or groups can query LAPS passwords for the computers in it.

When the computer object moves, it stops inheriting from the old OU and starts inheriting from the new one. If the new OU was created after LAPS was rolled out, and nothing above it carries the grants, neither is there. Microsoft’s troubleshooting guide names this case under event 10065, the insufficient-rights error in legacy LAPS emulation mode: it can occur if you move the machine to a different OU and the destination OU doesn’t have the Self permission.

There is often a second gap. If the Windows LAPS Group Policy object was linked to the old OU rather than higher up, the moved computer may receive no LAPS settings at all. With no policy, BackupDirectory defaults to 0 (Disabled), and the password is not backed up anywhere.

Impact

The local administrator password stops rotating, and the helpdesk loses supported access to it. Windows LAPS checks the password expiration time in Active Directory every hour and tries to rotate when it has passed, but each attempt fails and leaves the current password in place. With the default PasswordAgeDays of 30, a password that should have changed monthly keeps working for as long as the move goes unfixed.

The tempting workaround makes it worse. Under pressure, people give the helpdesk All Extended Rights on the new OU, add them to Domain Admins, or grant read access high in the tree so it covers everything. Microsoft treats the extended rights permission as problematic on a LAPS OU, because holders can read confidential attributes and every Windows LAPS password attribute is confidential. It also recommends reserving password read access as tightly as possible and setting tighter boundaries for sensitive machines, such as executive laptops, than for frontline devices. A broad grant undoes that tiering for every computer under it. Read permission does not even guarantee the helpdesk can use an encrypted password: decryption is controlled by the ADPasswordEncryptionPrincipal setting when the device stores it, and defaults to Domain Admins.

How to confirm the destination OU is missing the rights

These checks change nothing. Run them from a machine with the Windows LAPS PowerShell module, comparing the old OU with the new one.

  1. List who can read LAPS passwords on each OU:
    Find-LapsADExtendedRights -Identity "OU=Laptops,OU=Workstations,DC=contoso,DC=com"
    Find-LapsADExtendedRights -Identity "OU=Laptops,OU=Devices,DC=contoso,DC=com"

    If the helpdesk group appears in ExtendedRightHolders for the old OU but only NT AUTHORITY\SYSTEM and Domain Admins appear for the new one, the read grant was never made there.

  2. Check the Self permission on the new OU the way Microsoft’s guide does: in LDP.exe on a domain controller, connect and bind, open View > Tree, right-click the OU, choose Security descriptor, and look for NT AUTHORITY\SELF entries for the msLAPS-Password attribute. Close the dialog without saving.
  3. On one moved computer, confirm the LAPS policy still applies:
    gpresult /scope computer /r

    The Windows LAPS GPO should be listed among the applied Group Policy objects.

Correction

Grant the destination OU the same Self and read permissions the old OU had, test one computer, then move the rest. Each grant only adds permissions, so no step leaves a computer worse off than it already is. Before you start, save the output of the Find-LapsADExtendedRights checks above as your record of the starting state, and note the original OU of every moved computer.

  1. Preview, then grant the Self permission on the destination OU:
    Set-LapsADComputerSelfPermission -Identity "OU=Laptops,OU=Devices,DC=contoso,DC=com" -WhatIf
    Set-LapsADComputerSelfPermission -Identity "OU=Laptops,OU=Devices,DC=contoso,DC=com"
  2. Grant read access to the same group the old OU allowed, and nobody wider. Use a fully qualified name; an isolated name that is not a well-known account is rejected:
    Set-LapsADReadPasswordPermission -Identity "OU=Laptops,OU=Devices,DC=contoso,DC=com" -AllowedPrincipals @("contoso\LAPS-Helpdesk-Readers")

    If the old OU also had Set-LapsADResetPasswordPermission for a group that expires passwords, repeat that grant too.

  3. If gpresult showed no LAPS policy, link the existing Windows LAPS GPO to the destination OU:
    New-GPLink -Name "Windows LAPS" -Target "OU=Laptops,OU=Devices,DC=contoso,DC=com" -WhatIf
    New-GPLink -Name "Windows LAPS" -Target "OU=Laptops,OU=Devices,DC=contoso,DC=com"
  4. On one moved computer, run Invoke-LapsPolicyProcessing instead of waiting for the hourly cycle. Stop here if the cycle still ends in 10017, and read the events between 10003 and 10005.
  5. Only when that computer passes, move the remaining computers.

Validation

A fixed computer logs event 10018 and the helpdesk can query its password again. Microsoft names 10018 as the success event. Then, as a member of the helpdesk group rather than a Domain Admin, run:

Get-LapsADPassword -Identity LAPTOP-0142 -AsPlainText

The query should succeed, DistinguishedName should show the new OU, and PasswordUpdateTime should be recent. For an encrypted password, DecryptionStatus shows whether the reader may decrypt it. Run Find-LapsADExtendedRights on the new OU once more: the holders should match the old OU, with no extra group.

Rollback

Every step adds a permission or a link, and each can be removed without touching the others. To undo the GPO link, run Remove-GPLink -Name "Windows LAPS" -Target "OU=Laptops,OU=Devices,DC=contoso,DC=com", which removes the link and leaves the GPO itself intact. To put a computer back while you investigate, move it to the OU it came from with Move-ADObject -Identity "CN=LAPTOP-0142,OU=Laptops,OU=Devices,DC=contoso,DC=com" -TargetPath "OU=Laptops,OU=Workstations,DC=contoso,DC=com", where its old LAPS rights still apply. The Self and read grants are ordinary ACEs on the OU; if one was made on the wrong OU or for the wrong group, remove that entry in the OU’s security descriptor in LDP.exe, then check the result against the record you saved.

Prevent it on the next OU change

Make the LAPS grants part of creating an OU, not part of moving computers into it. Microsoft documents setting the Self permission once on the domain root, using the distinguished name format such as DC=contoso,DC=com, which lets every computer update its own password wherever it sits. Keep read permission at OU level so sensitive machines keep their tighter boundary. Before any bulk move, run Find-LapsADExtendedRights on the source and destination OUs and compare the holders, the same way you might check that a fine-grained password policy actually reaches the accounts you think it does. It is the same class of problem as adminCount drift leaving rights behind after a change: in Active Directory, permissions follow the container, not intent.

3

Apply the safer control

Before you change production

Confirm the affected scope, export the current configuration, and test the replacement control in a non-production environment first.

Fix commands and configuration

Set-LapsADComputerSelfPermission
Set-LapsADReadPasswordPermission
Get-LapsADPassword
4

When to escalate

Validation and rollback are covered in the sections above.

Escalate

Escalate when the blast radius is uncertain, the control cannot be tested safely, or remediation requires an outage or security exception.

The KBY Brief

Fixed? Get the next one before it hits you: The KBY Brief

Practical fixes for the systems you run, by email about twice a week. Unsubscribe at any time.

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

After remediation

Further reading stays below the corrective workflow and is selected by platform, category and shared technical keywords.

Discover more

Connected KBY resources