Score:0

WDS Unattend with LAPS

in flag

For a few years, we have been using WDS and MDT to make images and then boot new laptops via PxE to be imaged. During the image, they are configured properly, connected to our domain, get applications installed and get all relevant GPOs. This has been working fully unattended the whole time.

Recently however, we have rolled out LAPS. Laps is great and all but it has started making the imaging process a real pain. Once the laptop connects to the domain and gets GPOs, LAPS is immediately set up. The laptop will restart about 5 times during the image and since setting up LAPS, we need to manually enter the randomized password every time as the image fails to login with the default password we have given it, which defeats the purpose of the image being fully automated.

Is there a way using WDS to have it take the password from LAPS and auto login with that instead of the default password that is stored in the unattend.xml file? I have tried looking around for a solution but have been unable to find one.

joeqwerty avatar
cv flag
I might suggest modifying WDS to create new computer accounts in an OU where you block GPO inheritance, or barring that, find a way to filter your LAPS GPO so that it isn't applied to the computer until you're ready to hand it off to the end user.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.