In the Group Configuration you can define as to how one should go about with the newly created groups.
The group configuration must be done before the starting a project, as in the course of the project the permission group are created corresponding to this configuration.
Here, you can select from which type the permission group should be created automatically by migRaven. Domain local, universal and global groups are available for selection. Please note the effects with reference to the token size and eventual requirements in the allocation of permissions over multiple domains.
With only one domain global or universal groups are available, both occupy only 8 Bytes in the Kerberos-token and can contain global groups, the customary types for the user groups. Universal groups have the advantage, that apart from the global groups they can even contain universal groups, and both from other domains.
Multiple domains in a forrest
While working with multiple domains, global groups are not at all suitable as permission groups. Domain local groups and universal groups are possible. However, the universal groups from other domains occupy 40 Byte in the Kerberos-token. Local groups occupy always 40 bytes in the Kerberos-token. A disadvantage of the universal groups could be that they replicate in the global catalog and thereby produce more load on the system.
Selected OU for new groups (canonical name):
The permission groups you create with migRaven are stored in an OU. As standard-OU-names migRaven specifies the OU MigR in the beginning. These names can be changed. In case the OU is not available, migRaven creates it automatically. In every project, you can change this OU. That means, you can store your permission’s group project- or permit it to share.
Under the OU given here, migRaven places an OU with the server name. In this server-OU migRaven places all newly generated permission groups for the shares of this server.
If you do not want this additional file server-OUs to be stored, you can prevent this in the migRaven.exe.config with the parameter “ServerOU” and put the value to “0″. The permission groups are then stored in the OU given here.
At the end, the configuration must be saved.