When a software update has a superseded = yes, it would be useful to also be able to see if the superseding update is deployed, to verify it is safe to remove from a given software update group.

Moving from OS Deployment to Software Updates

M365 Offline Updates Exporter Utility - Language Selection

Provide language option for OfficeUpdateExporter.exe so that only content related to language of choice is downloaded for an update (rather than update content for all languages). This would reduce a significant amount of time and disk space when gathering M365 App updates.

I would like the software updates module have an improved filter.
Basically I want to create filters which can use NOT LIKE on columns such as severity or Product.

It seems that if you set a client notification time in Computer Restart client policy that exceeds the maintenance window on a collection then the devices in that collection will never force a reboot with a user logged on.

It would be nice if it gave the user the notification window but when the maintenance window comes around for the 2nd time and a reboot has not been done then the installation would happen at the start of that maintenance window.

is it possible to see the Software update download date in console?

i mean when a KB is revisited or bug fixed but keep the same name it's good to know if i donwloaded the previous version or the revisited one.

then i can see if i need to redownload the kb or not

When enabling the "Upgrades" classification in SCCM SUP properties, the advice about KB3095113 is wrong, KB3095113 is superceded by KB4041693. This is horrendous to unravel and badly needs clarification and attention. Please make efforts to sort this mess out, thanks.

It would be nice to have the option to add updates that you, for some reason, manually download in the Software Updates node to an existing Software Update Group.

It's not much work having to go back to the console after the wizard is complete and add them but would be a nice addition to the 'Download'-wizard for Software Updates.

We do not apply quality updates in our environment. We only deploy security only updates. There are updates that are superseded by quality updates only. They are also superseded for longer than our site configurations supersedence rules and therefore we have no way to deploy these to our environment except building a package for them.

When deploying Software, Updates etc. the Deployment Wizard should show the actual 'Member Count' of a collection like in the example screenshot.

In addition in the Deployment Overview the 'Assets Targeted' column should be displayed as default and immediately display something after a deployment has been created. Currently it can take quite a long time before you can see the actual amount of clients targeted.

This will make it easier for Sys Admins to prevent accidental deployments

Active clients should connect regularly to SCCM over the BGB status (it is what is used to determine if a client is 'online/offline' today). My organization tracks patch compliance closely, and part of that measure is determining if the client was online long enough in a given day to actually complete compliance related activities, such as installing the latest CU. We would like a way, likely using the BGB channel data, to determine how long a client is online in a given period of time, with flexibility to quantify by day, by week, by month, etc.

In both the CM CB 1606UR1 and the CM TP 1609 admin consoles, the Windows Update for Business Profiles node needs the "B" in Business capitalized.

Remove unused Vendor classifications from SUP.

As l have been configuring SCCM 1806 with Third Party Patching, l am now left with unwanted Vendors being listed in SUP and SUP Reports.

Can these be pruned/removed?

In ConfigMgr 1511, the "All Windows 10 Updates" node has no filter bar as we have for Software Updates. There are lots of elements listed and the number will increase with the future Windows 10 Builds.
It could be very helpful to get a filter bar which allows to filter on languages, build, SKU, etc.

Publish third party software update content even that catalog were added to WSUS by another application, tool, or script, such as SCUP.

Allow the end user to postpone windows updates and show in the console user/computer name of the postponed computer. Currently the console has vague reasons for software failure.