Blog Post

Windows IT Pro Blog
4 MIN READ

By popular demand: Windows LAPS available now!

JaySimmons's avatar
JaySimmons
Icon for Microsoft rankMicrosoft
Apr 11, 2023
Welcome to the new and improved Windows LAPS! That's Local Administrator Password Solution. We've been listening to your feedback and requests, and the day is finally here for both cloud and on-premi...
Updated Nov 09, 2023
Version 7.0
security
servicing and updates
JaySimmons's avatar
JaySimmons
Icon for Microsoft rankMicrosoft
Apr 13, 2023

Anthonymelwhrhs ,

 

>>Is this interop bug guaranteed to happen?

 

It is a near certainty based on all reproes I have looked at.  The other prereqs are that 1) the device also has to have the legacy LAPS policy installed prior to the install of the legacy LAPS MSI, and 2) Windows LAPS has to have already noticed the legacy LAPS policy and enforced it, ie set a password on the legacy LAPS AD attribute and on the local account.  

 

If you did not apply the legacy LAPS policy until after the legacy LAPS MSI pkg was installed, then you will not run into it (Windows LAPS will defer to legacy LAPS).  Maybe that is what happened in your case?  Are you using a staging OU for the intial domain-join?

 

The Windows LAPS event log should tell the exact story.   If you want to, please run Get-LapsDiagnostics cmdlet and send me a private message with the zip file - then I can probably tell you the history of how it did or didn't happen on that device.