|
1 | 1 | --- |
2 | | -author: mestew |
3 | | -ms.author: mstewart |
| 2 | +author: aczechowski |
| 3 | +ms.author: aaroncz |
4 | 4 | ms.prod: configuration-manager |
5 | 5 | ms.technology: configmgr-core |
6 | 6 | ms.topic: include |
7 | 7 | ms.date: 02/16/2022 |
8 | 8 | ms.localizationpriority: medium |
9 | 9 | --- |
| 10 | + |
| 11 | +## <a name="bkmk_delcollref"></a> Delete collection references |
| 12 | + |
| 13 | +<!--9708999--> |
| 14 | + |
| 15 | +Previously, when you would delete a collection with dependent collections, you first had to delete the dependencies. The process of finding and deleting all of these collections could be difficult and time consuming. Now when you delete a collection, you can review and delete its dependent collections at the same time. |
| 16 | + |
| 17 | +A new **Details** window shows more information about the relationship types, and lets you [view collection relationships](../../../../clients/manage/collections/manage-collections.md#view-collection-relationships) in a graphical chart. |
| 18 | + |
| 19 | +:::image type="content" source="../../media/9708999-delete-collection-references.png" alt-text="View collection dependencies in list and graphical form when deleting a collection" lightbox="../../media/9708999-delete-collection-references.png"::: |
| 20 | + |
| 21 | +There are several reasons why the site can't delete a dependent collection: |
| 22 | + |
| 23 | +- **Assigned to user**: For more information, see [Modify the administrative scope of an administrative user](../../../../servers/deploy/configure/configure-role-based-administration.md#modify-the-administrative-scope-of-an-administrative-user). |
| 24 | + |
| 25 | +- **Used by cloud attach**: For more information, see [Enable cloud attach for Configuration Manager](../../../../../cloud-attach/enable.md). |
| 26 | + |
| 27 | +- **Use for upload to Microsoft Endpoint Manager**: For more information, see [Make Configuration Manager collections available to assign Endpoint security policies](../../../../../tenant-attach/endpoint-security-get-started.md#bkmk_collections). |
| 28 | + |
| 29 | +The details window lists collections that can't be deleted with the reason why. |
| 30 | + |
| 31 | +### Try it out! |
| 32 | + |
| 33 | +Try to complete the tasks. Then send [Feedback](../../../../understand/product-feedback.md) with your thoughts on the feature. |
| 34 | + |
| 35 | +1. Create multiple collections that are dependent on each other. Use relationships such as **Limiting**, **Include**, and **Exclude**. For more information, see [How to create collections in Configuration Manager](../../../../clients/manage/collections/create-collections.md). |
| 36 | + |
| 37 | +1. Delete a collection that has dependent collections. For more information on how to delete a collection, see [Collection actions](../../../../clients/manage/collections/manage-collections.md#collection-actions). |
| 38 | + |
| 39 | +1. In the **Delete Collection Error** window, select **Details**. |
| 40 | + |
| 41 | +1. Once the relationship types finish loading, select **View Relationships** to see the graph. |
| 42 | + |
| 43 | +1. If all of the dependent collections can be deleted, select **Delete all listed collections**. |
| 44 | + |
| 45 | +1. Review the list of collections and any software deployments that the site will also remove. You also can **Delete each collection member from the database**. |
| 46 | + |
| 47 | +### Known issue when deleting collection references |
| 48 | + |
| 49 | +<!--13235415--> |
| 50 | + |
| 51 | +Consider the scenario where you're deleting collections with references, and another administrative user is simultaneously creating a reference to a collection that you're deleting. When this behavior occurs, the console displays an error, and the collection isn't deleted. |
0 commit comments