Does anyone have any ideas why the web reports for task sequences will show data, and then the data disappears. For example I usually run the web report "Status summary of a specific task sequence advertisement" and usually this will show all the machines that are either "running" "failed" or "succeeded". But usually the "succeeded" disappear after an hour or so. And sometimes when I'm monitoring a "running" task sequence because I'm testing a new one I keep hitting F5 to refresh and it usually works, but then sometimes all the data disappears and it shows "no matching records could be found". The report is based on the advertisement ID, which hasn't changed (I haven't created a new TS advertisement). Any ideas?

i replied to this exact same question before here, does that help ? My step by step SCCM Guides I'm on Twitter > ncbrady

Thanks for the info. I guess it helps, at least I'm not crazy, if others are seeing it as well. What report were you trying to reference, for me "ReportID=295" brings up "Scan 1 - Last scan states by collection" under the "Software Updates - D. Scan" category.

report id's change from site to site, i was referring to the same report as you My step by step SCCM Guides I'm on Twitter > ncbrady

You can use this script/method to copy the report in the form of an HTML file, at the end of the TS! I use this all the time at my customers! http://blog.coretech.dk/mip/getting-a-hardcopy-of-the-ts-progress-report/Michael Petersen My Deployment Blog - http://blog.coretech.dk/mip

Good info, thanks. It's a shame everyone still has to jump through circus hoops like this, 4 years after the product was released. And the next major version is on it's way, with all of its own unique bugs, so I don't expect this to be addressed ever :(

Has anyone found a resolution to this? Are the status messages even in the DB? Is the report bad or is the data just not there? I have a system that is running a sample TS that has a few steps in it and it's STILL not returning data. It's not a rebuild, it's just a task sequence that runs a few commands using some packages and is forced to exit with success. Not sure why this has been an issue all along and it's never been addressed. nick