Windows LAPS installation in Windows server 2016 forest Functional level

Question

Could not able to install windows laps in windows server 2016 with same functional level as when we try to extend the schema using Update-LapsAdSchema cmdlets it showing module not found and in below mentioned article microsoft has installed in windows 16 DFL.

https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-scenarios-windows-server-active-directory

Does anyone have idea about the same.

Thanks in advance!

Answer 1

Once your domain reaches 2016 DFL, you can enable Windows LAPS password encryption. However if you're still running any WS2016 DCs, those WS2016 DCs don't support Windows LAPS and therefore can't use the DSRM account management feature.

https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-scenarios-windows-server-active-directory

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Hello NIYAZAHMAD-7887930407,

Thank you for your question and for reaching out with your question today.

The article you mentioned states that LAPS (Local Administrator Password Solution) can be installed on Windows Server 2016 with the same functional level. However, you are encountering an issue when trying to extend the schema using the Update-LapsAdSchema cmdlets.

The error message "module not found" suggests that the required PowerShell module for LAPS is not installed on your Windows Server 2016. To resolve this issue, you need to ensure that the LAPS PowerShell module is installed on the server where you are running the Update-LapsAdSchema cmdlets.

Here are the steps to install the LAPS PowerShell module:

1. Download the LAPS installer from the Microsoft Download Center: https://www.microsoft.com/en-us/download/details.aspx?id=46899
2. Extract the contents of the installer package.
3. Run the installer and follow the on-screen instructions to install LAPS.
4. After the installation is complete, the LAPS PowerShell module should be available on your server.

Make sure you are running PowerShell with elevated privileges (Run as Administrator) when executing the Update-LapsAdSchema cmdlets.

If you have already installed the LAPS module but are still encountering the "module not found" error, ensure that the module's installation path is included in the PowerShell module search path. You can check the module path by running the following command in PowerShell:

$env:PSModulePath

If the LAPS module is not listed in the output, you may need to manually add its installation path to the PSModulePath environment variable. You can do this by modifying the system environment variables.

After performing these steps, you should be able to successfully extend the schema using the Update-LapsAdSchema cmdlets on your Windows Server 2016.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.