Category: 5. Migration Projects

Group Policy Project

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.

1. Advantages, limitations and features

1.1. advantages

Continue reading

Permanent link to this post:

Generate the Microsoft GPO to set the NTFS permissions with DEPLOY GPO

1. Distribute the new NTFS permissions through Microsoft Group Policy (GPO) (Deploy GPO in migRaven)

1.1. Automatically create the Microsoft GPO migRaven

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.

Continue reading

Permanent link to this post:

Project type "Novell Migration"

Work Instructions Novell Migration

A complete guide on how to use the permissions of a Novell server migRaven can migrate to a Windows Share,

can be found under "Work instructions" in the article "From Novell to Microsoft".

Permanent link to this post:

User mapping

You want to transfer permissions from a Novell server to a Windows share.
However, the usernames are not always the same on the Novell server and in Windows AD.
With the user mapping we offer a solution for this.

The solution is to give users an unused AD attribute in which the Novell name is entered for users whose AD and Novell names are not equal. About it finds migRaven the connection.

Continue reading

Permanent link to this post:

The view - the visual representation of the authorization structure

The view is the visual representation of the authorization structure, on the one hand the read in (initial state) and after the "Design & Work" of the planned authorization structure (target state).

1. Initial state - the read authorization structure

The "View initial state" is only part of the "Scan resources" project type. It shows the authorization structure of a read Windows share.

After reading the source directory lands migRaven in view - initial state.
On the left you can move through the directory structure. On the right, you can see the authorized groups and accounts and their rights for the directory selected on the left. Underneath, you can let the members of the groups, the accounts, who are allowed to change, or let all authorized persons be shown on this directory.

Continue reading

Permanent link to this post:

Tables mode

You populate the table with your credentials, whether from a scanned share, Novell permissions, or a self-created Excel spreadsheet. You can edit and change the permissions according to your needs and ideas. You can remove and add directories. You can authorize users and groups with the five default rights to these directories. You can initiate inheritance breaks and redirect directories in the redesign project.

Continue reading

Permanent link to this post:

Rights mapping

After scanning your share, the rights mapping will be displayed if rights have been found in the scanned share that differ from the standard rights. Not only the rights themselves play a role, but also the type of rights (like refuse) and the propagation (the application to this folder, subfolders and files). These rights can be converted into standard rights in the mapping table.

1. The standard rights at migRaven

Right Type Propagation (Apply to)

Read and Execute   Allow this folder, subfolders, files
Write              Allow this folder, subfolders, files
Modify             Allow this folder, subfolders, files
Modify Plus *       Allow this folder, subfolders, files (more about ModifyPlus)

Full Control       Allow this folder, subfolders, files

Continue reading

Permanent link to this post:

Different destination directory

Ab migRaven Version 3.2.1029 makes it possible to redirect directories when migrating a Windows share.

To do this, under Design & Work in table mode, you will find an additional column "Different target directory" next to the (initial) path.
Here you can specify a different directory than the home directory.

In general, the home directory will be replaced by the new directory. The permissions are applied.
Subdirectories under it are taken over, up to the level in which a different target directory may be specified.

Continue reading

Permanent link to this post:

Rolemining function in the Novell migration

Conversion of all Novell rights information

Under Novell you can also set permissions (trusts) on objects other than just users or groups. To avoid losing information when migrating from Novell Fileserver to Microsoft Filer, see migRaven integrated an intelligent Rolemining mechanism.

1. migRaven works as follows

  1. It must be the group type for the permission groups in migRaven Domains, Global, or Universal groups are available
  2. Definition of the name concept for the authorization groups

Continue reading

Permanent link to this post:

Drag and drop

Drag & Drop displays the scanned permissions in a directory tree.

This feature is characterized by the fact that user and group names no longer need to be written. You can search for objects in the AD, park them in a clipboard and drag them from there or from a directory of the initial state to a destination directory and drop them there, hence "drag and drop".

Continue reading

Permanent link to this post:

Load more