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 System Center Configuration Manager, though we can’t promise to reply to all posts.
Please do not use UserVoice to report product bugs or for assisted support.
If you believe you have found a product bug, please send us a bug report through the Configuration Manager Console (1806 and newer). To do this, press the 🙂 button in the top right corner and choose “Send a Frown”. For more details, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
Standard Disclaimer – our lawyers made us put this here ;-)
We have partnered with UserVoice, a third-party service, so you can give us feedback. Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Microsoft Configuration Manager. Do not send any novel or patentable ideas, copyrighted materials, samples or demos. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms.
-
SCCM updates: User Experience - Reboot notifications
Here is the User experience for the update process as I understand it:
1. System tray balloon appears saying 'software changes are required'
2. System tray balloon appears saying 'downloading and installing software'
3. System tray balloon appears saying 'Restart required: Recently installed updates require your machine to be restarted'
4. *It is here I would like the larger temporary notification reboot window to appear but it doesn't.
5. Permanent notification reboot window appears and stays on the screen
I would like option 4 to be possible. Without this it seems quite easy for users to miss seeing the balloon…
1,691 votesDoing work in this area. Please make sure your requests are included in the comments.
-
Allow the Client Upgrade to be performed outside maintenance windows
We would like the Client Upgrade feature to allow the client to be upgraded outside of maintenance windows but also give the option to only install when no user is logged in, like deploying Applications allow.
156 votes -
Enable HTTP content locations for source files
Enable the use of HTTP and HTTPS locations as source locations for content. With the increaseing use of GitHub and binary repositories like Artifactory the ability to use HTTP locations as content locations for applications and packages would be greatly helpful in managing and distributing the a content in an efficient manner within SCCM.
53 votes -
Adjustable Window Sizes within Admin Console
It would be nice to have the ability to adjust window sizes within the console. As an example, the Membership rule window in the collection properties only has enough room to show 2 lines. Being able to maximize or edit to a custom size and have the console remember these sizes would be great.
This could be incorporated into the fixes that are being introduced with the High DPI resolutions.
37 votesDoing this everywhere in the console would be expensive/difficult. Rather than wait to make any improvement until the time we can fix it all… I’m curious what the top 10 most important places to fix are. I’m thinking we fix those first, and then go from there.
-
Include orchestration of software updates especially for tiered solutions
Today it's only possible to orchestrate software updating based on a membership in collections.
This is however rarely enough for more complex setups where you might have back-, middle-, and front tiers in your setup.Therefore I recommend adding a dependency system between computer objects, so that you can orchestrate at least the following:
1) Which tier of servers are patched first, second and third etc.
2) Reboot order between the different tiers which includes an accept of one tier being fully patched and rebooted before the next tier is begun updating.
3) Ability to choose between warning or rollback…30 votesWe’ve started doing work in this direction. Look in the Tech Previews for things called “cluster patching” that lets you orchestrate multi-machine patching.
-
Give more granular control over the 2 hour SUP failover timeout
Currently, failover from one SUP to another SUP is always at least 2 hours. Even with the new Boundary Group design, with controllable failovers - the minimum is still 2 hours. Allow admins to control that minimum, and set it smaller than 2 hours.
10 votes
- Don't see your idea?