Make global conditions usable for all types of Deployments (Maintenance Windows, Power Settings, Compliance Baselines,...)
It's crazy how many different manually-made Collections I have just for targeting a Maintenance Window to match a particular department's needs, then also Power Settings, then their Compliance Baselines, then their Apps. Wouldn't it be better to just push evaluating applicability for all that out to the clients and free up server resources?12 votes
Allow us to leverage a configured account for connecting to content source locations for packages, applications, updates, boot images, ect.2 votes
It would be great for troubleshooting if the download location where content is actually downloaded from would be send to the MP as a status message. Some might not want this Information, so please make this a decision each admin can enable/disable.7 votes
If a Pull Distribution Point is throttled, this affects the remote site system from a client perspective, so its client downloads are throttled as well (even though those downloads may essentially come from itself).
Throttled download jobs, as the system is functioning as a Pull DP, should be separated from throttled download jobs as the system is functioning as a client/agent. I'm not sure how this can be accomplished; it may have something more to do with BITS than something internal to ConfigMgr, but it would be welcome.1 vote
If CM-Agent installed on a Win10 Client it should be automatically add his first DP to the Posh as a register-PackageSource Repository, that we can Use that Command to install SW with the add-package command from a App-Deployment type, in faster cases to install SW on a client with remote Powershell and also registered in the Monitoring Workspace as installed, maybe in background the Posh adds the client with direct membership to the right collection that we lose no information's about that.7 votes
Currently Pull Distribution Points may not be able to report their status to a given Management Point in their site (i.e., a remote site system in a DMZ). To reduce delays, I think a Management Point option should be added for Pull Distribution Points so administrators can choose which MPs a Pull DP reports to instead of having all MPs loaded into the registry (the ManagementPoints string value). The UI could look similar to the "Source Distribution Points" tab within a Pull DP's properties. Multiple MPs could be defined with priorities. If an administrator didn't define this, at least one MP, perhaps one in the same domain as the site server or site database server, would be filled in by default.
Currently Pull Distribution Points may not be able to report their status to a given Management Point in their site (i.e., a remote site system in a DMZ). To reduce delays, I think a Management Point option should be added for Pull Distribution Points so administrators can choose which MPs a Pull DP reports to instead of having all MPs loaded into the registry (the ManagementPoints string value). The UI could look similar to the "Source Distribution Points" tab within a Pull DP's properties. Multiple MPs could be defined with priorities. If an administrator didn't define this, at least one…1 vote
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
To reduce the attack fingerprint of servers it would be good if you could deploy a distribution point on server core.9 votes
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
Reboot configurations are set per-client. I would like the ability to do this per-deployment. It can currently be done through creative collections, but it's time-consuming to maintain. Just adding a couple of fields to the deployment table for reboot override behavior ought to do it.3 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
- Don't see your idea?