SCCM 2012 Task Sequence Error

I'm getting a failed task sequence with error code (0x800700A1). I know the error means it can't resolve a package source. However, I'm sure how to determine which piece of the sequence is broken.

Thanks.
LVL 1
LCNWAsked:
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.

WyoComputersCommented:
http://elgwhoppo.com/2012/07/02/today-in-my-scc/

I usually tell it to run package source from distribution point and use UNC share name for source location

\\servername\share\deploythis.vbs

if you are copying from distro point to local computer then running it, use environment variables like %computername% or %~dp0 or similar

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
merowingerCommented:
Check out the SMSTS.log file on the Client or the SCCM Reports.
Packages referenced by a running Task Sequence
and
Task Sequence Advertisement Status for a specific Client
LCNWAuthor Commented:
How do I check the log file on the client if the install failed?
Angular Fundamentals

Learn the fundamentals of Angular 2, a JavaScript framework for developing dynamic single page applications.

merowingerCommented:
logon as local Administrator...is this possible?
WyoComputersCommented:
Go to deployments and check the status.  See if it failed or not for the install... It's logged there in summarization.
LCNWAuthor Commented:
I figured out the issue. The OSD didn't like the partitions on the hard disk as they arrive from the factory. Unbelievable!

I ran gparted and wiped them out. You could also use a windows setup disk and delete all the partitions.

After this, the task sequence ran fine. I hope this helps others.
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 2012

From novice to tech pro — start learning today.