Category: 3. group configuration
migRaven Builds all permission groups in one operation and nests them as recommended by Microsoft Best Practice. (AGDLP / AGGP)
Depending on the project scope, this can be up to thousands of groups. The selection must take into account whether it is a single domain, a domain Forrest or even choked domain environments. In certain constellations you can not select every group type.
The Group configuration of migRaven The group type and name structure of the Active Directory authorization groups to be created, the creation depth of the list groups and the storage location for the new groups are specified in AD.
The group configuration must take place before the first project call, since the authorization groups are created according to this configuration during the project run.
The Rider Type The group type for the authorization groups and the storage location for them must be entered in the AD.
Permanent link to this post: https://help.migraven.com/gruppen-konfiguration/
Under the tab "Name" the name structure of the migRaven configured to create authorization groups. Here, the authorization groups must specify the prefix, the components of the name, the order of these and the separator between the components.
Within certain parameters are the names of migRaven created groups freely definable. Should the from migRaven created authorization groups are later used by 8MAN, the group names are already here to agree with the possibilities of 8MAN.
Permanent link to this post: https://help.migraven.com/gruppen-name/
In order to access authorization endpoints in lower directories, the authorized users require list rights. Two types of groups can be used for this purpose: special list groups on the one hand and the authorization groups that are created for the authorization endpoint on the other.
Here is to be shown how both types of groups interact and that their advantages and disadvantages are balanced when they are used together.
1. The use of list and authorization groups for the allocation of list rights
1.1. Why list rights?
Permanent link to this post: https://help.migraven.com/vergabe-von-listrechten/
1. Need for list permissions
As a rule, access rights to NTFS file servers are lower than to the 1. Assign directory level. But once that is the case, you have to make sure that the user can also browse through the file system to the appropriate directory. There are different possibilities with different effects.
2. Variants of the allocation of list rights
Permanent link to this post: https://help.migraven.com/ntfs-listberechtigungen-optimal-aufbauen/
New migRaven Version 2.1.1010:
- Now it is possible to change the group suffix - this is especially useful for 8MAN users
- With the new authorization group ModifyPlus, you can specifically protect authorization endpoints against accidental deletion by users
For the authorization groups, a file attachment indicates which rights this group has to the directory. This group suffix can now be changed.
Permanent link to this post: https://help.migraven.com/rechte/
migRaven can be used to migrate Novell file server structures to Microsoft. The advantage of moving with migRaven is the automatic transfer of the authorizations to Microsoft with simultaneous construction of all necessary authorization groups and list permissions, so that the access authorizations under Windows function almost exactly as under Novell.
The migration takes place in two steps. First, the permissions must be obtained from the Novell server. There are differences between Netware and OES. In the second step triggers migRaven Through an LDAP connection to the Novell server, groups and replace them with members. This requires admin rights.
Permanent link to this post: https://help.migraven.com/anbindung-von-migraven-an-novell/
The config file for configuring the program migRaven called:
It is located in the directory c: \ Program Files \migRaven\. migRaven adopts the parameters from this file at program start. For parameter changes to take effect, you must migRaven start anew.
For a program update from migRaven all program components are under c: \ Program Files \migRaven\ deleted and rewritten, even this config file. Note down changed parameters separately and enter them again after a program update.
Permanent link to this post: https://help.migraven.com/config-datei/