In the Client Data Sources dashboard, have an option to display a total amount for all sites.

Listing updates in the CM console I can see compliance level in a pie chart. It would be good if I directly from there could list all objects that are missing the update I'm looking at in the same way as we are able to navigate to the monitoring part for a package being distributed.

With Windows 10 and Server 2016 updates taking longer to install than previous versions of Windows. It would be helpful to be able to be able to set a site wide setting for the default installation time given for software updates. Currently this is 10 minutes but we are having to manually set this to 60 minutes on each update presently.

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.

Windows 10 1803 builds with more recent cumulative updates show up as "Other" on the Windows 10 servicing summary. This is with SCCM 1802 with all hotfixes installed.

We use encryption and have a bypass script but need a way to have it run prior to updates installing or at least prior to updates causing a reboot.

Server Groups - Would be nice to see some options on Patching Clusters with regards to patching the passive node/active node in the server group during its maintenance window. Right now im having to solve for this with making patches available to the collection and then running powershells to determine which node is passive. would save tons of time if we just had the feature built into Server Groups as another option along side the others (allow percentage, allow a number, specify sequence, etc....)

Hi,

please check if this is a bug or we made something weird: If you rename a Software Update Group which is created by an Automatic Deployment Group, the ADR is crashing on next run.

Sometimes we need to rename them if a product is added or removed.

Cool Option would be if you rename an ADR, the Name of the Group + Deployment will be updated with a new Name, too.

Thanks in Advance

Florian

Would be good if you could change the description of the Office 365 updates to match the update text or at least not include the paragraph about it not being possible to deploy via WSUS. It's just not something that needs to be visible in Software Center.

Either that or allow administrators to overwrite the description visible in Software Center for users similar to custom severity. It's not a big thing, but I've had a few people ask about it.

We have very custom servers and I am using Maintenance Windows to control these Reboots. I would love to see where we can control reboots on a server...For example, we reboot a server wait for it to come back up before second server gets rebooted.

It would be nice if SCCM automatically removed superseded updates from Software Update Groups and replaced them with the superseding update. I can see the supersedence trail for each update, so SCCM can tell me the KB number of an new update that supersedes a previous update, now just make the swap!

The 1806 feature to download from MS directly is great. But once the SU is downloaded it won't work anymore. Would like to have the option to deploy in different ways (DA clients to pull from MS, on site clients from DP).

Provide the feature updates to newer windows version including the latest Windows CU.
Currently the upgrade to 1803 is done to the RTM version. Thus already solved Windows bugs appear (e.g. low disk space, additional drive letter).
When upgrading with the latest CU, these issues dont happen.
TaskSequence is no option also the installation of the CU afterwards as the bug have raised before.
The opened support case was closed with the information to post the DCR here.

When your devs publish a new version in Git it automatically creates an update catalog entry. We can then use SCUP to push that new version to our clients.

I have seen issue in my environment with Office 365 update not applying properly if Office apps are open during installation. The update is shown as successful and restart required in Software Center. After restart original Office 365 build is still installed, next Software Update Deployment Evaluation Cycle, the update is reapplied. Only way around it for me was to close Office Apps

Allow Windows Updates to be managed through SCCM but allow users to pull the actual files from WSUS.

In smaller environments why must I download the updates on the WSUS server than have the update sync down to the SCCM server forcing me to put 60 gig worth of updates in 2 places. This should be an option.