Migrating NetWare 4.x, 5.x, or 6.x Files to Active Directory

Updated: September 15, 2010

Applies To: Windows Server 2008 R2

To migrate NetWare 4.x, 5.x, or 6.x files to Windows Server 2008 R2 Active Directory, follow these steps:

  1. On the Windows Server 2003 R2 domain controller, click Start, point to All Programs, point to Administrative Tools, and then click File Migration Utility.

    The server performs an initial check for connectivity and logon IDs.

  2. Click Next to continue the file migration.

  3. On the Migration Log Selection page, click Browse to select the migration log that is used as the template for file migrations.


The migration log is the log file generated during the previous migration of accounts and groups.

In a default installation of Windows Server 2008 R2 and MSDSS, the file migration logs are placed in the *%systemroot%\\system32\\Directory Synchronization\\Session Logs* directory. The file migration logs are sequentially named “1.txt, 2.txt, 3.txt, and so on.”  
  1. On the Migration Log Selection page, select the Validate Active Directory maps check box, and then click Load Data.

  2. To display the NDS to Active Directory accounts mappings, click View Maps.

  3. Confirm the mappings, and then click Close.

  4. To adjust the Novell to Active Directory permissions mapping, click Access Rights.

  5. By default, the Windows Read permission is made equivalent to Novell Modify. The Novell Modify permission can also be made equivalent to the Windows Read with Write permission combination. To increase the Modify permission mapping to include Read with Write, in the Access Rights dialog box, select the Write check box, and then click OK.


Because Novell file permissions do not identically map to Windows Server 2008 R2 file permissions, you have the option of changing the extent of rights of the Novell Modify permission.

  1. The Security Accounts for Migration (Optional) page makes it possible for you to verify the NetWare Server to which you are attached and to change the NetWare supervisor account information that you use to attach to the server.

    This page also displays the Active Directory user name that you used to log on and makes it possible for you to change Novell login script behavior and to attach to the system via dial-up connections.

  2. Click Next to continue.

  3. The Source and Target Volume Migration page appears. In the boxes, select the source(s) and target(s) of the volumes or folders that you want to migrate from Novell to Active Directory.

    As shown in the following illustration, in the Source (NDS/Bindery) box, you can see a partially expanded view of an NDS tree. In the Target (Active Directory) box, you can see a partially expanded view of an Active Directory forest.


If the NDS volume you selected in the source tree indicates Unavailable, you are not currently logged on to that tree. Log on, and then continue the migration.

In the **View computers of type** box, select the type of computer that the user’s files are migrated to. For example, in this sample, the Domain Controllers and Member Servers choices determine the list of available selections shown in the **Target (Active Directory)** box.  
  1. Identify and select the appropriate source and target locations for each volume or folder to be migrated. After you select each source and target directory, click the Map button in the center of the page.

    The following screen shows the Novell NDS Tree and Active Directory Forest expanded. The “Data” source directory is selected for migration to the Active Directory target directory of the same name.

    In this example, the source directory is an NDS shared volume; the target share is a shared folder on a Windows Server 2008 R2 domain controller that was created before the migration process.

    As the shared volumes or folders are mapped, their mapping information is displayed in the Migration order of maps box.

    The data mappings can be reordered or even deleted and remapped if necessary.

  2. After all of the mappings are complete, click Next to continue.

  3. On the Log Settings (Optional) page, select the Enable logs check box. Set the desired log file settings, or accept the defaults.


While logging is optional, it is recommended that you enable logging for the migration. You can then select other options that are available on the page, such as the file naming attributes. The results from the logs can be reviewed at a later time if needed.

  1. Click Next to continue.

  2. On the Source Files and Target Verification page, click Scan to verify that the source and target objects are valid and that the target disks have enough space available. The following screen shows the results of a scan.


Although there is an option to bypass errors while scanning, it is recommended that you not use this feature on the first scan if at all.

  1. After the scan is complete and you have reviewed the results, click Next to continue.

  2. On the Start Migration page, click Migrate. The following screen shows the results of a successfully completed migration.

    An unsuccessful migration might display a screen similar to the following:

    Notice that after an unsuccessful migration, the Next button is unavailable. If the migration is unsuccessful, you must correct the errors and perform the migration again.

  3. Review the results, and then click Next to finish.

  4. The results of a File Migration Utility migration are displayed as shown below. Review the results of the file migration, and then click Finish.

  5. To close this window, click Finish. The Confirm dialog box appears, prompting you to save a log file.

  6. Click Yes (recommended), or make another selection.

  7. If you click Yes, in the dialog that appears, specify the name of the log file, and click Save. The log file is saved, and the File Migration Utility closes.

    This completes the migration process.