on our short term radar.
@Peter: as a workaround, you could set a maintenance windows for update deployment of 5 mins in 10 years from now (on your server manual collection) and on your deployment, do not allows installation and reboot outside the Maintenance window, that would have almost the same behavior as available, at least that is what we do for our server(s) to simulate available deployment.
Should be in the 1802tp.
And we should have the ability the filter this per collection and apply some Security Scope.
and would it be nice if the ADR only downloads the required updates for the targeted collections. i.e. Rule X create deployment Y & Z that trigger collection A & B, then only required updates for Collection Members A & B will be downloaded.
Also, I think it would be nice if we can add some filter lilke "deployed" to the Software update tab... then will be able to use ADR to deploy all required updates that are Not Deployed...
This feature will evolve from the “run scripts” features that first showed up in ConfigMgr 1706 tech preview. It lets you build a library of powershell, and execute them on demand. We will evolve DSC capabilities into this feature too.
There are a lot of dashboard like the ones for Software updates, Client health, Windows 10 & Office 365 servicing, security that could be great to publish to non admin console users.
It could be great to have a way to filter those by collections, as well as having a option to export or publish those dashboards to PowerBI or Sharepoint. The same king of integration that SCOM has with sharepoint?