SCCM 2012 SP1 cannot Create Image

Hello Experts,

I am having an issue creating a Task Sequence Media and I just cannot find anything when searching for a resolution.  Part of the problem is I am not that familiar or comfortable with SCCM 2012 but this issue seemed to surface after SCCM Service Pack 1.  We used to be able to create windows 7 images with no problems prior to the service pack.  I got assigned to create a new updated image with windows 7 sp1 and I keep recieving the following errors which I have attatched.

What I did next was removed all task sequences accept the partition, boot, and image sequence and it still does the same thing.  I tried running images that worked successfully in the past and I get the same message.

I think the problem is with the boot image and from what I read with SCCM 2012 sp1 it changes the boot image to windows 8?  Anyone come across this issue yet?


LVL 22
Nick RhodeIT DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In my opinion something is wrong with your boot image. Delete boot image from all yours DP and distribute it again.
Which version of MDT you have?
Nick RhodeIT DirectorAuthor Commented:
We are upgrading to SCCM R2 today for I do believe it is the boot image.  I have redistributed it but R2 is apparently supposed to resolve issues witht he images.  I will post an update soon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Nick RhodeIT DirectorAuthor Commented:
SCCM R2 update resolved the issue.  I believe the root of the problem was SCCM SP1 changing the boot image.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.