So we haven't changed anything with our Task Sequences but all of a sudden we're getting an error on every machine we try to image.

The step that it seems to be on when it fails is just running a script to add the machine to an OU in AD.

The error referenced is 8007052e.  All the information I find online with that error point to something to do with a username or password but I've tested our service account for SCCM and it works just fine.

I checked the SMSTS and CCMEXEC files but couldn't find a reference to that error message anywhere.

I did notice that the machines ended up not on the domain which normally would have been done before the step that it showed when the error came up.  The only thing we changed recently was to add an extra NCI driver into the Boot Image for a new model but the laptops are getting online since they couldn't download the image if they weren't.  It just seems very strange.

If I can provide info from any certain log file, please let me know and I'll add it in.

Thanks!

On the client, go to C:\Windows\Panther\UnattendGC and look in setupact.log Also check C:\Windows\Debug\NetSetup.log for domain join issues. If it's not in the domain it's not gonna succeed in moving the machine to another OU. That NIC driver you added probably messed things up. As long as the client gets an IP address in WinPE it won't have any issues pulling the wim file. But bad drivers in the boot image might mess things up later when OSD continues in Windows.

I thought the boot image file were only used in the initial PE area and that it woudl use the actual Windows drivers once it booted into Windows.

The SetupAct.log file has a bunch of errors that it could not join the domain so I'm also thinking it's something with the NIC driver.

I don't have a netsetup.log file in the debug folder.

I'll see if I can remove the one we added and see if things go back to normal.

I thought the boot image file were only used in the initial PE area and that it woudl use the actual Windows drivers once it booted into Windows.

I thought the boot image file were only used in the initial PE area and that it woudl use the actual Windows drivers once it booted into Windows.

That is correct. Did you see my other post? The error code clearly indicates the issue

Yes sorry, missed that. However, the error code is unambiguous and there is no other interpretation of it.

There is no service account in ConfigMgr. The account used in the task running the script is the account in question here (assuming that you are using a run command-line task with alternate credentials specified).

Yes sorry, missed that. However, the error code is unambiguous and there is no other interpretation of it.

There is no service account in ConfigMgr. The account used in the task running the script is the account in question here (assuming that you are using a run command-line task with alternate credentials speci

Well, I just went to check out my Boot Images and seem to have a problem.  We have 2 images.  One that is x86 and one for x64.  When I try to open the x86 one I get an error that says:

Failed to query for Drivers.

Same error as mentioned in this thread.

I tried to go to the new drivers I added last week and uncheck the x86 boot image but after i clicked OK it just hung for a while and then came back and said "Some packages cannot be updated".

• Edited by Kelemvor33 14 hours 1 minutes ago