With 1610, the Cloud Management Gateway feature arrived. Although it's a Pre-Release feature, as Cloud Solution Provider we're UNABLE to use/implement this. And so are our customers...!

When you try to set this up from the ConfigMgr console, a prerequisite is the Azure Management Certificate, which can't be configured as CSP-tenant because this needs the Classic Azure Portal (ASM). This is unacceptable for us, as CSP, as we would have to instruct our customers to get an Azure Subscription separately.

https://blogs.msdn.microsoft.com/cie/2016/11/28/azure-management-certificates-and-publishing-setting-file-with-csp-subscriptions/

Beginning with 2012SP1, we have the ability to add a CAS to an autonomous primary site. It could be interesting to reverse the proposition by having the ability to remove a CAS above a Primary when a CAS is no longer needed or has been set for a wrong reason.
I know that it could be done through creating another hierarchy and using migration tasks by this is quite difficult for it requires additional hardware.

as KB 3095113 is required to do Windows 10 servicing and as WSUS 4.0 requires that hotfix in order to correctly display the Upgrades classification, the prereq checker should check for this hotfix and if it's not detected warn the user along with a URL linking to a guide explaining the correct order to install the prerequisites for the hotfix and that the hotfix needs to be installed directly after installing WSUS.

Hi,

PKI- Make V3 Template compatible with SCCM Current Branch.

Older version of windows server are falling out of support, or are deprecated for ConfigMgr current branch. i.e. Windows Server 2008 and 2008 R2. Support an easy way of upgrading those operating systems to newer versions of windows server.

We should be able to deploy SCCM Gateway servers for deployment to DMZ, Internet and Remote locations where opening ports to the management servers / domains are not feasible. We are unable to forward ports from the internet to our LAN and must use a DMZ. There is no way to implement SCCM for IBCM because of this.

This is a DCR requesting that we improve the logic around MP, SMP and SUP selection by clients. Currently, we gather AD Site and IP Subnet details for DPs, store that in DPInfo and include that information in the XML body returned on content lookup requests. Why can we not do this for other server roles so that the client can choose the best server to connect to based on matching AD Site and/or IP Subnet? This would provide a far better solution than having to populate AllowedMPs, too.

If you have deployed offline Service Connection Point, ServiceConnectionTool.exe now (in ConfigMgr 1511 - 1606) downloads ALL published ConfigMgr update packages when you use -connect parameter. E.g. if your site only requires post 1606 hotfix, ServiceConnectionTool.exe downloads 1602, 1606 installation packages although they are installed! Currently it will download over 7 GB of updates, when you just need about 25 MB update package. This is just waste of time, network traffic & disk space.

Please improve ServiceConnectionTool.exe, so it would only download the update packages that are applicable for the current installation.

Enable appropriate distribution point functions on Cloud DPs like Group Relationships, Content, Boundary Groups, Schedule, Pull Distribution Point, and Rate Limits.

of course, PXE and Multicast would not be appropriate Cloud DP functions.

better control weather I want a site to fallback to primary or not.
real bandwith limitation instead of current posibility. Control priority of metadata

both in online and offline modes of the Service Connection Point, when installing 1511 and then get the updates, ConfigMgr downloads 1602, 1602 hotfixes and 1606 EasySetups (and all of their prerequisites) when in 99% of the cases - we only need the latest release.
this causes a lot of time waiting and bandwidth usage for nothing and it will probably get worse as there will be more future release.
we want an option to choose what release to download instead of download them all

As the final step in Updates and Servicing, remove previous installer files for current branch builds and superseded hotfixes from %ProgramFiles%\Microsoft Configuration Manager\EasySetupPayload or add and enable a scheduled cleanup script/

Also there are now 3 locations with the full installation source files:
%ProgramFiles%\Microsoft Configuration Manager\cd.latest
%ProgramFiles%\Microsoft Configuration Manager\EasySetupPayload
%ProgramFiles%\Microsoft Configuration Manager\CMUStaging

Please don't forget about those of us who work in an environment where we can't connect to the Internet. I've been very concerned by Microsoft's cloud-first effort turning into cloud-ONLY effort.

Support for renaming a site server. Our stand-alone primary site server is the last server named by our old server naming conventions.

Add a way to perform a site restore to a system with a different name (but keep the same site code). In the event of a Datacenter Move, often times we are not allowed to retain the same system name (location based naming) and we end up having to stand up and entire new infrastructure and migrate.

While this is doable, it's tedious work and when operating in a Hybrid scenario with Intune, it means that we have to re-enroll the Intune managed clients to a new management authority. It's a whole lot of pain.