
Collections are the basic way to organize the resources detected by Configuration Manager. It is possible to create a membership rule that takes into account another collection (Include collection). In this way, you can easily create aggregate collections based on criteria specified in other, constituent collections.
Cyclic dependency of collections in Configuration Manager
An obvious problem with the application of such membership rules is the creation of a cyclic dependency when, for example, three collections are included in each other: the first in the second, the second in the third, and the third in the first. In order to test the effects of such a situation, three test collections were prepared:

Protection against looping of collection memberships
As you can see, the administration console has a built-in defense against closing the collection membership cycle. This is by no means limited to two or three collections. The SQL vSMS_CollectionDependencies view records all collection dependencies, hence the attempt to loop memberships with four or more collections also fails.

So it's easy to see that the defense against cyclic dependency of collections is not just a feature of the GUI (admin console), but has its basis in database mechanisms. Especially with a large number of collections, accidental closure of dependencies can happen - fortunately, there is a mechanism to defend us against this.

- Support and development of Microsoft and Nintex based applications
- Application design and development including digital processes
- Invoice management
- Requisition management
- Contract management
- Modern Intranet
ISCG sp. z o.o.
Al. Jerozolimskie 178, 02-486 Warsaw
NIP: 5262798378
KRS: 0000220621
Phone