Jump to content

Recommended Posts

Posted
Wish I hadn't wasted my time in setting this up a few weeks ago

 

It's good for the soul.

 

The bugs apparently are where Legacy LAPS is installed after the April update has been applied, and where April Update has been applied but Legacy LAPS is not installed and Legacy LAPS GPO Settings apply.

 

https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-overview#legacy-laps-interop-issues-with-the-april-11-2023-update

 

 

Simplest solution for us will be to uninstall Legacy LAPS and Legacy LAPS GPO settings, replacing them with functional equivalents from the modern LAPS policy options.

  • 4 weeks later...
Posted

Does this work on LTSB machines...?

 

I configured this last week and 99% of my machines have converted and stored a password in AD.

 

However I noticed a few missing and it appears they are the 1% of machines still on LTSB (the others are all on LTSC)...

 

All in the same OU, all show GPO applied with RSoP/GPResult, all have the correct local admin account, all have the correct registry entries.

Posted
Is there a procedure for using LAPS if you're going to the physical machine and logging in as admin locally, do you write down the password and reset it afterwards kind of thing?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...