Category: 2. migRaven version 5.0

Project types

migRaven proposes three types of projects:


  1. Scan Your resources  (a Share or directory tree is read)
  2. Novell migration (Trustee information is imported)
  3. Import a table (predefined structures can be imported from an Excel table)


Start menu

Continue reading

Project typ “Scan Resources”

1. For each Share a new project

1.1. Reading directories and permissions

In migRaven one always works with a project. This is the logical unit, which is to be processed. This can, for example, be a share or a directory below a share. In ideal cases it is the point, which is also mounted by the users or is connected in the DFS. Thereby it is ensured, that all permissions – including the list permissions – are correctly created by migRaven.

1.2. Best Practice: for each Share a new project is placed

When you define the individual shares as standalone projects, then you have time to process this in peace and “Step by Step” to copy the data in the new directories and then provide these to the users.

Continue reading

How does the Novell connector work?

Authorizations are transferred from Novell to Microsoft on the basis of the Trustee Information of the appropriate Novell Volume.

Under Novell it is possible not only to assign rights to users and groups but moreover to other projects from the active directory, like organization units. The use of OUs for assigning authorizations is a simple method, as new objects need not be created anymore. Furthermore it is common practice in Novell to create rights directly on the user level.

The Novell Connector of migRaven is in the position to transfer all these rights sensibly in the Microsoft world. Prerequisite: The user accounts have been replicated to Microsoft and have been assigned via the SAM.

Continue reading

Project typ “Table import”

1. Function

In case of Table-Import, you can insert, migrate and write the authorizations provided in a table (e.g. Excel-table) in a provided share.

2. Table structure

The table structure expected by migRaven looks as follows:




Read and Execute



Modify Plus

Full Control

\directory\projectfiles domain\gr1;domain\gr2 domain\gr3

Continue reading

Project statistics

Available from Version 2.1

In the project statistics, questions related to general authorization situation and volumes of files existing within the project directory are represented.

The number of files has for example significant influence on the duration of the authorization changes or copy procedures. If there are too many files in a directory tree, then for example the new rights should be rolled out via the Green Meadow to avoid performance issues.

Continue reading

Set access rights

migRaven has powerful algorithms, which greatly simplifies the complete process of re-granting the access. These algorithms follow these principles:

  • No interruption in permission inheritance (only in exceptions)
  • Only authorizations in groups
  • Application of the A-G-DL-P principle or a modification depending on configuration
  • List authorizations are automatically set by migRaven
  • Minimum authorizations: There are as many authorizations in the total in the root, as were authorized on the complete path.

Following advantages arise:

  • You must take care of only the authorizations at the authorization end points. -> this is where the real permission is set (e.g. Change or Read)
  • The help authorizations are automatically generated by migRaven. -> All list rights
  • Groups are automatically generated by migRaven and are provided correctly with names.

That result:
you only need to take care of the directories, which are the authorization end points.


Modify Plus

Modify Plus has become even better!

The ModifyPlus-right prevents the accidental move or deletion of the authorization end point by the user. The new ModifyPlus replaces the version, which was also identified as ModifyPlus. The function of both the versions is same, however the implementation was improved. By using the authorization “Delete sub-folders and files” instead of “Delete” can be waived by the “Deny deletion” for “Only this folder”.

What has also changed is that you need not decide whether you assign Modify-Rights or ModifyPlus-Rights in a project. In case of each directory (authorization end point), you have the option whether the user should get normal modify rights, or whether you want to prevent the fact that the user moves or completely deletes this directory.

Continue reading

Deploy access right groups

In case of Design & Work, a new authorization structure was computed on the basis of the read authorization structure in accordance with the Best Practice of Microsoft.  This consists of

  • new permission- and list groups,
  • nesting of available groups and accounts in the new groups, as well as the nesting of new groups in each other, and
  • the access rights contained in the groups that have access to the directories.

1. Task of this function

In case of Deploy Groups, the new authorization- and list groups are written in the AD. In these, the provided groups and accounts are nested.
For this you need the write rights on the AD, for example as domain admin

Continue reading

ACL deploy

1. Task of the function

With “Deploy ACL”, the directory structure is written under the target path and the list- and authorization groups created before are entitled to it. Sub-directories without explicit authorizations are not created.

You need write rights to the deploy directory, for example as administrator.

Continue reading

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.

Continue reading

Load more

Translate »