by the migRaven-Documentation
ImageMap links take you to the relevant articles in our technical documentation
Permanent link to this post: https://help.migraven.com/schritt-fuer-schritt/
The following overview shows the main functions of migRaven Step by step described. Via an assigned link you have the possibility to get detailed information about each operation. Based on a redesign project, the steps from reading the permissions of a share, editing the rights and creating the authorization and list groups to writing the groups and directories with their authorizations (ACLs) are displayed in an empty share.
Permanent link to this post: https://help.migraven.com/kurzanleitung-windows-filer-ntfs-share-migration/
At a migRavenUpdate, there are three components to consider: the program migRaven, a migRavenDatabase running as a service and the graph.db directory containing the data you have been scanned for. Here is a description of what you need to consider when updating.
If you at the start of migRaven If you see a red flag in the upper right corner, we want to send you a new one migRavenUpdate. In the update box you will find two links. With the one you can see the innovations of the migRaven-Updates, with the other you come to the download page for the new version.
Permanent link to this post: https://help.migraven.com/update-auf-aktuelle-version/
With our company migRaven You can migrate the permissions of Novell servers. This concerns both Novell Netware and Novell OES. The rights of the Novell servers are read out and must be converted into NTFS rights. This actual state is in migRaven read. migRaven migrates the permissions and creates permission and list groups. Finally created migRaven the authorization and list groups in AD and and writes the new directory tree with new permissions. All steps of the Novell migration are described step by step.
To identify the members of the groups listed in the trustee list migRaven An LDAP connection to your Novell server. The prerequisite is that the Novell server works with the LDAP version 3. This was introduced to 1998. migRaven requires the attributes, schemas, and standards set for this release.
The users to be transferred from Novell must be created in Windows AD beforehand.
Permanent link to this post: https://help.migraven.com/von-novell-auf-microsoft/
Microsoft distinguishes between "basic permissions," such as Full Control, Change, Read, Write, Read and Execute, Show Folder Contents, Special Permissions, and "Advanced Permissions," such as Read File, Execute File, Read Attributes, Create Folder, and more
Each extended privilege has a value: Read data = 1, Create Files = 2, Append Data = 4, Read Extended Attributes = 8, ...
The basic permissions are composed of several extended permissions, their value being the sum of the individual permissions. For example, the write right consists of "Create Files" (2), "Append Data" (4), Write Extended Attributes (16), and Write Attributes (256). The value for "Wrire" adds up to 278. "Synchronize" (1048576) results in the value 1048854.
The extended permissions can be clicked together as needed. If a right arises that does not correspond to the basic rights, it is marked under Windows as "special permission".
Only the right "Synchronize" can not be assigned manually by us. Synchronize controls the wait function on the file handle for asynchronous reads and writes and is set only by the system.
Permanent link to this post: https://help.migraven.com/filesystemrights/
It is possible, eg for reasons of space, the migRavenDatabase and the path for the CSV files to another disk as well as to another computer. It is also possible to change the port 7474 for the database.
These changes of the location of the database and the CSV files as well as the change of the port number are made via parameters in the configuration files. For program installations, the configuration files are overwritten, causing your entries to be lost.
Please document your entries and take them after a program installation of migRaven or the database again.
Permanent link to this post: https://help.migraven.com/migraven-datenbank-verlegen/
migRaven and 8MAN (updates 26.10.2016)
For the introduction of 8MAN in structures with more than 150 users, it is usually necessary to prepare the existing file server so that it can be managed with 8MAN at all. 8MAN has a high level of automation that completely manages the management of all required permission groups. But for this to work, all previous permissions must be completely switched to the 8MAN algorithm! Since 8MAN only works directory by directory, there is the program migRaventhat can provide hundreds or thousands of directories with new 8MAN compliant authorizations in one go.
Image 1: Overview
Permanent link to this post: https://help.migraven.com/integration-migration-filer-migraven-8man/
Before installing the new program version, the components of the previous version must be completely uninstalled. First, the database service "migRaven Database "finished.
Then in the Control Panel program and database "migRaven" and "migRavenDB "can be uninstalled. For the shot, the contents of the directory "c: \ Program Files \migRavenDB \ DB \ data "will be deleted. It contains your old data, but it does not fit in the structure to the new version.
Optimization of the creation of GPO group policies.
In the report generator, there is a new AD function for "Checking for recursive group nesting"
The migRavenDatabase can be put on another drive or on another computer.
Under "migRaven Report API"Describes how to list the orphaned SIDs in the scanned directories.
Permanent link to this post: https://help.migraven.com/migraven-release-notes/
New migRavenVersion 5.0: Share migration through Group Policy
We have developed a new project type: the migration of authorizations via group policies!
The permissions are migrated directly to the source share via Group Policy without the directories and data to change or copy. No target share is created. The advantage of this project type is that the authorizations are granted very quickly.
In contrast to the "ReDesign / Scan resource" project type, a Group Policy object is created instead of the "Deploy ACL" in Group Policy Management, which contains the new authorizations for the scanned share. To enable this object, the user must link it to the server being migrated through AD and Group Policy Management.
Permanent link to this post: https://help.migraven.com/gpo-projekt/
The "Deploy GPO" creates a GPO that contains the authorizations to be set. This GPO must be assigned to the appropriate server after creation. The GPO can contain hundreds of entries. Since setting the authorizations via GPO does not use the standard API, which can only process the authorizations one after the other, the new authorizations are set in parallel via the directory tree via GPO. This process is extremely fast and makes it possible to set the rights on a productive system without influencing users.
Permanent link to this post: https://help.migraven.com/erzeugen_microsoft_gpo_zum_setzen_ntfs_permission_deploy-gpo/