At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.

Introduce ConfigMgr Web Console and remove the need to update the console on every device with each SCCM CB Upgrade as local admin rights are needed to update the console.

The ConfigMgr Web Console might be similar to Azure Portal with Microsoft Intune.

With SCCM CB updates getting released more frequently than before, this will provide benefits and ease of management. The Admins can connect to the ConfigMgr console from any computer in the organisation without the need to install it.

When working with multiple customers and/or in migration scenarios (and also in lab- technical preview environments) it would be great to be able change the color scheme in the ConfigMgr console to clarify which environment the console belongs to.

Can be frustrating, SCCM console, keeps resetting to default, every time you exit. The odd occasion it will retain settings. IE: folder options, and settings. Would be nice if we could save these to a personal default, so it retains settings.

Managing your SUP can be challenging in large environments where other teams may be implementing new Microsoft products and forgetting to notify the SCCM Admin that it might be a good idea to patch the product.
With Management Insights now available in the Console it would be nice to show insights in what Microsoft products are detected in your environment as being installed, but are not enabled on the SUP hence creating a potential security risk.

How about providing associated log file details at the end of the summary / completion page of all SCCM Wizards to help SCCM admins. I think it would be helpful. What you think?

For example if you are creating a SUP role -> Add Site System Roles Wizard -> Completion page will have the log file name -> SUpsetup.log

Do you love SCCM updates and servicing monitoring log file details?

Add Column for Email just like 'Primary User'. This will allow rapid targeted communication to the Primary Users in a collection.

Add Additional Options for Maintenance Window Schedules. Add check boxes to select how the schedule should be applied.

For Example

Apply this schedule to:
[_] OS Deployment Task Sequences
[_] Software Update Deployments
[_] Standard Software Distribution (Applications and Packages)

Currently, the maximum an administrator can give users to reboot their systems is 1440 minutes (24 hours). Please let us specify up to 7 days. The goal of the delay is to allow a reasonable amount of time for an end user to save their work and reboot without losing anything. The 24 hour limit means that if a user is gone for a day, there is a strong chance they could lose their work. Allowing up to 7 days seems like a better compromise between end user control and respecting admin intent/organizational need.

It's possible to create a new node in the console with favorite actions.

Example:
Favorite\Frequent Action 1 (Device collection)
Favorite\Frequent Action 2 (Monitoring content)
Favorite\Frequent Action 3 (Application Deployment)

If you want to add any action in the console to favorite Node, just right click on the action and select add to favorite actions...

In this wau

I would like to be able to copy a boot image so I can update it and make changes without breaking the original boot image. Currently you have to create all new boot images by hand and manually add the drivers.

You should be able to enable or disable any deployment (for applications, packages, software updates, etc) by right-clicking and selecting enable or disable.
Currently to disable an application deployment you either have to delete the deployment or retire the application and for packages you need to disable the program.
Software update deployments already have this feature.
You should also be able to enable/disable a deployment from the Monitoring workspace.

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.

Console users must have "Run Scripts" security role permission to use CMPivot. Can you add a separate security role permission for CMPivot so we can make administrative users with CMPivot permission but not "Run Scripts?"

Why can't we simply drag and drop machines/users into collections instead of having to go through wizard?. It makes it much harder for Helpdesk to understand how to use the console (hence why most people use AD security groups as targets). Why not select/Multi-select items and drag into relevant collection

During the cutting and pasting in the query section, also allow the capture of the label column. This would have to be a bit 'faster to export the data. The best solution would be to have the ability to export via a dedicated button in various formats, csv, excel, pdf.