Showing posts with label 1909. Show all posts
Showing posts with label 1909. Show all posts

Wednesday, 22 April 2020

LAPS not working after computer rebuilds

Many of my customers use the Microsoft Local Administrator Password Solution (LAPS) to manage local account passwords of domain joined computers. Recently I created a Windows 10 v1909 task sequence solution with ConfigMgr for one of these customers. Everything looked good in testing but after a few days I got a report to say that LAPS wasn't working. Admins couldn't sign into the devices uing the local administrator password.

I figured that was unusual so I reinstalled W10 v1909 on a test laptop and LAPS worked perfectly. That was a bit odd. What was the difference between my test and the customers test?

You have to delve a little deeper into how LAPS works to be able to answer that question. This Microsoft blog post explains what happens to LAPS during machine reinstalls.

“LAPS uses the attribute ms-MCS-AdmPwdExpirationTime on the computer object to remember the expiration time of local administrator password. It works pretty well during lifetime of computer. But what happens when computer is reinstalled? LAPS design expects that in this case, computer account is deleted and created again. But what if you decide to reuse computer account?

In this case, when you install the computer and then install LAPS CSE on it, during first GPO refresh after install, CSE looks to computer account and sees that it is not time to reset password yet: ms-MCS-AdmPwdExpirationTime attribute still has value populated by previous computer that used this computer account. This means that the password that is on local administrator account after setup may be there until the password expiration time set by previous computer expires: up to 30 days by default”.

That explained to me why my test computer worked and none of the others did. I ALWAYS delete the computer object from ConfigMgr and Active Directory before I re-image. The customer verified that they didn't do this for any of their tests.

The customer wondered why this not happen before. I explained that it did occur but they didn't notice as they didn’t test LAPS immediately. The solution corrects itself after the password expiration date.


It's easy to verify that this is happening:


I generated the password on 10th Feb but it was set to expire on 12th Feb. That was my first clue. The password should have been valid for 30 days.

I hope this helps you to explain the anomaly if you encounter it. It's expected behaviour. 

Until next time....

Note: several people have pointed out to me that it's better to automatically expire the existing password during the rebuild by including this script in the task sequence.


Thursday, 6 February 2020

Windows 10 v1909 and language packs - my experience


I've been working with Windows 10 v1909 and language packs for the first time this week. This used to be pretty easy with 1809 and Microsoft Endpoint Manager (formerly ConfigMgr or SCCM) but it's not so easy any more.

  • Download the ISO matching the Windows version
  • Extract the CAB files
  • Install the one you want in the task sequence (dism.exe /norestart /online /add-package /packagepath:xxxx.cab)
  • Apply regional settings with an xml file (e.e. rundll32.exe shell32,Control_RunDLL intl.cpl,,/f:"English_UK.xml")
What do we do now with v1909? I can see that 1909 has nothing new so we use the 1903 media, but which one? As well as the LXP files we can still download the .cab files as before. They are included in the Windows 10 version 1903 Language Packs (released May 2019) 32/64 MultiLanguage ISO (5852MB).




Tip: choose MultiLanguage as the language using the drop down menu.


I downloaded this ISO, extracted the cab files and organized them in folders (in the same way I had done for 1809, making sure that the files had the same name). Then I created packages (without programs) using these folders as source files. I "figured" that I just had to replace these packages in my existing 1809 task sequence and all would be good.

However it wasn't. In my testing, this breaks the search function and messes up some dialog on the regional settings


The search bar wouldn't work at all. I couldn't even type in it. That was a showstopper straight away. 


Also the regional settings contained a lot of garbage.

I did some research and others seemed to be having similar problems with no real resolution. 

Eventually I got this working by adding a step in the task sequence to install the January 2020 CU for 1909 before installing the language pack. 

KB4528760


Search bar now working......


....and this is how the Regional settings should look.

I hope this helps you if you encounter the same problem. Until next time.....