Category Archive: 1. Project Types

Project typ “Novell Migration”

Case Instructions Novell Migration

You can find our complete Novell migration instructions here: Instructions – from Novell to Microsoft

Role Mining Novell Trustees

1. Converting all Novell Rights Information

Under Novell one can place permissions (Trusts) on other objects than only on users or groups. We integrated an intelligent role mining mechanism into migRaven, which guarantees that no information is lost, but all translated into suitable permission group structures, which corresponds with Microsoft Best Practice.

1.1. This is how it works:

  1. The group type for the permission group is defined in migRaven: Domain local, global, or universal groups are available for selection
  2. Definition of the name concept for the permission groups

Read the rest of this entry »

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

Read the rest of this entry »

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.

Read the rest of this entry »

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.

Read the rest of this entry »

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:

 

Depth

Path

Read and Execute

Write

Modify

Modify Plus

Full Control

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

Read the rest of this entry »

ACL Errors

If errors appear during scanning your shares, then these are listed during scanning.

Frequent errors are for example, too long path names. The path name is composed of the computer names and all directory names down to the lowest directory. The complete length must not exceed 260 characters.

An additional problem could be that despite administrator rights you have no access to a directory. (Only the legitimate owner has the rights, the administrator has none.) In that case, the error message “Access to ACL not permitted” appears.

Read the rest of this entry »

Project Management

What exactly is a project?

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.

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.

In the project management, you find your projects that have been started and generated. You can find your project again quickly with a meaningful project name.
Further the time of the previous processing, the source- and the target-path are displayed.

Read the rest of this entry »

Navigation with migRaven

References for navigation and workflow in migRaven

Start display

Illustration: Navigation in migRaven

Read the rest of this entry »

The Green Meadow

1. Necessity of the “Green Meadow”

If the authorizations of a share are to be migrated to a server, then there are two possibilities. Either one migrates within the share or one creates a target share parallel, which one designs and which one finally names the source share. The first variant is possible with migRaven, contains however old and new authorizations and requires rework. The second variant with the structure of a parallel share is only sensible. Then which name should one give to the parallel share? Should the source share be renamed anyway, one simply give the target share the new name. The name should mostly be maintained, i.e. the target share should retain the same name like the source share. Two same release names on a server are however not possible. Thus the new share gets first any name, e.g. “Green Meadow”. After the migration, i.e. after creating the authorizations and after copying the data, the old share must be renamed and the new share can maintain the original name of the old share.

Read the rest of this entry »