Appendix A - NetWare 3.x Migration

Published: September 15, 2010

Updated: September 15, 2010

Applies To: Windows Server 2008 R2

NetWare 3.x services typically include file, print, and limited Internet services. NetWare 3.x environments use binderies to store user account and other resource information and are maintained on each server in the network. However, replication of account information is not provided. Individual implementations of bindery services normally include file and print services; however, older versions of messaging, applications, and databases might also be present that rely on NetWare 3.x services.

Migration of Bindery environments is simpler than migration of other Novell environments, because only a small number of services are subject to migration. Further, migration from NetWare Bindery to Windows Server 2008 R2 Active Directory is almost always desirable unless some specific application or service prevents the migration. Such scenarios could occur when you migrate an application such as Novell GroupWise. In this situation, some additional planning might be required.

If migration is not an option, you can implement interoperability easily at several levels. The Windows Server 2008 R2 operating system includes support for connecting to NetWare Bindery servers or for using MSDSS to synchronize accounts with the Windows Server 2008 R2 Active Directory.

To perform a direct (non-staged) Accounts and Groups migration from a Novell NetWare 3.x Server Bindery to the 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. MSDSS starts.

    The MSDSS MMC snap-in appears with your Active Directory Forest name in parentheses on the title bar.

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



    MSDSS New Session

  3. On the Welcome to the New Session Wizard page, click Next to continue with the accounts and groups migration.



    New Session Wizard Welcome screen

  4. On the Synchronization and Migration Tasks page, choose the following three settings:

    1. On the Synchronization and Migration Tasks page, in the Select NDS or Bindery list, click Novell Bindery.

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

    3. Under Select a task, select the Migrate Files check box. This will create the file migration log required by File Migration Utility.

      noteNote
      The Migrate Files check box is selected. This setting does not force you to immediately migrate the files, but rather creates a text log file to be used later for the file migration when you are ready to migrate files. It is recommended that you select Migrate Files, even if the timeframe for file migration is not yet decided.

    Your screen should look like this:



    Novell Bindery

    noteNote
    If files are to be migrated with directory objects, you must select the Migrate Files check box. 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. Record the Migrate Files log locations—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.)

  6. On the Active Directory Container and Domain Controller page, click Browse to select the Active Directory Container in which you want to place the migrated NetWare Users and Groups.



    Active Directory Container

  7. In the Select an Active Directory Container dialog box, browse to select the object container that will store the NetWare Users and Groups.



    Select an Active Directory Container

    noteNote
    You cannot use MSDSS to migrate the NetWare Users and Groups into the Active Directory Domain Users object. If you have not already created the object container that the NetWare Users and Groups are to be placed into, you can do so now by opening the Active Directory Users and Computers MMC snap-in and creating it, and then re-opening the Select an Active Directory Container dialog box to select the new object container.

  8. On the Active Directory Container and Domain Controller page, under Active Directory container, type the path to the Active Directory container to which you want to copy items, or click Browse to locate the container.



    Active Directory Container

    noteNote
    All sub-containers of the selected containers are copied.

  9. In the Domain controller box, accept the default domain controller in which you want to store the migration log, or click Find to locate a different domain controller to store the log, and then click Next.

  10. On the Bindery Container and Password page, click Browse to select the NetWare Bindery Server that you want to migrate.



    Bindery Container and Password

  11. In the Browse for bindery server dialog box, browse to select the bindery server that you want to migrate, and then click OK.



    Browse for bindery server

  12. After you select the bindery server, the Bindery Container and Password page reappears. Click Next to continue.



    Bindery Container and Password

  13. In the User name and Password text boxes, type the Novell Administrator account and password that you want to use for synchronization, and then click Next.

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



    Initial Reverse Synchronization

  15. In the Password Synchronization Options dialog box, click the appropriate option, and click OK.



    Password Synchronization Options

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

    For an extended description of the four password options, see the “MSDSS Password Management” section of this document.

  16. On the Initial Reverse Synchronization page, click Next.

  17. To complete the migration of NetWare Bindery User Accounts and Groups to Active Directory, on the Completing the New Session Wizard page, click Finish.



    Completing the New Session Wizard

  18. The Synchronize dialog box informs you when the migration is complete. For more information on the migration, click View Logs, or click OK to complete the migration.



    Synchronize

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

  20. 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.



    Active Directory Users and Computers

  21. Close Active Directory Users and Computers.

To migrate NetWare 3.x files to Windows Server 2003 R2 domain controller, follow these steps:

  1. Start the File Migration Utility by clicking Start, point to All Programs, point to Administrative Tools, and then click File Migration Utility.



    File Migration Utility

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



    File Migration Utility Welcome page

  2. Click Next to continue the file migration.

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



    Migration Log Selection page

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

    In a default settings installation of Windows Server 2003 R2 and MSDSS, the file migration logs should be located 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.”

  4. On the Migration Log Selection page, select the Validate Active Directory maps check box, and then click Load Data.



    Validate Active Directory maps

    This step confirms that the user mappings work with the file migrations. See the following screen shot for more detail.

  5. To display the Novell to Active Directory user mapping, click View Maps.



    View Maps

  6. Confirm the mappings, and then click the Close button.



    Mappings

  7. To make adjustments to the Novell to Windows Active Directory permissions mapping, click Access Rights.

  8. 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.



    Access Rights

    noteNote
    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 that the Novell Modify file permission has.

    By default, the Windows Read permission is made equivalent to Novell Modify. The Novell Modify command can also be made equivalent to the Windows Read with Write permission combination.

  9. To skip the Security Accounts for Migration (Optional) page, click Next.



    Security Accounts for Migration

    noteNote
    This optional page makes it possible for you to verify the NetWare Server you are attached to and change the NetWare supervisor account information you use to attach to the server. It also displays the Active Directory user account with which you are logged on to the Windows domain, makes it possible for you to change Novell login script behavior, and makes it possible for you to attach to the system via dial-up connections.

  10. On the Source and Target Volume Migration page, browse for and select the NDS or Bindery source object and the Active Directory target object.

    The following screen illustrates a partially expanded Novell Bindery to Active Directory migration screen. The left side of the screen shows the Novell NetWare 3.x Server SYS volume view, partially expanded. On the right side is the Active Directory Forest view, partially expanded.

    If the Windows file share that you are migrating to is located on a domain controller or workstation, verify that the Domain Controllers check box and Workstations check box are selected.



    Source and Target Volume Migration

    noteNote
    If the Bindery volume you that select in the source tree indicates Unavailable, then you are not currently logged on to that Bindery server. Log on, and then continue with the migration.

  11. Identify and select the appropriate source and target locations for each user to be migrated. After you select each user’s source and target directory, click the Map button in the center of the page.

    In the View computers of type box, select the type of computer that the user’s files are migrated to. In the figure shown, the selections made for View computers of type (Domain Controllers and Member Servers) affect the selections shown in Target (Active Directory) box.

    On the following screen, the Novell Server and Active Directory Forest is expanded, and the sample user ANNEPA’s source directory in NetWare and the Active Directory target directory are selected.

    In this example, the source directory is user ANNEPA’s home directory; the target directory was created in a shared folder on a Windows Server domain controller before or during the migration process.



    Source and Target Volume Migration

  12. In the following screen, the source and target for the user ANNEPA have been selected, and Map has been clicked.



    Source and Target Volume Migration

  13. In the Migration order of maps box, confirm the data mapping that occurred.

  14. Assume that after the user ANNEPA was mapped, two more sample users, DONHA and FUKIKOOG, have been mapped for migration by selecting both their unique source and target directories.

    As the users are mapped, their data mapping information is displayed in the Migration order of maps field. The data mappings can be reordered or even deleted and remapped if necessary.



    Source and Target Volume Migration

  15. When all of the user mappings are complete, click Next to continue.

  16. On the Log Settings (Optional) page, select the Enable logs check box.



    Log Settings

    noteNote
    It is recommended that you enable logging for the migration. You can then select other options, such as the file naming attributes. The results from the logs can be reviewed at a later time if needed.

  17. Click Next to continue with the migration.

  18. On the Source Files and Target Verification page, click Scan to confirm that the system is ready to migrate the files.



    Source and Target Volume Migration

    noteNote
    The system verifies that the target roots and source objects are valid, and that the target disks have enough space available. Although there is an option to bypass errors during a scan, it is not recommended that you use it on the first scan, if at all.

  19. After the scan is complete and you have reviewed the results, click Next to proceed with the file migration.

  20. On the Start Migration page, click Migrate to begin the file migration.

    The following screen shows the results of a completed migration:



    Start Migration

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

  22. On the Completing Migration with File Migration Utility page, review the results of the file migration, and then click Finish to close the utility.



    Completing Migration

Community Additions

ADD
Show: