migRaven can be used to migrate Novell file server structures to Microsoft. The advantage of moving with migRaven is the automatic transfer of the authorizations to Microsoft with simultaneous construction of all necessary authorization groups and list permissions, so that the access authorizations under Windows function almost exactly as under Novell.
The migration takes place in two steps. First, the permissions must be obtained from the Novell server. There are differences between Netware and OES. In the second step triggers migRaven Through an LDAP connection to the Novell server, groups and replace them with members. This requires admin rights.
To get authorization information from the Novell server, two ways are necessary:
1. Acquisition of the trustee files from the Novell server
Depending on the Novell version, the trustee data will be adopted in different ways. At Netware can with the Trustee.nlm create a CSV file that contains the required trustee information. The content of the file must be for migRaven however modified. On Open Enterprise Server are trustee files named .trustee_database.xml already available. For the conversion into a CSV file we provide a PowerShell script. Problem: Novell has changed the structure of the xml file over time, so the PowerShell script needs to be customized according to the OES version.
Both server operating systems, whether Netware or OES, have in common that there is a separate trustee file for each volume. It contains directory names, the access rights to them, and the authorized users, groups, and OUs. This file is, as already mentioned, converted into a CSV file and can be edited as a table and in migRaven be read.
This file does not tell us the members of the groups and OUs. Therefore, a second step is required.
2. An LDAP connection to the Novell server
An LDAP interface connects to the Novell eDirectory. About it can migRaven determine the container members. To do this, the parameters for connecting to the Novell server must be specified in the group configuration in the "Novell" tab.
Three details are required:
- the address of the Novell server (IP address or server name), eg 192.168.0.44
- LDAP port, only port 389 is supported
- the Name of the admins with fully qualified name (DN), eg CN = admin, OU = Berlin, O = aikux.
The admin that logs in here must be in the same organization (o = company) as the groups and users that are to be resolved.
You should save the data here. Even after a program update, the parameters are still available.
The password is not saved. You will need to re-enter this for every Novell migration project.
For the groups and containers specified in the .trustee_database will bring migRaven the member names from the eDirectory of the Novell server. Then check migRavenwhether they exist as a user with the same name in the Active Directory of the Windows server. If not, this is acknowledged with an error message in the status column.
In the right part, an alternative attibut can be selected in case a user's Novell and Windows logon names are not identical. For detailed information, see User mapping.
For detailed information about Novell migration, see Working Guide to Novell Migration with migRaven.