Directly Migrating NetWare 4.x, 5.x, or 6.x NDS

Updated: September 15, 2010

Applies To: Windows Server 2008 R2

The following procedure illustrates a direct, non-staged, step-by-step migration of a NetWare 5.x or 6.x NDS object container to Windows Server 2003 Active Directory. The NetWare 4.x migration is similar. In this example procedure, an NDS object that contains user accounts and groups is migrated into a similar OU structure in Active Directory. The user accounts and groups are migrated to Active Directory by using MSDSS.

To perform an Accounts and Groups migration from a Novell NetWare 4.x, 5.x, or 6.x NDS Server to an Active Directory using MSDSS on the Windows Server 2003 functional domain, follow these steps:

1. On the Windows Server 2003 R2 domain controller with MSDSS installed, click Start, point to All Programs, point to Administrative Tools, and then click Directory Synchronization.

   

   The MSDSS management console appears, with your Active Directory Forest name in parentheses on the title bar.

2. To start the New Session Wizard, from the MSDSS console tree, right-click MSDSS (Your Active Directory Forest Name), and then click New Session on the shortcut menu.

   

3. The Welcome to the New Session Wizard page appears. Click Next to continue.

   

4. The Synchronization and Migration Tasks page appears.

   

   1. From the Select NDS or Bindery drop-down list, select Novell Directory Services (NDS).

   2. Under Select a task, click Migration (from NDS or Bindery to Active Directory).

   3. Select the Migrate Files check box.

Note

When you select the Migrate Files check box, the file migration log that is required by File Migration Utility will be created. Creating the migration log does not force you to immediately migrate the files; the text log file is created for later use during the file migration. It is recommended that you select the Migrate Files check box, even if the timeframe for file migration is not yet decided. If you intend to migrate files with directory objects, then you must select the Migrate Files check box.

4.  Record the **File Migration Log** location—you are prompted for the file names and their locations when you use File Migration Utility. (If you have not recorded them, you can search for them on the disk at that time.)  
      

Note

In a default settings installation of Windows Server 2003 and MSDSS, the file migration logs are placed in the “%systemroot%\system32\Directory Synchronization\Session Logs” folder. The file migration logs are sequentially named “1.txt, 2.txt, 3.txt, and so on.”

5. When you have completed your selections, click Next.

6. The Active Directory Container and Domain Controller page appears.

   

   1. Click Browse to select the Active Directory container in which you want to place the migrated NetWare Users and Groups.

Note

The New Session Wizard does not permit you to migrate the NetWare Users and Groups into the Active Directory Domain Users object container. If you have not already created an object container into which you want to place the NetWare Users and Groups, you can do so without canceling the New Session Wizard by opening the Active Directory Users and Computers Microsoft® Management Console (MMC) snap-in and creating the object container. You can then re-enter the Select an Active Directory Container screen to select the new object container.

2.  Select the Active Directory object that you created to contain the NetWare Users and Groups, and then click **OK**.  
      

Note

All sub-containers of the selected containers are copied.

    You are returned to the Active Directory Container and Domain Controller page, and information for the Active Directory container you selected is displayed.  
      
      
      
    ![](images/Ff978903.e2217dae-3511-4a52-98b9-a3abf607857d(WS.10).gif)  
      
3.  In the **Domain controller** box, accept the default domain controller to store the migration log, or click **Find** to select a different domain controller to store the log.  
      

7. When you have completed your selections, click Next.

8. On the NDS Container and Password page, click Browse to select the NDS container that you want to migrate.

9. In the Browse for NDS Container dialog box, select the NDS container that you want to migrate. Click OK.

   

Note

All sub-containers of a selected NDS container are copied to the specified Active Directory OU.

10. On the NDS Container and Password page, enter the Novell administrator account User name and Password to be used for synchronization. Click Next to proceed.

    

Important

The NDS administrative account must be typed using the NDS context. The account ID syntax must be entered as follows:
The account to be used is admin, the container it is a member of is Sales, and the NDS tree is CompanyTree:
Example, enter admin.sales, not admin.sales.companytree.

11. On the Initial Reverse Synchronization page, click Password Options.

    

12. In the Password Synchronization Options dialog box, click the appropriate password scheme. For an extended description of the four password synchronization options, see the “MSDSS Password Management” section of this document.

    

Note

NDS and Bindery do not allow user passwords to be read. Therefore, you must choose a password assignment scheme to specify how passwords are assigned in Active Directory once they have been migrated from NDS or Bindery.

13. After you have selected a password scheme, click OK, and then click Next.

14. On the Completing the New Session Wizard page, click Finish to complete the migration of Novell NDS User Accounts and Groups to Active Directory.

    

15. The Synchronize dialog box informs you that the migration is complete.

    

16. From the Synchronize dialog box, click View Logs for more information on the migration, or click OK to complete the migration.

17. To confirm the migration of accounts and groups, start Active Directory Users and Computers.

    

18. In Active Directory Users and Computers, click the Active Directory object into which the Accounts and Groups were migrated. Confirm their existence and their proper group memberships.

19. Close Active Directory Users and Computers.