Task Sequence Troubleshooting
I have a task sequence that installs OS, drivers and software just fine on most hardware. One a couple models of ThinkPad it installs everything except for ALL software applications. I proceed to the smsts.log file but there is only two lines of information which does not help. I have it setup in the TS so that all software is within a folder which currently is set to halt on error. I'm not sure how I should be troublshooting this. Previously I had all software packages/folders set to continue on error, but I found it was hard to catch items that didn't get installed for whatever reason. I find that the smsts.log file does not provide any sort of clue on what is going wrong. Any help is appreciated. Thank you.
February 10th, 2011 1:37pm

Under System Status -> Advertisement Status, locate the advertisement used to deploy the mentioned computer and look at all status messages. You can filter the result by computername to make it easier to locate where the error has occured.
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2011 2:12pm

I was actually checking that as well, but for some reason the computer name does not show up. It's also not showing up in the "Anything" collection...this is new... I've confirmed that the configuration manager client is installed.
February 10th, 2011 2:52pm

You say your smsts.log only contains two lines. Is there another log called smsts-<date and time>.log?
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2011 5:36pm

Yes there is and for the first time i've noticed that this log file has created some entries. Not much...but there is an error saying it "failed to set the log directory. Some execution history may be lost. The system could not find the file specified". I've also found that under advertisement history it is not picking up the new computer name just yet so it is being listed under "MININT-...." Last step that runs is a reboot for "Setup windows and ConfigMgr".
February 10th, 2011 6:15pm

Wht is the command of the task that fails? And does it indeed try to write to a non existant directory? If so, the obvious solution is to change the directory to one that you know exists on all computers.
Free Windows Admin Tool Kit Click here and download it now
February 11th, 2011 3:16am

Hello, In the logFolder on the client computer (C:\Windows\system32\ccm\logs\) could you find a EXECMGR.LOG file ? If yes, open this file. This log file contains more information about software installation (for example the Workdir used and the command line ran). Régis
February 11th, 2011 10:10am

Ah that log file is providing a lot of useful information. I should be able to work through this now...thanks to both of you.
Free Windows Admin Tool Kit Click here and download it now
February 11th, 2011 4:52pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics