[sccm 2012] SCCM 2012 - Task Sequence Error

[dobsonl]

Hi

 

We are starting to use SCCM 2012 to deploy & manager applications on windows 7. When creating the task sequence to build and capture the windows 7 image we get a error after it has downloaded the wim from the server and prior to it applying to the workstation. The error is 0x80004005 and says to refer to the system administrator.... only problem is this seems to be a general error from googling anybody seen this before?

 

I have found that this also affected 2007 version...

 

Thanks

Luke

[synaesthesia]

Most common cause for that would be that not everything required has been sent to the distribution points. Also check permissions for source files etc. Use cmtrace.exe to follow SMSTS.log and you'll be able to see the reason.

[ChrisH]

That error is fairly generic as I have found out. Get the log out of the temp directory and not the one in the directory on the C: drive. I found the one on the C: drive folder was not updated with the actual problem but the actual error was highlighted by cm trace on the copy from the temp directory.

[dobsonl]

Thank you @synaesthesia i hadn't actually sent the task to the distribution points!

 

All seems to be working (fingers crossed)

[synaesthesia]

Easy mistake - done it myself Best way to learn!

[dobsonl]

Its just something you don't think you would have to do when everything is on the same server...

 

I may need to call on your help in the future got a feeling I got a steep learning curve before teaching the other techs.

[synaesthesia]

I'm probably at the same stage you are tbh - a good eye on Technet and windows-noob.com are getting us through though

[rcadmin]

Thank you @synaesthesia i hadn't actually sent the task to the distribution points!

 

All seems to be working (fingers crossed)

 

Hi,

 

Would you please guide me what do you mean by saying "task not sent to DP" ? I am getting same error and not able to fix it as yet.

 

Thanks in anticipation

[synaesthesia]

For software to be able to be deployed to any workstations, it first needs sending to the distribution point(s). So once a task sequence is complete, you can right click it and select distribute (you can also "update distribution points" which is useful if something's changed or you're worried the original task sequence and/or it's relevant files have gotten corrupted). Only once the software and task sequences are available on the distribution point can it be successfully deployed.

You can check in the distribution point properties what packages, software, updates and task sequences are available.

[gshaw]

There's a neat little script I used to use that will check any Task Sequence to make sure all content is available on the Distribution Points. If I find it I'll post back with the link

 

Edit: here it is Using PowerShell to Check Task Sequence Package References for a DP

[rcadmin]

Thanks. Actually the driver set I was using had a corrupt driver, I believe. I removed drivers and added only required drivers and it has fixed my issue. Though I was getting the same error as you mentioned in your first post.

 

Thanks for your response.