Failed Dependencies

[mherby]

If a task sequence fails to start due to not being able resolve all task sequence dependencies, is there somewhere I can check to find out what dependency its failing on? The SMTS log is not created at this stage of the task sequence, it often seems to happen when I try and run a task sequence too quickly after setting up a software package, I'm just wondering out of interest really. Thanks.

[Vancouverite]

I've had Task Sequences fail on me for exactly the same reason. Once a package has been created and sent to the DPs you just have to be patient and wait a while before trying to run any TS that calls it. But are you sure that the smsts.log hasn't been created? In my experience one is created as soon as the Task Sequence starts and I have successfully used it in the past to identify failed dependencies.

 

The location of the log does change and it can be found in different locations depending upon how far along in the imaging process you are:

 

 

• Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log

 

• Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

 

• Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

 

• Full version Windows (x86) after SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log

 

• Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

 

• After Task Sequence has finished running (x86): c:\windows\system32\ccm\logs\smsts.log

 

• After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log

[mherby]

Thats great, I wasn't aware of all the log locations so thanks for that.