Trouble redeploying an Image

[TheCDay]

We have a task sequence that deploys Windows 7. I deployed a machine and found that the task sequence did not include all the drivers for the specific machine. I added a driver package to the task sequence and setup a new deployment for the machine. The machine boots to the initial SCCM screens (the DOS type screens) and then reboots and goes to the windows 7 login screen without going through a deployment. Im not sure whats going on here, is it not imaging, is it trying to apply the new drivers without reimaging the whole machine, but I have the wrong ones....

Any help would be greatly appreciated.

Scott C

 

Also sorry if this has been asked before, I didnt find anything like it when I did a search.

[TheCDay]

I tried removing the "reboot to windows PE step" and that did not help....

It does have those conditions although it does not have the "success codes" area at all though I think thats just a version issue.

Here is a dropbox link to the SMSTS.log file. https://dl.dropbox.com/u/65384/smsts.log

[binarymime]

These are your two problem lines as highlighted by CMtrace / Trace32:

 

It looks like the TS cant find the following package ID that it references

 

Failed to find CCM_SoftwareDistribution object for AdvertID="P0120080", PackageID="P0100037", ProgramID="*"

 

Subsequently if a TS dependancy cant be found it will reboot the TS immediately as stated by the following:

 

Failed to resolve selected task sequence dependencies. Code(0x80040104)

 

Thanks

[binarymime]

Further I would add that the Driver packages that you added were probably not distributed correctly to your distribution points as that is all that you changed in the TS between it working and not working, I assume one or both of the driver packs are what the TS is failing to find as referenced by:

 

Failed to find CCM_SoftwareDistribution object for AdvertID="P0120080", PackageID="P0100037", ProgramID="*"

[TheCDay]

That was exactly it. Thanks for the help !

[binarymime]

your very welcome, cmtrace and trace32 will be your friends, if you open .log files with either it will highlight errors in red and makes troubleshooting a breeze, from that point its just knowing which log files to check, 9 time out of 10 Task sequence troubleshooting can be narrowed down by checking smsts.log