Category Archive: 3. Configuration

Group configuration

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.

Type_2

Read the rest of this entry »

Group naming

The names of the groups created by migRaven can be freely defined within certain parameters.

If the authorization groups created by migRaven are later used by 8MAN, then the group names are to be already agreed upon with the possibilities of 8MAN.

GK Name en

Read the rest of this entry »

How to set List Permissions

1. The use of list groups and permission groups to set list permissions

In other articles we already referred to the aspect that for the allocation of list permissions, list groups and permission groups can be used. For this purpose, there are questions such as:

  • “Can I use only list groups to set list permissions?”
  • “Can I use only permission groups to set list permissions?”
  • “Can I use permission groups on higher directories and list groups below?”
  • “Up to which level can the list groups be used and from which level the permission groups?”

2. Example

Read the rest of this entry »

Build perfect NTFS list rights

1. Necessity for list authorizations

Generally access rights to NTFS-file servers are assigned deeper than the 1st directory level. As soon as this is the case, one must take care of the fact that the user can should also bo able to browse the file system for appropriate directory. Here there are various possibilities with various effects.

2. Variants of assigning list rights

For browsing through the directory system, migRaven can flexibly form list authorizations. In addition to this, two options are fundamentally offered:

  1. For the list authorizations, own authorization groups are formed, which for example include the “Change” authorization groups from the lower levels.
  2. 2. In the directories above the explicitly authorized folder, for example the “Change” authorization groups are used for assigning the list authorizations.

The optimal way is the combination from both options. It should however be used in 1st and not up to the lowest level because otherwise the account appears in several groups. But it should not also be dispensed to position one because otherwise too many entries are included in the ACLs of the above directories. An ACL can maximum includes 1800 ACEs. Too many ACL entries make the access to directories slow.

Read the rest of this entry »

Permission suffix

1. New from migRaven Version 2.1.1010:

  • Now it is possible to change the group suffix – this is particularly useful for 8MAN-users
  • With the new authorization group ModifyPlus, you can protect the authorization end points in a targeted manner from accidental deletion by the user

In case of authorization groups, one marks with a file attachment, which rights does this group has on the directory. This group suffix can now be changed.

Read the rest of this entry »

Connecting migRaven to Novell

migRaven can be used for migrating Novell file server structures to Microsoft. The advantage of migrating with migRaven is the automatic transfer of the authorizations to Microsoft for timely structuring of all necessary authorization groups and list authorizations so that the access authorizations under Windows function exactly as under Novell.

In order to collect authorization information from your Novell servers, two paths are used:

1. Transfer of the trustee-files from the Novell server

Depending upon your Novell-version, the trustee-data can be extracted using different methods.

In Netware, a CSV-file can be generated with the Trustee.nlm, which contains the required trustee-information. However, the content of the file must be modified for migRaven.

On Open Enterprise Server, the trustee-files already exist with the name .trustee_database.xml.  For the conversion into a CSV-file, we have made available a PowerShell-Script. Please note, that Novell has changed the structure of the xml-file in the course of time, and therefore the PowerShell script must be adapted to your OES-version.

Read the rest of this entry »

Optional adjustments to migRaven.exe.config

The Config-file for configuring the program migRaven is called:

migRaven.exe.config

It is available in the directory c:\Program Files\migRaven\. migRaven takes over the parameters from this file while starting the program. So that the parameter changes become effective, you must restart migRaven.

1. Important

In case of program update by migRaven, all program components, also this Config file, are deleted and re-written under c:\Program Files\migRaven\ . Please note here changed parameters separately and then re-enter after a program update.

Read the rest of this entry »