Be nice to see the Pending column as a default column instead of adding it each time.

redistrib pending packages in Content Library Explorer

In the Content Status node of the Monitoring workspace, add an option to allow all failed content to be redeployed without having to go into each package/application and selecting redeploy. When a site has numerous packages that have failed to deploy, having the option to easily redeploy all of the failed content (or specific packages) at the same time would very useful.

Smsdpmon.exe appears to only use the local SCCMDP class for the list of content to validate. We have experienced a few cases where the SCCMDP content list does not match what is assigned at the site level. For complete validation can it also query the primary server for the assigned content and then flagged the differences as well???

GetCacheInfo Additional information exposed

Can you please have the data available in WMI or ComObject include additional fields.
Currently:
ContentId
ContentVersion
Location
LastReferenceTime
ReferenceCount
ContentSize
CacheElementId

Could you add information from the Package Fields in the Console:
PackageName
*PackageVersion
PackageLanguage
PackageDescription

I'd like all of them, but I really need PackageVersion for a project I'm working on.

I would like an easy way to see who last replicated a package in the console in the drop down list options.

Export and import boundaries

Add a status of 'Skipped, prestaged content mode' or 'waiting, maintenance mode' for content distribution. Distribution points in prestaged mode are skipped and not processed, yet the status states 'in-progress'.

An option to configure a DP such that it only downloads the distributed content from the site when the first client requests for it. This will help manage DP disk space efficiently as most of the content never gets used at a remote site but we do not know what's really needed in advance. With semi annual channels the content problem is getting worse each day.

Below is the config manager thread I had opened and an expert asked me to submit a request here.

https://social.technet.microsoft.com/Forums/en-US/c249e600-b781-43ee-9aae-0b0efb6ba078/question-about-sccm-content-distribution?forum=ConfigMgrCBGeneral

An option to configure a DP such that it only downloads the distributed content from the site when the first client requests for it. This will help manage DP disk space efficiently as most of the content never gets used at a remote site but we do not know what's really needed in advance. With semi annual channels the content problem is getting worse each day.

Below is the config manager thread I had opened and an expert asked me to submit a request here.

https://social.technet.microsoft.com/Forums/en-US/c249e600-b781-43ee-9aae-0b0efb6ba078/question-about-sccm-content-distribution?forum=ConfigMgrCBGeneral

Currently, when content for an OS Image, Package, Application, etc is being updated, that object is unavailable until the content update completes. This means that content updates for large items must be timed very carefully, especially when sending to remote sites.

It would be amazing if a Distribution Point could keep the previous version of the item available while the content is updating, then switch to the new content and delete the old after it's completed.

Currently rate limits only allow you to configure this for a 24 hour period.

Consider expanding this to allow a schedule based on the day of the week.

This would allow for remote sites to use 100% of their bandwidth during the entire weekend, but a limited amount during business hours.

It would be helpful to be able to prioritize the DPs beyond the two options available. This would be especially helpful for ADRs where we want to get the new content into our test DPs quickly, but pilot and production can replicate much slower.

Need ability to define global rule for all distribution point servers never use a USB drive. We have techs in the field plugging drives into DP servers and without the nosmson_drive.sms flag file and SCCM start using the USB drive distributing packages and then they pull USB drive after their work and the DP has issues.

Allow the Content Cleanup Tool to ignore issues such as Nested Task Sequences. Currently it is a known issue that Nest Task Sequences cause this error "This content library cannot be cleaned up right now because package *** is not fully installed”"

when we need to remove secondary site server or when need to rebuild secondary site server with another site code. A full uninstall and re install required for all Distribution points associated with that secondary site.
Also when we need to move a DP from one site code to another site code, it requires uninstall / re install….to avoid this it will be helpful to have ability to move DP’s between secondaries.

At SCCM you can validate Content only for one Device or you have manny work to validate Content at all Devices. With waork around right click tools you can validate content for all Devices. Implementing the right click solution and it will a better work with Content

While at the distribution point a hashed file method is used to keep different applications using the same file, the really need fro this, in my opinion, should be the client computers, we have faced a really annoying case where to install 4 different applications (visio, visio pro, project, and Office suite) the same group of files are used , Office 365 installer, so it cam be 2.5GB four times if all the apps have to be installed at the device. this has a severe penalty at the storage and the network at the user device