Introduction
Configuration Sets can be used to create templates for a specific business case where you will need to create multiple entities at once. By defining a Configuration Set Templates you can ask the user to enter a predefined set of attributes and then use this information to create various entities.
A good example is a project. A project usually has a name and someone who will be in charge of it. You can add those two attributes to the template and each time a user will create a new configuration set of that type he will be asked to enter the name and select someone who is in charge. With the information entered you now can create various entities such as a project folder within the file structure, an Active Directory group for all members and even a project specific Shared Mailbox on mail server.
Later on you can easily add members to the configuration set and configure what should happen in that case. For example we can automatically add all members to the Active Directory group and give permissions to access the Shared Mailbox.
Configuration set features
Resource nesting
Automatically added resource types or identity types according to a certain schema
An entanglement of the entities to be created with the organizational tree
Independent GUI part only for configuration sets
Grouping of Core-Identities with automatically setting up the above described features
Constant adding, updating and deleting of configuration sets possible
Currently missing features
Configuration set GUI not entirely completed, it is currently only possible to setup the behaviour of the configuration sets in the database, an individual GUI per configured configuration set type is planned.
A configuration set cannot have their own active directory account (so f.e. group mailboxes could be setup using configuration sets whereas user mailboxes, which need an active directory account, cannot)
Currently no fast-tracking implemented (configuration sets are only handled by the constantly running ConfigurationSetTask)