Capturing logs during failed Task Sequence Execution

July 16, 2008 at 6:25 pm in ConfigMgr 2007, migration, SCCM 2007 by Kenny Buntinx [MVP]

Steve Rachui: Every OSD administrator knows the feeling of configuring a complex (or even simple) OSD Deployment, testing and releasing – only to have the deployment fail. At failure, OSD will begin a countdown to reboot and, on restart, the logs are often lost and we administrators are left wondering what went wrong. To find out we have to start the deployment again and spend time waiting for the failure. Wouldn’t it be cool if we had a way to automate forcing OSD to collect logs when it fails before exiting? Good news! :)

I have spent some time recently working on just how to do that and we have two examples – both use the same approach but one is for generic task sequences (those sent through advertisements,etc) and the other is for OSD deployments. Lets start with the generic one, explain the needed steps and the show how we incorporate that into OSD.(continue at source)

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest