Skip to main content

Goodbye, Microsoft LAPS, and a big welcome to Windows LAPS. Windows LAPS is finally available for both cloud and on-premises environments. Every administrator should set up Windows LAPS in Active Directory for easier management of the domain-joined device’s local passwords. In this article, you will learn how to install Windows LAPS step by step.


What is Windows LAPS?

Windows Local Administrator Password Solution (Windows LAPS) is a Windows feature that automatically manages and backs up the password of a local administrator account on your Azure Active Directory-joined or Windows Server Active Directory-joined devices. You also can use Windows LAPS to automatically manage and back up the Directory Services Restore Mode (DSRM) account password on your Windows Server Active Directory domain controllers. An authorized administrator can retrieve the DSRM password and use it.

You might already be familiar with the existing Microsoft security product known as Local Administrator Password Solution (LAPS). LAPS has been available on the Microsoft Download Center for many years. It is used to manage the password of a specified local administrator account by regularly rotating the password and backing it up to Active Directory (AD). LAPS has proven to be an essential and robust building block for AD enterprise security on premises. We’ll affectionally refer to this older LAPS product as “Legacy LAPS”.

Windows LAPS doesn’t require you to install legacy LAPS. You can fully deploy and use all Windows LAPS features without installing or referring to legacy LAPS.

Note: The feature is ready to go out of the box. You no longer need to install an external MSI package! Microsoft will deliver future fixes or feature updates via the normal Windows patching processes.

Windows LAPS benefits

Benefits of using Windows LAPS:

  • Use Windows LAPS to regularly rotate and manage local administrator account passwords and get these benefits:
  • Protection against pass-the-hash and lateral-traversal attacks
  • Improved security for remote help desk scenarios
  • Ability to sign in to and recover devices that are otherwise inaccessible
  • A fine-grained security model (access control lists and optional password encryption) for securing passwords that are stored in Windows Server Active Directory
  • Support for the Azure role-based access control model for securing passwords that are stored in Azure Active Directory

Windows LAPS Management

The below options are available to manage and monitor Windows LAPS:

  • The Windows Server Active Directory Users and Computers properties dialog
  • A dedicated event log channel
  • A Windows PowerShell module that’s specific to Windows LAPS

No more dedicated LAPS Management client (LAPS UI) exists, as we had in Legacy Microsoft LAPS.

Windows LAPS requirements

Windows LAPS is available on the following OS platforms with the specified update or later installed:

Note: There are no license requirements to use Windows LAPS, and it’s integrated into Windows OS.

Do you want to find which Windows OS Builds are running in the organization?

How to configure Windows LAPS

To configure Windows LAPS in Active Directory, follow the below steps:

1. Update Windows Server

Ensure that you run Windows Update on all  Domain Controllers . If you only update 1x Domain Controller and extend the Active Directory schema (next step), it will throw an error.

2. Extend Active Directory Schema

There is no Windows LAPS client to download and install on the Domain Controller like we are used to with Microsoft LAPS because it’s already integrated into Windows Server 2019 and higher.

1. Run PowerShell as administrator on the Domain Controller.

2. Run ipmo LAPS to import the LAPS module.

PS C:\> ipmo LAPS

3. Run the gcm -Module LAPS command to verify the LAPS module is loaded.

Note: If there is no output after running above command, you must update your Windows Server to the supported version (see above).

PS C:\> gcm -Module LAPS

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Function        Get-LapsAADPassword                          LAPS
Function        Get-LapsDiagnostics                          LAPS
Cmdlet          Find-LapsADExtendedRights                    LAPS
Cmdlet          Get-LapsADPassword                           LAPS
Cmdlet          Invoke-LapsPolicyProcessing                  LAPS
Cmdlet          Reset-LapsPassword                           LAPS
Cmdlet          Set-LapsADAuditing                           LAPS
Cmdlet          Set-LapsADComputerSelfPermission             LAPS
Cmdlet          Set-LapsADPasswordExpirationTime             LAPS
Cmdlet          Set-LapsADReadPasswordPermission             LAPS
Cmdlet          Set-LapsADResetPasswordPermission            LAPS
Cmdlet          Update-LapsADSchema                          LAPS

4. Run the Update-LapsADSchema cmdlet, press A, and follow with Enter.

PS C:\> Update-LapsAdSchema

The 'ms-LAPS-Password' schema attribute needs to be added to the AD schema.
Do you want to proceed?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): A

3. Check LAPS attributes

To verify that the LapsAdSchema ran successfully, run the Update-LapsAdSchema again with the -Verbose parameter.

PS C:\> Update-LapsAdSchema -Verbose

The end of the output is important, which shows that the LAPS schema is already extended successfully with the attributes:

  • msLAPS-PasswordExpirationTime
  • msLAPS-Password
  • msLAPS-EncryptedPassword
  • msLAPS-EncryptedPasswordHistory
  • msLAPS-EncryptedDSRMPassword
  • msLAPS-EncryptedDSRMPasswordHistory
VERBOSE: The 'computer' classSchema already has a required mayContain: msLAPS-PasswordExpirationTime
VERBOSE: The 'computer' classSchema already has a required mayContain: msLAPS-Password
VERBOSE: The 'computer' classSchema already has a required mayContain: msLAPS-EncryptedPassword
VERBOSE: The 'computer' classSchema already has a required mayContain: msLAPS-EncryptedPasswordHistory
VERBOSE: The 'computer' classSchema already has a required mayContain: msLAPS-EncryptedDSRMPassword
VERBOSE: The 'computer' classSchema already has a required mayContain: msLAPS-EncryptedDSRMPasswordHistory
VERBOSE: The 'computer' classSchema already has all expected LAPS-related mayContains
VERBOSE: ProcessRecord completed
VERBOSE: EndProcessing started
VERBOSE: EndProcessing completed

Go to a Windows 10/Windows 11 AD object properties and select the Attribute tab.

Note: If you don’t see the Attribute Editor tab, click in Active Directory Users and Computers in the menu bar on View and enable Advanced Features.

Windows LAPS attributes

You will also see the LAPS tab, and you can click on it. But it’s empty for now and will populate information once you complete all the steps.

Windows LAPS in Active Directory Users and Computers computer object empty

4. Set LAPS AD Computer permission

The managed device needs to be granted permission to update its password. This action is performed by setting inheritable permissions on the Organizational Unit (OU) the device is in. The setting will apply to all nested OUs too.

In our example, we want set permissions on the Company OU.

Active Directory Company OU

Set the permissions on the Company OU with the Set-LapsADComputerSelfPermission cmdlet.

Note: Do you have computers in other OUs? You need to repeat the below and add the OUs which have computers added to them.

PS C:\> Set-LapsADComputerSelfPermission -Identity "Company"

Name    DistinguishedName
----    -----------------
Company OU=Company,DC=exoip,DC=local

Suppose it fails because the OU name is used multiple times in Active Directory, then copy the DistinguishedName and place that in the command.

PS C:\> Set-LapsADComputerSelfPermission -Identity "OU=Company,DC=exoip,DC=local"

5. Set up LAPS GPO

Configure a GPO for LAPS and enable its settings.

1. Start Group Policy Management on the Domain Controller.

2. Right-click the Desktops OU.

3. Click Create a GPO in this domain, and link it here.

Create a GPO in this domain

Is the new Group Policy Object (GPO) a user or computer policy? Or will you place user and computer policy settings in the GPO? If it’s a Computer Policy, we recommend placing a C_ before the group policy name. If it’s a User Policy, make it a U_. Do you want to add computer and user policy settings in a new group policy object? Name it CU_.

  • C stands for Computer Policy
  • U stands for User Policy
  • CU stands for Computer and User Policy

In our example, the GPO is a computer policy, so the name will start with C_.

4. Give the Policy the name: C_LAPS.


5. Right-click the C_LAPS GPO and click Edit.

6. Navigate to Computer Configuration > Policies > Administrative Templates > System > LAPS.

Windows LAPS Group Policy settings

7. Double-click on Configure password backup directory setting.

8. Select Enabled and choose the backup directory Active Directory.

Important: You have to ENABLE the setting and select Active Directory or Azure Active Directory. Otherwise, the local administrator password is not managed and will not work.

Windows LAPS password backup directory

9. Double-click on Password Settings setting.

10. Select Enabled and configure the password complexity.

Windows LAPS password settings

11. Double-click on Name of administrator account to manage setting.

12. Select Enabled and insert the administrator account name lapsadmin.

Windows LAPS name of administrator account to manage

13. This is what the LAPS GPO state looks like.

Windows LAPS Group Policy settings configuration

6. Create local admin account

In the previous step, we did enable the Name of administrator account to manage setting and set the administrator account name: lapsadmin.

The LAPS GPO will not create your local administrator account on all the machines. That’s something you have to take care of with another GPO, a PowerShell script, or another choice.

Important: Disable all the other local admin accounts and ensure that only the lapsadmin account is enabled for security purposes.

This is what it will look like on a computer.

Windows LAPS local user account on computer

Note: After completing all the above steps, restart the domain-joined Windows computer to have the changes take effect.

The Windows LAPS configuration is successfully completed.

Get LAPS password

Now let’s see how to retrieve the LAPS Password in GUI and PowerShell.

Get LAPS password with GUI

Get the LAPS password directly from the Active Directory Users and Computer console.

1. Start Active Directory Users and Computers.

2. Go to the AD computer object properties.

3. Select the tab LAPS.

You will see that the fields are now filled in and are not empty anymore. It means that Active Directory connected with the Windows computer and synchronized the information.

4. Click on Show Password.

Windows LAPS show password

Get LAPS password with PowerShell

An excellent way to get the LAPS password and information is with PowerShell.

1. Run PowerShell as administrator

2. Run the Get-LapsADPassword cmdlet and fill in the target computer, including the -AsPlaintText parameter.

PS C:\> Get-LapsADPassword "WIN10" -AsPlainText

ComputerName        : WIN10
DistinguishedName   : CN=WIN10,OU=Desktops,OU=Company,DC=exoip,DC=local
Account             : lapsadmin
Password            : .[lBkDWXy1&kg3
PasswordUpdateTime  : 4/17/2023 10:23:46 AM
ExpirationTimestamp : 5/17/2023 10:23:46 AM
Source              : EncryptedPassword
DecryptionStatus    : Success
AuthorizedDecryptor : EXOIP\Domain Admins

Sign in with LAPS password

Always test if everything works as you expect and test the LAPS local admin account password.

Sign in with the local admin account lapsadmin and the password that appears in LAPS for the computer.

Sign into computer with LAPS password

We are successfully signed into the Windows 10 computer, with the Local Administrator Password generated from Active Directory (LAPS).

Get Windows hostname and whoami

Reset Windows LAPS password

There are times when you want to reset the Windows LAPS password.

1. Click on Expire now.

Windows LAPS expire now

2. Run a GPO update on the Windows computer and verify that the LAPS local admin account password is reset.

Windows LAPS verify reset

3. You can also run the Reset-LapsPassword cmdlet on the Windows computer.


4. It will reset the current/new password expiration and LAPS local admin account password.

Windows LAPS verify new expiration and password

You successfully set up Windows LAPS in Active Directory and tested that everything works.

Leave a Reply