This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 87%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBR%3C/text%3E%3C/svg%3E)
i packaged a new software version for an app and my deployment contect never reached the dp. after looking i noticed the "size mb" field is 0. on the old version it was 118 mb. i copied all of the files (except the new version installer) straight from the old file on the sccm server. i have the deployment configured the exact same way. distmgr.log just shows it sleeping the deployment. no job show in dpmanager. i repackaged and the same thing happened. the only thing out of the ordinary that i did was copy the same installer script from the original location to the new. after this i even packaged something completely different and it had the same issue
This issue is related to SCCM, I have changed the tag.
i came back the next morning and this had fixed itself.. thanks for the help
Thank you very much for the update and we're glad the problem is solved now. If you have any questions in future, we warmly welcome you to post in this forum again.
Have a nice day!
Hi, @masoncox-5152
Thank you for posting in Microsoft Q&A forum.
Sorry, I have some doubts about your issue description. Are you using Packages to deploy application?
What is the Content Status of the application?
And what sccm version are you using and where is the screenshot from? could you please have a more complete screenshot?
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.
Look into Distribution Manager component in Monitoring VIewer. It should give you better/faster insights than the distmgr.log.