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.

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.

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.

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

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

I would love the ability to query or better yet, create a device collection based on devices that have failed to install an application (or pending).

Allow a Right Click option on a single device to access the properties of that device (e.g, OS version, hardware type, installed software) and then select certain properties to automatically create a Device Collection based on those properties.

It would build a SQL query as would happen when you create a Collection today, but to have Config Manager fill in the bits you don't know would be great.

Like do I need OSVersion.Caption or .BuildNumber or .whatever? I just could pull the properties straight out of an existing device.

Be able to identify which collections are enabled for AAD Group Sync

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?

In the Devices area can a column for the primary users email address from Active Directory or AAD be added and perhaps optionlly be able to add other AD or AAD user attributes.

When building out collections for whatever reason, you can presently only copy a collection by right-clicking and hitting copy, which creates a single copy of the collection. If you need, for example, 21 copies of the same collection, you have to go through that process 21 times. It'd be nice if there was an option in the context menu to select how many copies to make.

As it is possible to run ADRs after running a SUP sync, it should be possible to do it with collections.

E.g.: you have a collection named "Workstations" and a collection named "Workstations | Windows 10". Instead of planning your schedule to sync first the "Workstations" and only after the "Workstations | Windows 10", there should be an option like "Run sync after sync of limiting collection". This assures that the collection gets updates after the first one is correctly updated.