Jump to content

Recommended Posts

Posted

I recently built a new Windows 7 image for our workstations. I am re-using the SCCM task sequence (TS) I used in past years, which has always worked with minimal issues. For some reason, when I change the TS to use the latest image, it fails at the "Apply Operating System Image" step with an error code of 8022000B (this error code does not come up in any Google searches). Looking at the logs (relevant section copied below) it seems like it might be an issue with the unattend.xml file. Strangely, if I change the TS to use the old image, this error does not occur.

 

The only differences in the new image are the latest Windows updates were applied, larger disk space consumption (due to addition of AutoCAD and Autodesk Inventor) and that the base WIM went from 2 partitions (Sys Reserved + OS) to 3 (Sys Reserved + OS + Temporary Storage from captured system). I am only deploying the single OS partition through my TS (like previously) and looking at the PC after the error occurs, the files from the OS image seem to be present on the disk properly.

 

Any ideas?

 

smsts-part2.txt

Posted (edited)

Does it have a newer version of IE thanks to updates, I know that cooked one of my automated deployments as the settings keys don't stay the same between versions.

 

Also, did you capture it manually with imagex or dsim and did you use the /flags ENTERPRISE switch on the end of the capture?

Edited by SYNACK
Posted (edited)

I've copied my unattend.xml below.

 

As for IE, the old image did run IE9 and I upgraded it to IE11 for the new image. I captured the image using the capture media wizard from SCCM like I have in the past. I do not run the capture media wizard with any special options or perform any other modifications to the captured wim using imagex/dism.

 

This is a 64 bit Windows 7 Enterprise image, if that makes a difference as well.

 

Unattend.xml

true

 

Edited by netadmin
Posted
changing IE to version 10 from 9 cooked my image of win7 tho it was able to apply the image but failed when appling the unattend, ended up adding it using DISM. Further looking it was a setting in the unattended that causes it to break (Specilize Pass IEWelcomeMSG needing to be set to revert change).
Posted
I always create a new Task Sequence and unattend file when updating images, far less hassle for me that way (Although, I don't have any changes made to the unattend file either)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...