I have installed SCCM 2007 over the last couple of weeks in between other things, and I have now come to testing it and I have run into a problem.
I have created boot images, OS Images, task sequences and advertised. I have followed guides from on here and on windows-noob dot com.
I can boot a PC via PXE and then I see it download the windows boot PE image, and then I get the Initializing screen then I am presented with "Welcome to the task sequence wizard" (with no password ) I select next and then I get to choose the task sequence. This is where the problem arises, I get the message "Failed to run task Sequence" the task sequence cannot be run because a package referenced by the task sequence could not be found.
I have searched the web and I am lead to look for the logs on the client PC by pressing F8 and navigating to the X: drive I am unable to do this as the the machine just reboots and no end of pressing the F* button.
So does anyone have any suggestions on what to do next. I have included shots of the screen just to illustrate what I am seeing.
Attachment 13568Attachment 13569Attachment 13570Attachment 13571Attachment 13572Attachment 13573
Ok I have found out how to enable the F8 support
right-click on your boot image and choose PropertiesSelect the Windows PE tab from the properties, and place a check mark in "Enable command support" then click apply
If it can't find the package, then whatever packages you've included in the task sequence need to be sent to the distribution points. In SCCM 2012 you can also tick a box in the package properties to copy it to a shared area to do the same thing, may be there in 2007 also.
I have downloaded a program from Microsoft called SMS Trace and it shows the issues with the deployment from the smstslog file. It turns out I had not distributed one of the packages, I can now enjoy my weekend :)
One from System Centre 101 - double check that you distribute packages to DPs... usual error is the 8005 or 8004 for that one
I've got a handy little script I found that goes through your Task Sequences and lets you know if any of the packages are missing from DPs. Will post on Monday as it's saved me pulling hair out a few times now :)
CMTrace from SCCM2012 is an absolute godsend - suspect SMSTrace is the same thing :)
Hi Gshaw that would be really handy cheers, I also see quite a few of you are on SCCM2012 is it a easy upgrade or are you re installing?
Here we go :)
Using PowerShell to Check Task Sequence Package References for a DP
Just need to put the Powershell components in the required places and away you go!
This is also the original Technet article for reference
Make sure a ConfigMgr task sequence has all the packages it needs - Michael Niehaus' Windows and Office deployment ramblings - Site Home - TechNet Blogs
Thanks for that I am sure it will come in very handy