Deployment stuck at 0% and waiting to begin installation

Sebastien Weiland 1 Reputation point
2021-03-03T12:01:41.39+00:00

Hi there,

It seems I got a problem which is a lot referenced everywhere, but need to dig a bit further...

Here is the problem on a specific device (so not a general problem server side):
73804-image.png

Usually, you dig into the ccm log files, and check boundaries and everything (bitsadmin to check the queue for example)

In my case, no problem but even with clearing the cache & rebooting, the status stays the same and the download is stuck

Only thing I find it some "failed to get content" but this is not even anymore in SCCM as I do not see any corresponding package apparently (in v_Content or v_Package):
Failed get the value of Content_058584a8-eb8f-446e-a9d7-966cf172c011.1
Failed get the value of Content_c2045698-6d7b-42e6-9b5c-d04815125fb1.1

I do not know at all why the client continues to look for these "contents" as they are not apparently available on the SCCM server, and also I do not have a clue on how to unlock this situation (I do not want to reset again the client, if possible to narrow to the root cause and find a solution instead...)

Thanks a bunch

Microsoft Configuration Manager
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Amandayou-MSFT 11,051 Reputation points
    2021-03-04T05:47:40.713+00:00

    Hi @Sebastien Weiland ,

    We could check if the content is replaced into DP already by deployment packages status. Please refer to the following picture:
    74102-344.png

    The display shown as green means the content has been replaced into DP already, if not, there may something wrong to distribute the content to from server to DP, we could check distmgr.log. Similar record is recorded in this log:
    74142-3445.png

    Besides, when the client shows downloading, we could check ContentTransferManager.log, it schedules the Background Intelligent Transfer Service (BITS) or Server Message Block (SMB) to download or access packages. Similar record is recorded in this log:
    74065-34.png

    74093-341.png


    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.

    0 comments No comments