Correct the "Add Selected Items" ribbon button functionality
Currently when you select a collection(s) in the console, then utilize the "Add Selected Item" button you are able to functionally add the collection(s) selected to another collection as a member, however it does not actually add the member of the selected collection(s) to the target collection just the root collection itself.
1. Open Console and navigate to Administration \ Assets and Compliance \ Device Collections \ Select a collection.
2. Click the "Add Selected Items" button and then "Add selected items to existing device collection"
3. Select the existing collection that is to be the target
The collection itself now shows in the membership of the target collection, however the members of the collection added are not and are not utilized by the target collection.
1. Open Console and navigate to Administration \ Assets and Compliance \ Device Collections \ Select a collection and open it.
2. Select a device or devices in the collection
3. Click the "Add Selected Items" button and then "Add selected items to existing device collection"
4. Select the existing collection that is to be the target
The devices themselves now shows in the membership of the target collection.
Since the functionality of this ribbon button is a part of the Core XML files for the console stored "%ProgramFiles%\Microsoft Configuration Manager\AdminConsole\XmlStorage\ConsoleRoot." it is not supported to modify them by Microsoft per the article here: https://msdn.microsoft.com/en-us/library/hh949647.aspx
Please update the code for this button \ process to add the members of a selected collection to the target collection truly or grey the button out when collections are selected instead of devices \ users so that the "Add Selected Items" cannot be utilized.
We’ve taken some changes to improve this. But we believe the remaining behavior of the ribbon being context sensitive to be the correct action. This is the standard design behavior for ribbon context specific behavior.
Chetana Adhikari commented
Thank you so much for your feedback. We tried to repro the problem that you have described. We created a collection A with three members and Collection B with three members. We targeted Collection B to collection A. Now collection A has 6 members. If we go to collection A and do show members all 6 members are listed here (3 from collection B and 3 from collection A).But if we go to Collection A’s properties (and Membership Rules Property sheet), in the list-view, it will only list its 3 members and Collection B(but not its members). We wanted to verify with you that what you are recommending is that we list the targeting collection’s members here, not just the collection itself?
Another thing to note is that: If we go to the targeted collection and click on 'show members' we will find all members from (Targeting Collection + Collection being Targeted) listed there. Could you please help us understand the importance of listing these members in the Membership Rules Property Sheet listview?
Joaquin Santos commented
this is a critical problem for my organization.