Hello All, I've spent my fair share of time reviewing many a smsts.log post-OSD-failure and have generally been able to identify the root cause of failure. Unfortunately with my most recent failure this is not the case. I'm testing MBAM and it falls over somewhere around the installation & configuration of the agent during the task sequence. That's a problem, but the bigger problem is this: I can't figure out where in the task sequence it is failing.
Parsing the log in cmtrace, the last action I can find is a restart computer step at the very beginning of the State Restore phase and it shows successful. From there on, the entire smsts.log seems to be noise, and even though I know it completed a few other steps successfully (Use Toolkit Package, Set Status 4, Install Dell OMCI, etc) - I don't see any reference to them being started or succeeding. I never really had a great understanding of what smsts.log is actually logging, and although I've done a good job of muddling through them until finding the issue, I'm currently stuck. So my questions are these: a. How are all of you determining which step a task sequence fails on? b. Are there any good references to help me separate all the noise in smsts.log from the relevant information about current step, commandline, return codes, etc? It seems akin to looking for a needle in a haystack when diagnosing failures, but maybe I'm overlooking something? Thanks in advance, Andrew ________________________________ This e-mail is intended only for the person or entity to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the original message and all copies from your system. Statements and representations made in this message are not necessarily that of the Company.
<<attachment: winmail.dat>>
