Task Sequence Statistics - SCCM Deployment

AdamKue 1 Reputation point

We have our 20H2 upgrade deployed as a TS, and the collection we deployed it to has a limiting collection of machines with 1909 OS. The purpose is so when the machine upgrades, it will fall out of the collection and no longer require the task sequence, since we have it rerunning every week to upgrade any failed machines. Here is the only issue though, we have seen over 30 machines that have successfully upgraded to 20H2, but still show as failed in the deployment statistics, over two weeks later. We are very confused by this, since the most recent attempt was successful.

How long does it take for the deployment statistics to update after a failed attempt, and then a rerun, which is successful? We are using the failure statistics to create tickets and reach out to users so sometimes we look silly reaching out when the upgrade was actually a success, just isn't updating in deployment statistics.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
37,746 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Simon Ren-MSFT 32,146 Reputation points Microsoft Vendor


    Thanks for posting in Microsoft MECM Q&A forum.

    ==>the collection we deployed it to has a limiting collection of machines with 1909 OS.
    Are you using a dynamic collection for the collection of machines with 1909 OS? If yes, the value for schedule a full update on this collection is 7 days (1 week) by default.

    So it may take 2 weeks (1 week for the rerun behavior and 1 week for the dynamic collection full update schedule) plus random delay to update the deployment statistics.


    Hope it helps. Thanks for your time.

    Best regards,

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.