When viewing a software update in the console, it only shows the number of systems that are compliant, non-compliant, etc. next to the pie chart. Modify that so each number is a hyperlink that when clicked opens a new node under Devices showing the list of systems that are in that state for that update. Having the ability to quickly see which systems still need an update in the console would be extremely useful. Having to run a report every time is slow and cumbersome.

I find updates duplicated into multi packages, and downloaded in each, making the space used 2x+ more then needed.

Please add the possibility to integrate cumulative updates into Windows 10 Feature Updates (SCCM servicing)

or

do the integration by yourself and give us the possibility to re-download the Feature update with an integrated cumulative update.

The feature updates in our environment always time out on the older machines with mechanical drives as they are slow to update. It would be helpful if the timeout was set to a lot more than 1 hour by default. Secondly when it does time out it would be helpful if it failed the deployment instead of sitting in software center saying it's installing indefinitely. The only way I've been able to do this is to delete the client from SCCM and re-install the agent on the client machine. Distribution of feature updates through SCCM needs a lot of work.

Extend the Phased Deployments feature to include Software Updates if it is not already planned.

Seems Office 365 updates do not coincide with Windows updates like previous versions. What happens is Windows updates will force a reboot without waiting for Office 365 updates to finish installing.

Both are set with the same deadline in the same Software Update Group.

Otherwise, I recommend that the Office/SCCM Team come up with restart flags that can be set via SCCM to just restart the Office 365 apps.

Would be nice to create a new custom search from an Automatic Deployment Rule.

Add a button near the "Preview" that will create a new custom search or replace an existing one.

Please add full functionality of SCUP to the Third-Party Software Update feature. Adobe Acrobat catalogs don't expire older updates and don't include supersedence information. I normally added supersedence settings through SCUP to mitigate this. Without the ability to edit this information or to expire old updates manually, deploying Acrobat updates becomes unwieldy. Unexpired updates that are not superseded will likely bloat and fill up the data shares. If you can publish it, you should be able to expire it.

The UBR is also used to identify a machine is complaint to cumulative monthly patch or not.

Now that we have OS build (Buildext or UBR) info add to V_R_System via DDR, it would be great if the same UBR or OS Build is added to each update in V_Updateinfo table in SCCM Database
when the new updates released by Microsoft on MSPD, so that the win 10 compliance reporting would be much simpler.

Add a filter in the ADR rules to filter on members of collections. So an ADR rule can have required by more than one device (>=1), but limited to required updates by collection membership

Would it be possible to have a visual queue in the Software Updates console a hint of which KBs are delivering which Windows Update Agent?

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

Being able to select a device group when scanning for updates and only seeing updates that are missing from that group would be a huge help.
currently the counts reflect the whole environment which is much less helpful.

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?

Allocate more than 60 minutes max runtime to a feature update, or at least have the feature update/ConfigMgr tell the user it was aborted because their PC is too slow. At the moment software center just keeps saying 'installing'. setupact.log has a MOUPG entry noting % progress.
changing max runtime has no affect unless re-deployed.

In some certain scenarios, it would benefit to have the ability to Blackout Existing Maintenance Windows (universal) for a specifc date or range of days.

e.g. systems maintenance or migration in progress for three days, I don't want those systems to be touched by deployments or software updates as to not cause disruption. Or in a case where its a holiday week and high volume of sales so would like to "pause" any automated actions that could cause reboots within a specified date(s)/time(s).

Software Updates Required View Status

Can we get an option to view status like in deployment status to view machines that are required and installed? We have no idea what does machines are.

Thanks.

If you define a server group and use Windows Defender you might want to update those definitions as early as possible.

Currently, those definition updates trigger the node drain and resume skripts, which can lead to service downtime.
Additionally, the updates can only be installed during maintenance windows.

I want you to
a) add an option in deployment in software update groups to always ignore maintenance windows
b) add an option in deployment in software update groups to ignore server group settings