Support for the new LAPS (April 2023 Update)
modified the existing LAPS Dynamic folder to work with the "new" LAPS (April 2023 Update), This Version fetches the Connections out from AD (Get-ADComputer) and the LAPS user and Password also via AD (Get-LapsADPassword)
also solved the problem with german umlauts, added description field from AD
@krikk This adds a completely new file to the repo new LAPS (Windows PowerShell).rdfx instead of replacing the original.
Is this new script not compatible with older versions of LAPS or did this happen accidentally?
the "new" LAPS (released April 2023) has new powershell Commands, which are different to the "old" one, so this script will only work with "new" LAPS and not with the old one, so it's better to offer both, ...the old one for people still using the old laps, and the "new" version for up-to-date Systems
and sorry about the naming, but Microsoft did this "bad" naming :)
new LAPS: Windows LAPS is now available on the following OS platforms with the specified update or later installed:
Windows 11 22H2 - April 11 2023 Update Windows 11 21H2 - April 11 2023 Update Windows 10 - April 11 2023 Update Windows Server 2022 - April 11 2023 Update Windows Server 2019 - April 11 2023 Update
@krikk Thx for the clarification. So, should we maybe name the new script LAPS April 2023 (Windows PowerShell).rdfx instead of new LAPS (Windows PowerShell).rdfx to make that more clear?
as the "new" LAPS is inbuild into the OS with the April 2023 OS Updates, it will become the new standard very fast
so i would suggest the following: rename the old "LAPS (Windows PowerShell).rdfe" to "LAPS (deprecated) (Windows PowerShell).rdfe" <- this because the the old LAPS need additional software and non-standard powershell Modules and the new file (mine) to "LAPS April 2023 (Windows PowerShell).rdfe"
@krikk Yeah, that sounds good to me! Awaiting the changes...
nearly forgot this one, renamed like planned, i think it ready to merge
Why not naming the old laps LEGACY or classic?