Server 2025 – GPUpdate triggers immediate LAPS reset
So we’re currently testing out the Public preview of Windows 2025 and have noticed some new behaviour when testing out joining the OS to our domain. Initially all works well, the system joins the domain and our LAPS GPOs take over managing the local administrator password, allowing some of our automation to retrieve the password and start running tasks against the system.
However one thing we’ve noticed is that as soon as a gpupdate is triggered on Server 2025 it causes LAPS to immediately reset the password again, something that doesn’t occur on Server 2019 or 2022. This in turn causes our ansible automation to immediately begin failing because the credentials are now incorrect.
Does anyone know if this is intended behaviour? Or just a quirk of the Preview version? If it is intended behaviour is this something we can change? Given that it only seems to be happening for Server 2025 I’m hoping there might be some OS config we can change to stop it happening, but I’m not sure if we might need to make changes to our GPO instead.
So we’re currently testing out the Public preview of Windows 2025 and have noticed some new behaviour when testing out joining the OS to our domain. Initially all works well, the system joins the domain and our LAPS GPOs take over managing the local administrator password, allowing some of our automation to retrieve the password and start running tasks against the system. However one thing we’ve noticed is that as soon as a gpupdate is triggered on Server 2025 it causes LAPS to immediately reset the password again, something that doesn’t occur on Server 2019 or 2022. This in turn causes our ansible automation to immediately begin failing because the credentials are now incorrect. Does anyone know if this is intended behaviour? Or just a quirk of the Preview version? If it is intended behaviour is this something we can change? Given that it only seems to be happening for Server 2025 I’m hoping there might be some OS config we can change to stop it happening, but I’m not sure if we might need to make changes to our GPO instead. Read More
