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.

Currently you can only configure Boundaries based on IP Addresses or AD-Sites.
However, in some situations it would be great to have more Options.
For example, if you manage Clients in multiple protected NAT Environments.
It´s possible that multiple sites/zones use the same IP Ranges, so you cannot configure Clients to use local DPs.
A possibility would be a Reg Key like HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM:AllowedMPs, but for Boundary Groups.

Custom folder created during package creation should also get deleted from DP when the package is being deleted.
As of now whenever a package is deleted from console it deletes the content of the folder but leaves the empty folder itself.
These empty folder has to be manually identified and then cleared from the DPs.
This process of identifying and deleting empty folders is cumbersome specially when having large number of DPs and requires special attention while doing in order to avoid removing any of the working folders mistakenly.

Whilst i know the feature for phased TS deployments is only pre-release in 1802. It'd be super useful to be able to add additional collections into phased deployments as opposed to only being able to use 2 collections.

I regularly run 4/5 phase deployments to the enterprise, and in some cases office by office. Having phased deployments support more than just 2 collections would be a massive time saver.

You can not configure rate limits on pull distribution point only on non pull distribution points. this is an issue In many environments. please add the rate limit function to pull distribution point

Please add support for Windows 10 client to be a WOL proxy!
Today Windows 10 clients cant be a wake up proxy, "The supported clients are Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012."

Kind of sad its not already supported!

Regards
Robert

We noticed 2 things making it impossible for us to use Peer Cache:
In CB 1702, we noticed that clients contacting the Peer Cache Source only attempt this via HTTPS.
This doesn't make sense, especially because we (and most of the other customers we know) use HTTP for the entire SCCM infrastructure.
Furthermore, in the client settings the option to switch from HTTPS to HTTP was obviously forgotten - it's missing.

Is the PG aware of this, and can we expect the issues will be fixed in CB 1802?

Please create a setting (perhaps hierarchy or site) that allows an administrator to define the default content priority by content type. The current system default of Medium is not always appropriate and making this configurable could be a big help. The setting for this is already contained in WMI for most content types so creating a configurable setting in the console should be relatively trivial.

At the moment when setting up a schedule for Distribution Points to do their syncing the timezone being used is the one from the primary site server.

when having DP's over multiple continents this brings some advanced math to get the sync done right :p

Would there be a possibility to use "Use DP local Time" as with advertisements ?
Or maybe in the schedule tab on the DP properties have a dropdown list with for example "you are now scheduling in GMT+1" where you can select a list of timezones so it does the calculations for you.

When viewing the client data sources report, it would be nice if the items in the boundary group list box were alphabetically sorted.

when we want to schedule an update for a package, if you enter a previous date than the current one (due to an error) you don't receive an advertisement message telling you that date is anterior. If you click OK, then package is update immediately!

Thank you

Currently the smsdpusage process does not honour the DPs preferred Management Points for the submission of the usage report. Instead, it appears to pick the last MP listed in the following registry location, HKLM\Software\Microsoft\SMS\DP\ManagementPoints. In some cases this MP may not be reachable and as a result no DP usage reports are submitted to SCCM.

Today, when you remove an object from ConfigMgr (Package, application, etc), the content remains in the local client cache (if it was ever downloaded). In an effort to clean up that old content, I think it would be a great idea to automatically cleanup content. For example, once I delete an image from the admin console, I will never need it again on my client systems, so go ahead and delete it from any system that has it in the cache.

(I currently use TidyCache to remove 'old' cache', but would prefer that this be handled natively by ConfigMgr. https://gregramsey.net/2015/11/17/tidy-cache-clean-up-old-ccmcache/

It would be really nice if we could use Git as a source for Application and Packages.
Then we would have the benefits of Git, with version-control, check in and out, who did what, and why and so on.

In Monitoring, distribution status, client data sources, need to be able to select any boundary group. This is currently limited to 25. The greatest amount of data transfered

Allow administrators to configure Peer Cache clients with a list of DNS Search Suffixes, or for it to reference the local machines.

Currently I'm unable to use Peer Cache because client attempt to reach fellow clients via the FQDN which for xyz reason is unreachable. If it simply followed the DNS Search Suffix list, it would be able to contact them.

So as to minimize business impact during critical hours of the day where WAN impact can have significant outcomes. By being able to schedule when content distribution will start can greatly assist in this regard

DP's occasionally fail to get content because it has not got to the site server. Updating or redistributing does not fix this situation. The ability to refresh site content would be helpful. See https://social.technet.microsoft.com/Forums/systemcenter/en-US/312d86e3-e793-4147-97a7-7785295e4986/problem-with-stuck-distribution-points?forum=configmgrgeneral for a work around which is messy.