Ideas
What features would you like to see?
All of the feedback that you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Microsoft Endpoint Configuration Manager, though we can’t promise to reply to all posts.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
-
Queries vs Collections
We have also experienced "Collection Creep". A tool would be handy to view/delete collections from a search criteria, e.g: No Memebers, No Deployments, no membership change in 6 months.
4 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This feature is added in the soon to be released #SCCM 1902; via management insight rules to help you clean up unnecessary collections.
-
Allow Client Notification actions to be triggered from the Devices node.
Please allow Client Notification actions to be triggered from the Devices node. You currently can only do this from Device Collections.
35 votes -
Correct the "Add Selected Items" ribbon button functionality
Currently when you select a collection(s) in the console, then utilize the "Add Selected Item" button you are able to functionally add the collection(s) selected to another collection as a member, however it does not actually add the member of the selected collection(s) to the target collection just the root collection itself.
Example A:
1. Open Console and navigate to Administration \ Assets and Compliance \ Device Collections \ Select a collection.
2. Click the "Add Selected Items" button and then "Add selected items to existing device collection"
3. Select the existing collection that is to be the targetThe…
80 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
We’ve taken some changes to improve this. But we believe the remaining behavior of the ribbon being context sensitive to be the correct action. This is the standard design behavior for ribbon context specific behavior.
-
Improve addMembershipRules implementation for large direct membership collection or provide Stored Procedure to do the same
Today we use an automated process to populate our device collections with machines from a fore-front configuration system.
After we had exceeded 250000 machines in some collections adding new machines to these large collections has become a real pain. Meanwhile it takes from 40s to 7 minutes to a add a single machine. The SCCM console cannot be used anymore for large collections. It crashes with OOM when the collection is opened or a new computer is added using right click.
Interestingly execution times don't really differ in terms of the number of machines added in one call of the…
21 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Performance for editing direct mem collections is greatly improved now.
-
Collection Query re-design request
I am looking the issue/design from SMS 2003 to SCCM 2012 version. I am not sure if any purpose must be behind of this design of collection default query select * from smsrsystem.
Whenever a user create the query based device collection, if there is any modification in the query
He/she shouldn’t remove the entire query and apply OK.
If user applies ok, its automatically select * from smsrsystem query will enabled, it will targed to all system which is “All system” as limiting collection.
It has serious issue in most the companies, deployment is performing…129 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Fixed in #SCCM 1902 which shipped today.
-
clouduserid not displayed correctly
Clouduserid in console is displayed with Chinese characters instead of the string from database
7 votescompleted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
This should be fixed in our next hotfix rollup for 1710. Thanks for reporting this.
-
Fix the renaming of collections
The following behaviour should be fixed
- Create 'Collection A'
- Create 'Collection B'
- Go to the properties of Collection A. Under Membership Rules, go to Add Rule and select 'Include Collections'. Choose 'Collection B'.
- Rename 'Collection B' to 'Collection C'.
- Note that under the Membership Rules, Collection C is still referenced using it's old name.
When a collection is renamed, this change should also be reflected under the 'Membership Rules' of other collections.
24 votes
- Don't see your idea?