Instructions: introducing an IDM system

1. Create project and read in directories

Create new project – Read in directories and authorizations

In migRaven, one always works with projects. A project is a logical unit, which is to be processed, for example a share or a directory below a share. Best is the point which is mounted in case of users or integrated in the DFS. Thus one ensures that all authorizations – including the list authorizations – are correctly created by migRaven. Via the title “Administer projects”, you arrive at the point, where new projects can be created, processed or deleted.

Read the rest of this entry »

Instructions: introducing DFS

1. Create project and read in directories

1.1. Create new project – Read in directories and authorizations

In migRaven, one always works with projects. A project is a logical unit, which is to be processed, for example a share or a directory below a share. Best is the point which is mounted in case of users or integrated in the DFS. Thus one ensures that all authorizations – including the list authorizations – are correctly created by migRaven. Via the title “Administer projects”, you arrive at the point, where new projects can be created, processed or deleted.

Read the rest of this entry »

Instructions: clean up NTFS access rights

1. Create project and read in directories

Create new project – Read in directories and authorizations

In migRaven, one always works with projects. A project is a logical unit, which is to be processed, for example a share or a directory below a share. Best is the point which is mounted in case of users or integrated in the DFS. Thus one ensures that all authorizations – including the list authorizations – are correctly created by migRaven. Via the title “Administer projects”, you arrive at the point, where new projects can be created, processed or deleted.

Read the rest of this entry »

Instructions: migrating a file system

1. Create project and read in directories

1.1. Create new project – Read in directories and authorizations

In migRaven, one always works with projects. A project is a logical unit, which is to be processed, for example a share or a directory below a share. Best is the point which is mounted in case of users or integrated in the DFS. Thus one ensures that all authorizations – including the list authorizations – are correctly created by migRaven. Via the title “Administer projects”, you arrive at the point, where new projects can be created, processed or deleted.

Read the rest of this entry »

Step 4: start migRaven and receive trial key

.net, Java, database and migRaven are installed? Request your licence!

After the initial start, migRaven prompts you to enter a license. Please click on Request Test key. You will receive the test license immediately per email.

Read the rest of this entry »

Transferring new access rights to an old share

If the “Green Meadow” cannot become the new storage location for your data, then the new ACLs can be transferred to the old area.

In addition to this, one must state that if need be, it can take a long time and is dependent on the number of files and directories, which should be authorized.

Read the rest of this entry »

database check

The database neo4j used by migRaven requires Java.

In order to consider the status, there is a web-based dashboard. One can reach this dashboard via the link http://localhost:7474 or http://127.0.0.1:7474.

Read the rest of this entry »

Optimizing the migraven database

Like any other database, the neo4j database is faster, if you access data in the main memory, without having to collect it from the hard disk.

For this reason, each customer should adjust the settings for the database individually in its computer. Values of 80% of available main memory are ideal on the computer.

If one for example has 4GB RAM, then the value should be set to 3.2 GB. One can make this setting in the “conf\neo4j-wrapper.conf”. This exists in the directory tree of the database.

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 »

Seite 5 von 7« Erste...34567