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.
-
Improve performance on queries bases on custom inventory
Many customers are adding custom hardware inventory classes and build collections on the data collected. Today the inventory tables are not indexed by default which has a negative performance effect, especially in large environments. It would be great to have an opportunity to classify the most used fileds and ceate a index on them to speed up queries.
30 votes -
Nesting Distribution Point Groups
Allow Nesting Distribution Point Groups.
We have an issue with not always wanting to replicate all content to all locations due to content size and applicability, but to specific locations determined by function.
Examples:
Site A - Imaging DP Group. (Server DataCenter Environments)
Site B - Imaging DP Group. (Desktop Environments)
Site C - Imaging DP Group. (A mix of Environments and business units)These three sites have different business functions. So while not all imaging content would be the same across the board. It would be nice to have if you could nest those three Distribution Point Groups into…
28 votes -
Scheduled Restart on Device Collections
Add another tab for collection properties to have scheduled reboots.
- Weekly
- Daily
- Monthly
- Custom26 votes -
Security: Prevent or prompt for modifications to collection rules with existing deployments
We now have deployment verification to prevent damaging deployments from being created, but that doesn't stop existing deployments from being deployed accidentally.
It would be great to prevent or atleast prompt for any modifications to collection membership rules (large number of direct adds, include, query) when the collection already has an existing deployment.
Originally mentioned:
https://www.reddit.com/r/SCCM/comments/4qhcwg/amawearetheconfigmgrteamheretotalkabout/d4tb5qv22 votes -
Server Groups - Run As Option
There are times when the drain and resume scripts may need to run as an account other than the local system account of the server. We often support "clustered" servers that rely on a clustering method or data outside of Windows fail-over clustering (Exchange being a good example, but not the only use-case).
It would be nice to specify a run-as account for these scripts in order to reach out to external systems using a service account in order to authenticate to those systems for any required health checks prior to patching (drain script) or after patching (resume script). We…20 votes -
Collections, View device model as additional column
I would like to be able to view the device model information within a collection from the admin console\device collections. This currently does not seem to be available from the menu when I right click on a collections column headings to add more columns.
I believe this may be useful as an additional way to ensure that mistakes have not been made when creating queries to populate collections with specific models\manufacturers.
As an example, I created a collection for a specific manufacturer that the computer object also had membership of a specific Active Directory OU. This resulted in the collection…
20 votes -
Server Groups - Increase Length of Drain and Resume Scripts
The drain and resume scripts are currently limited to 512 characters each. I know there is currently a request to add native cluster aware patching support, but it would be a great start to simply increase the size limit of the scripts. It doesn't seem like there is a safe way to "drain" a server from a cluster to prep it for patching in a mere 512 characters, especially considering that we have to use up some of those characters to return the correct exit code.
We can run some pretty complex and lengthy scripts in configuration items and baselines,…
20 votes -
Right-click Collection Deployments to View Deployment Status
I find it would be handy when viewing deployments to a collection, if a Right-Click option existed to view status - i.e. open the deployment status (Monitoring/Deployments/[Deployment]/Status).
20 votes -
Trigger the Approval Workflow engine on a software deployment or collection count change
In our organization, we really like what we've seen for the Scripts Approval Workflow, where we are able to select 'Approvers' to authorize changes to a Script before deployment.
This is a powerful mechanism, we'd love to trigger the workflow mechanism in two other situations:
1.) We want to require Approval when a new deployment is created, and especially when a new OSD Task Sequence is deployed to a collection.
2.) What if we have an existing Deployment that targets a collection? Someone could edit the collection and then add an Include rule for 'All of Our Super Prod Servers…
19 votes -
Add Pending Restart Option Under Criteria for devices
We don't have Option to Add "Pending Restart" Criteria While sorting devices Under Collection.
19 votes -
Collection link in deployments
When viewing a deployment, make the collection it's deployed to a link. So I can easily view it's membership. Right now I have to stop viewing the deployment and jump over to assets wunderbar and hunt down the collection. In a large environment this is time consuming, especially if you are using both device and user based deployments.
18 votes -
Allow Active Directory Distribution Lists to be Targeted for Deployments in Collections as a Group Resource
Allow Active Directory Distribution Lists to be Targeted for Deployments in Collections as a Group Resource. Currently AD DLs are not able to be targeted, just AD Security Groups are able to be targeted.
18 votes -
Word Wrap in Collection Editor
The new collection editor is very nice, but it would be even better if we had the option to enable "word wrap" as part of this new window. I know we can resize window, but often times word wrap is the preferred method for viewing.
18 votesstarted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Improvements are planned here for future releases.
-
Count of device status should pops once came to Online
Once the machine came to ONLINE from Offline - It should shows as a count status in that left corner of collection E.g., Out of 2000 clients if 500 machines are in ONLINE then count should be 500 in the left corner of that device collection.
16 votes -
Option to prevent Deployment on specific Collections
I would like to see the ability to prevent Deployments on specific Collections. (f.e. All Systems)
16 votesNoted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Is this really any collection? or just all systems / all users?
-
Excel Export for Collections
A right click on a colletion should provide to Export all members to an Excel file not only to an Managed Object Format (MOF) file.
15 votes -
Make Task Sequence 'Collection Variables' available in the full OS as an environmental variables
If 'Collection Variables' could be made available in the full OS as an environmental variables, I can then start to control other deployments, i.e. applications, based on the collection they are in.
15 votes -
Limit a Collection to Max Number of Machines for Licensing
It would be nice if you could create a feature for collections that could limit the number of machines that could appear in a certain collection. Say you have 5 licenses of a software, you wouldn't want 6 or more machines to appear in the collection as you don't have a license for the 6th machine. Just a thought.
15 votes -
Allow maintenance window schedules to be applied to reboots
In scenarios where you do not want a workstation or server to be rebooted, any rogue or untrained admin with rights could deploy something to the device without suppressing reboots.
Would it be possible to allow Maintenance Windows to be applied for reboots? This would allow admins to create collections of machines that would only reboot during a set schedule and ensure that the settings cannot be overridden by a deployment.
I could also see this being done via Client Settings, but that would be 24/7 not restricted to a maintenance window.
14 votes -
Increase performance of incremental collections so that the best practice limit of 200 can be increased
Incremental collections are an invaluable component of Configuration Manager 2012 that is unfortunately held back by the performance implications of having too many (based on the best practice limit of 200). While the -need- for frequent updating collections was reduced based on an applications conditions, there is still an industry preference to manage application availability using Active Directory groups. As a result, the number of collections potentially benefiting from incremental collection updates is high. I work around this by parsing collections that reference AD groups, checking if they've been updated recently and then requesting collections updates of relevant collections. This…
13 votes
- Don't see your idea?