migRaven Version 3.2.1019 and Database Version 126.96.36.199
The database version 188.8.131.52 belongs to migRaven version 3.2.1019. This runs with Java 8, 64bit-Version.
1.1. System Requirements
With reference to the hardware 8 GB RAM and minimum 2 core is needed.
The pre-requisite for version 3.2 is Java 8, 64 bit, and a 64bit- (Windows-) operating system.
Further a .NET framework version 4.52 is required.
1.2. Database Service
The database version 184.108.40.206 belongs to migRaven 3.2.1019. The service is called “migRavenDB” and displayed as “migRaven Graph Database”.
Version 2: starting from migRaven Version 2.1.1042.2 and 8MAN Version 5.6.147 , As on: 20.11.2014
Image 1: Overview
migRaven Version 5.0.1003, Database-Version 220.127.116.11, Release Date 05/17/2016
Prior to installing this new version of migRaven, any previous versions, currently installed, will need to be completely removed. To begin with, stop the “migRaven Database” service.
Then “migRaven” and “migRavenDB” can be uninstalled using ‘Programs and Features’ from the Control Panel in Windows. Finally, the contents of the following directory need to be deleted: “c:\Program Files\migRavenDB\DB\data”. It contains data from the old version of migRaven, which is no longer compatable with this release.
After these steps have been completed, the new version and database can be installed (in any order).
The biggest change in this release of migRaven is the “GPO” project (Group Policy Object), which migrates Share permissions assisted by Group Policies. This makes it possible to process enormous amounts of data in under an hour. The new permissions are saved to the original Share and the old permissions are deleted. This is in contrast to the “Redesign-Project”, which requires the creation of a new, empty Share. Therefore, the need to copy data is eliminated.
Go to “Group Policy Project”
The view is the visual representation of the authorization structure, once the read (initial state) and after the “Design & Work” the planned authorization structure (new state).
1. Initial state – the read authorization structure
The “View initial state” is the only component of the project type “Migration per Scan”. It shows the authorization structure of a read Windows-Share.
After reading the output directory, migRaven lands in the View – initial state.
You can move on the left side by the directory structure. On the right hand side you see the authorized groups and accounts and their rights for a directory selected on the left hand side. Below that you can display the members of the groups, the accounts, you may change or all members entitled to this directory.
1. Mapping Permissions
The first step in the table mode is the mapping of permissions.
Only then can you fill your table to set permissions.
2. Filling Table
The data is inserted here depending on the type of project. In case of “Scan Your resources“, the data is taken over from the initial state with the help of the button “Start filling”. The excel tables can be read in the “Import or create a table” and “Novell-migration“.
Further in all the types of projects it is possible to manually insert rows and change values. Here you must pay attention to the syntax of the field content and the column headers.
After scanning your shares the permission mapping table is displayed, if in the scanned share permissions were found, which deviate from the standard permissions. These permissions can be converted into standard permissions through the mapping table.
1. The standard permissions for migRaven
Permission type Propagation (applicates to) Read and Execute Allow this folder, sub folder, files Write Allow this folder, sub folder, files Modify Allow this folder, sub folder, files Modify Plus* Allow this folder, sub folder, files (more about ModifyPlus) Full Control Allow this folder, sub folder, files
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.