I would like to see an expansion of what can be done with a configuration item.
First it would be nice to see the create collection options move from the deployed baseline to the configuration item. This will allow there to be different collections for each compliance state for each CI. The option to create new or specify existing collection should be added for that as well.
It would be helpful to replace remediation with something like compliance action and an action based off compliances start (compliant, noncompliant, error, and unknown). I would also like to see different ways to be added to a CI's for compliance actions:
Add, modify, delete registry key
Run script and include multiple script languages
Run Task Sequence
Install individual software update or all updates in a update group
Add to collection
If you use an MSI to get a application detection method, be able to uninstall the software if detected
Tempted to mark this completed, now that we’ve released full blown powerBI integration:
Building reports & dashboards doesn’t get much easier than that.
need an on-perm solution
I am also looking for this. I would love ot be able to create collections based off both boundaries and boundary groups
Latest SDK documentation is online at https://docs.microsoft.com/en-us/sccm/develop/core/misc/system-center-configuration-manager-sdk
For additional information about defining site boundaries and boundary groups for System Center Configuration Manager, see https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/define-site-boundaries-and-boundary-groups
Thanks for posting this to uservoice, Bankim, as I haven't had a change to do it yet. Here is how we are using that information from WMI https://www.linkedin.com/pulse/using-sccm-compliance-settings-boundary-group-apply-bits-schultz
I would rather assign permissions to folders with or without recursive and collections and never have to touch scopes again.