Currently when you wish to adjust Pull DP settings you need to do this through Webmtest, Powershell or VB script. Example adjusting the retry times or retry interval.
It would be nice to take the most commonly used settings that are adjusted from review of the ConfigMgr cases and place those settings into the ConfigMgr console to make the Pull DPs more robust, manageable and a richer experience.1 vote
Make sure that WMI information about packages gets rebuild after a WMI restore, so that Content Validation of packages doesn't fails.
If a server for some reason isn't turn off gracefully, an automatic repair would happen, and thereby all packages information is gone in WMI.
Event ID: 5616
The Windows Management Instrumentation (WMI) repository was successfully re-created by the auto-recovery mechanism.6 votes
It would be nice to be able to adjust certain settings of a distribution point after its been configured.
The primary and secondary drive for the content library and package shares.
The drive space reserve
The host name2 votes
Reduce the amount of time between when content distribution is completed on a Standard DP and when its Pull DP begins to transfer. Consider using some type of notification to the Pull DP that it may begin instead of having it just wait when it could be pulling.1 vote
When removing a package from a ditribution point, remove it from the DP's single instance store as well
We've removed a 6GB .wim operating system image file from a distribution point to which we didn't intend to distribute it to. Although we've successfully removed it from the DP using the admin console, the file is still present on the DP in the single instance store, and thus 6GB of disk space appears to be permanently wasted.
Dear sccm Team,
we have a lot of middle sized Locations with max. 2 Mbps Connections that hold distribution points and we often have issues replicating. It would be great to leverage something like DFSR (with cross file remote differential compression). Also it would be great if we finally could copy single files between DPs when there were issues during DP update for a package. Wouldn't that be possible with a small command that verifies checksum and updates the CM database Information.
By providing this settings, it would ease up massive distribution of a package to many PullDP.
A setting similar to Concurent download on DP would be perfect!
As of now, updating a package hosted on 1000 PullDP will trigger all PullDP at the same time to update the package.
This cause high CPU and IO on the server as well as potential network load.20 votes
The best way to control this is make a mesh of pull-DPs, and have some pull from other DPs… as opposed to all from the siteserver. That offloads network bandwidth from the siteserver
Content Locations tab in a package properties allows to Validate, Redistribute and Remove a Distribution point. If you need to add a new Distribution point, it should be done via Distribute Content option of the package.
It would be great to have option to add new Distribution point on the same Content Locations tab.3 votes
while creating boundary it should search with the existing and findout if the admin try to create same boundary1 vote
If a Distribution Point server or server hosting the Content Location is restarted, the content transfer is not resumed to the Distribution Point. The content transfer should resume to the Distribution Point after the restart is complete.11 votes
Sometimes the admin isn't local to the Primary site. This can make creating and uploading packages a painful process. Allow an admin to upload that shiny new WIM package to a local DP and have the DP be capable of pushing back to the "hub" that is the Primary Site. This will allow much faster uploading from the admin perspective (content available immediately locally even if not for hours at other locations).
This one may be a pipedream ... but it's one of the last hurdles to never installing another Primary if you're sub 100k devices.2 votes
Set up distributions of content that hit one DP Group, then another automatically and so on.3 votes
An option to configure a DP such that it only downloads the distributed content from the site when the first client requests for it.
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.0 votes
Ability to move Distribution point from one secondary site server to another secondary site server' has been merged into this idea
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.0 votes
Have a built in script that will export an as built document.
Items to export and put into visio docs:
Each server config and HW specs
Boundary group summary and DP's associated.
Highest used Limiting collections and AD user groups with modify access.
Slowest SQL queries and scheduled run frequency
Number of devices using a DP.
Data growth rate for 1 year.0 votes
When updating content, don't automatically remove the old content on the DP's until the copy starts. Sometimes what happens is if there is a slow content transfer already taking place. The new content update waits for it to complete before it starts the transfer, so during that time the old content is not available (causing task sequences, packages, and applications that use the content to fail).0 votes
Can you allow add the ability to deploy Office 365 using the Office configuration service provider: https://docs.microsoft.com/en-us/windows/client-management/mdm/office-csp0 votes
Could logging for content library be improved.
Recently had a situation where the ini, sig files weren't created in the FileLib. Noticed the logs weren't helpful when it came to actions managing the content library on distribution points. This made resolving difficult.0 votes
- Don't see your idea?