As of now when an enterprise thinks of upgrade, we have only one thing to do before (TestDBUpgrade). This makes sure if the DB is upgradable. But what if the Upgrade fails at the next step (Copying files). We don't have an option to again run the upgrade only from that step and running from beginning will not work as DB is already upgraded it will fail to find some objects. If this is a CAS site this means you have to again go back to a previous version and recover it and make sure the sites in the hierarchy come out of the DRS issues which is a big task alone. So the ask is to either make the upgrade to continue from the steps that it failed after the DB upgrade or to create a tool which can verify the whole site for an upgrade success before we can actually do it.
As of now when an enterprise thinks of upgrade, we have only one thing to do before (TestDBUpgrade). This makes sure if the DB is upgradable. But what if the Upgrade fails at the next step (Copying files). We don't have an option to again run the upgrade only from that step and running from beginning will not work as DB is already upgraded it will fail to find some objects. If this is a CAS site this means you have to again go back to a previous version and recover it and make sure the sites in the hierarchy…5 votescompleted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to completed. This was addressed in SCCM 1606 production build, released yesterday
I think it would be great if SCCM could have a configurable value in registry for TFTP windowsize just as it has with TFTP blocksize. Both WDS and bootmgr.exe seem to handle it but there is no easy way to get this option into the generated BCD file upon PXE boot. Seems like a low hanging fruit.70 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Fixed in SCCM 1606 Production – released yesterday.
Configuration Manager is a great source of information for organisations. The problem with this repository of data is that it requires someone to take advantage of it. Reports or queries need to be generated by someone who knows what they are doing. Connecting Configuration Manager to PowerBI or providing an OData interface would allow Configuration Manager inventory data to be more easily accessed and used20 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
I’m marking the powerBI aspect of this completed. If you want the OData portion, please vote on that idea linked below.
I'd like to see a "Description" parameter added to the Get/Set/Add CMDistributionPoint cmdlets so descriptions can be programatically added w/o having to try this through separate WMI cmdlets.4 votescompleted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
This is completed in the 1604 release.
I know Windows 10 is bringing much better support of HiDPI, but I don't believe the console is taking advantage of those enhancements.
Most of the console renders OK on HiPDI screens, but there are many windows that are simply unusable due to improper support of scaling. The examples I've attached are from a 4K monitor at 150% (which is the default for Windows). This issue also occurs on HiPDI screens on laptops like the Dell XPS 13.190 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This is completed in ConfigMgr 1706 production release, publically available soon.
When a user installs updates from Software Center only the updates that were selected to be installed are evaluated for their state post reboot. The whole deployment those updates were in, even if all updates in the deployment were selected, will not be queried for compliance post reboot. This causes a delay in the deployment compliance reporting as you need to wait for the deployment to be evaluated on schedule. In some instances this could be days. Running evaluation on the deployments those selected updates were in post reboot would solve the reporting delay.11 votes
SCCM 2012 R2 - PowerShell Commandlet needed to remove Updates from Group (Add-CMSoftwareUpdateToGroup exists)
Hi all, my customer is using the PowerShell on a really high level to automate nearly all his ConfigMgr Patchmanagement Tasks. They are using Add-CMSoftwareUpdateToGroup but they're missing the matching Remove Commandlet.10 votescompleted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Remove-CMSofwareUpdateFromGroup cmdlet has been created and should be in the latest technical previews.
Add the possibility to set an operating system requirement on program for legacy package. The cmdlet set-cmprogram has no switch for that.0 votescompleted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We have updated New and Set-CMProgram to allow for configuring operating system platforms. These changes should be in the 1701 technical preview.
When you uninstall an application and the content for all the deployment types is not in the cache then the entire content will be downloade
When you uninstall an application and the content for all the deployment types is not in the cache then the entire content will be downloaded again even if this is not required for the uninstallation routine.
The client should be able to determine whether or not it needs to download the content before initiating an uninstallation.13 votescompleted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
Install and Uninstall content can now be specified separately. Thanks for the feedback!
A truly great feature would be to be able to customize all dialogs show to the end-user, both for OSD, but also reboot prompts basically all dialogs shown to the end-user.
Adding a company logo so that the end-user actually knows it is from our company and trustworthy.601 votescompleted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
ConfigMgr 1610 is available today and branded dialogs with company log is included. Thank you everyone for your feedback on this!
Request for intelligent MP, SMP and SUP selection based on network location, like current DP selection
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.49 votes
Boundaries have been rearchitected and improved from 1610, 1702, and now finally 1706 production releases.
Add a button in Software Center so the user can update the MAchine and User Policy. Would be a great feature for the end-user when waiting for an application to be available!118 votes
This is completed and available in our 1602 release https://blogs.technet.microsoft.com/configmgrteam/2016/03/11/now-available-update-1602-for-system-center-configuration-manager/
Now that we have the option to define both Distribution Points and Management Points as preferred, it'd be terrific if we could have the same option for Software Update Points. It would make a strong case when designing a flat hierarchy.604 votes
With 1706, there is no much more control over SUPs and mapping to Boundary Groups. There is one more item left, which will allow control to failover (timeout) faster than 2 hours:
Everything else for this item is completed in 1706.
We would like to see a single web portal, preferably HTML-based, to marry the Software Center and Application Catalog. We deploy both types of offerings, and a single place for users to get new software would be great.416 votes
This is complete and available in our 1511 release. Thank you all for your suggestions and feedback!
Would be nice if the application approval request feature had built-in support for emailing.389 votes
This is now available in the 1810 public release. https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1810.
Thanks for all the feedback!
When upgrading your site with a CU, have the clients automatically upgrade as well instead of creating a Package Deployment.402 votes
SCCM only supports up to version 6, latest hardware uses version 10.
SCCM provisioning uses SOAP which was deprecated by Intel.
This is now a big hassle for people who want to use Intel Vpro in combination with SCCM. We need to make use of an Intel Add-on (Intel SCS) to get things working but it’s far from ideal.
Please bring back the provisioning support compatible with the latest versions of Vpro and bring support for new features such as KVM.151 votes
In order to support customers as the speed Intel is update Vpro/AMT – we worked with Intel for them to own the integration, and support latest versions (as ConfigMgr itself only supported up to version 6.) Intel has released an updated version that should solve the customer needs:
We will continue to partner with Intel to provide APIs they need for the integration.
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.61 votes
This is working now e2e in 1706. There is one more thing we’d like to fix, which is to have software center (optional software) to work through CMG too. We’ll track that remaining work with this UV:
To reduce potential for failures due to low battery situations and to minimize the ConfigMgr client's impact to system battery life, introduce a check for certain client actions to allow them to be delayed or bypassed when the system is found to be running on battery or running critically low on battery:
+ Software distribution
+ Compliance settings
+ Anti-malware scans36 votes
We’ve completed some major battery power improvements in SCCM 1606.
SCEP policies do not have the ability to set security scopes. This is a problem because our SCCM is shared by several departments and colleges in the university. For example, someone may inadvertently (or intentionally) modify a policy for DCs which can have a catastrophic effects. Having the ability to set security scopes will restrict who has access to individual SCEP policies.51 votes
Thank you all for the comments and feedback. This is now in CM 1511 release.
- Don't see your idea?