Lsass.exe - Operation Failed on all newly updated XP images
Decided I’d go back through and grab a couple of our XP models and push out the most up to date pre-sysprepped image that I had, run Windows Update to grab the final updates (about 6-8 months worth) and then sysprep and upload. When deployed to any machine other than the one the image was created on, I get the dialog box shown in the attached image when it should be going to mini-setup.
The first time it happened, I made the assumption that I had a corrupt image, but with a second image totally different image doing it as well, I have to assume that it is something else. The only thing that I can come up with is something in the last 6-8 months of Windows patches.
Has anyone else run into this?
Also, to save anyone the question, I have googled the issue, and no, it is not any sort of worm or malware.
In the next two or three months we are finally supposed to have everything in place so that I can start pushing Windows 7 out to these machines, but in the meantime, I have a need to reimage a ton of them and was hoping to have them as up to date as I could.
Oddly enough, this problem fixed itself. All of the workstations are working just the way they are supposed to, no errors, images deployed just peachy. Going to chalk this one up to gremlins.
Sounds like it’s enumerating the PC1 instance but can’t find it on the PC2 so it errors out.
I understand what lsass.exe is doing, and I’ve found quite a few leads on it, my real confusion is just on what is going on in this particular instance. I updated the image for computer model A on PC1, uploaded, and pushed it to PC2 (same model) and got the error I indicated above. However, I then zeroed out PC1’s hard drive, redeployed that image to PC1 (that was build on PC1) and I have no problems.
I know I’m quoting Tom with this but here it is straight from Microsoft Support.