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.
For both server operating systems, whether Netware or OES, it is common that for every volume there is a specific trustee-file. It contains the directory names, the permissions on that and the authorised users, groups and OUs. These files, as already mentioned, are converted into a CSV-file and can thus be processed as a table in migRaven.
These files do not contain the members of the groups and OUs. Therefore a second step is necessary.
2. A LDAP-link to the Novell-Server
Via a LDAP-interface, the link to the Novell eDirectory is created. Moreover migRaven can determine the Container members. In addition to this, the parameters for the connection setup to the Novell server must be specified in the group configuration with the rider “Novell”.
Three specifications are required:
– The address of the Novell Server (IP-Address or Server-Name) with LDAP-Port, for example 192.168.0.40:389.
– The User name with fully qualified name (distinguished name, DN), for example CN=admin,OU=Berlin,O=aikux.
The admin who logged in here must be in the same organization (o=firma) as the groups and users, which are to be dissolved.
You should save the data here. The parameters are still available after a program update.
The password is not stored. You must specify it again in case of each project for Novel migration.
For the groups and container specified in the .trustee_database, migRaven collects the member names from the eDirectory of the Novell Server. Then migRaven checks whether these are available as users with same name in the Active Directory of the Windows-Server. If not, it is acknowledged with an error message in the Status column.
Find further information in the Work instruction for Novell-Migration with migRaven..