Many people build inefficient queries simply because they are unaware of the indexed fields available for the views that are referenced by their query. Can the indexed fields be marked?

Can Resource Explorer be updated to include the device name of the object you are looking at in the title bar.

Today if you have a collection with a large query such as for thousands of devices, you may hit a character limit. In larger environments, this may happen more often. This could be from a list query or a query with many ANDs or ORs.

It would be awesome if I could right click a Boundary or Boundary Group and create a queried collection off of it.

For instance, we have satellite clinics where we have boundaries for each floor (ED, Urgent Care, etc). It would be awesome to be able to quickly create a collection based on that range

in the sumary section of a collection, include the collection ID. So, we will be able to select and copy it.

An example would be installed software query. You find 50 machines with outdated software through cmpivot . You want to send them to a collection to uninstall or update them.

Whenever Admin removes any device A from Collection X and adds to Collection Y then to check the resultant membership of device A instantly, Admin has to update collection membership of both Collection X & Y. It will be better if the Admin can directly update the collection membership for Device A by right clicking on Device A and click on UPDATE MEMBERSHIP. Definitely, it will save time by updating membership at one place only.

I would like to suggest a new read only collection called "All Systems Discovery" maintained by SCCM itself where it would keep track of all System Discovery objects in it, similar to "All Systems" but instead this would repopulate with discovered systems on full discovery cycle. This collection would help SCCM admin to find active objects in AD at a glance without any additional efforts.

Include functionality to include or exclude members to a collection, based on their Compliance status on a specific Compliance Baseline.

It will be very suitable if new collections could be created per deployment results, e.g. create collection based on "failed" status in deployment

When building collections (particularly query collections) it would be handy to be able to preview the devices/users in the collection as written before you commit. Today we have to edit the collection, update membership, refresh then confirm that the membership is correct. If you have a button inside of "Edit Query Statement" it would save a lot of hassle.

You can click on the device and select to list all included collections. Also, select to exclude this device from all collections shown.

We don't have Option to Add "Pending Restart" Criteria While sorting devices Under Collection.

Allow the recurrence pattern for maintenance windows to be scheduled with an offset from a base day.

Meaning, if we want a maintenance window on the Wednesday following the Second Tuesday of every month, we could configure a maintenance window for the Second Tuesday with a +1 offset.

(This would be similar to the offset option added to ADRs in 1802.)

Be able to update membership in existing collection in CM from CMpicvot instead only create new