Microsoft KB Archive/301542

= How To Migrate Users from NetWare to Windows 2000 with the MSDSS Tool and One-Time Migration =

Article ID: 301542

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



This article was previously published under Q301542



IN THIS TASK
SUMMARY
 * Installing the Novell Client and Installing MSDSS
 * Performing the One-Way Migration
 * Troubleshooting

REFERENCES



SUMMARY
This step-by-step guide describes how to migrate user accounts, settings, and objects from a NetWare 3.x, 4.x, or 5.x server to a Windows 2000-based server by using the Microsoft Directory Synchronization Services (MSDSS) tool and a one-way migration.

The MSDSS tool is located on the Services for NetWare CD-ROM, which you can order from the following Microsoft Web site:

http://www.microsoft.com/windowsserver2003/sfn/default.mspx

back to the top

Installing the Novell Client and Installing MSDSS

 * 1) Install the Novell Client for Windows 2000 from the Novell Web site (http://www.novell.com/download/). For additional information about installing this client, please contact Novell.
 * 2) Install Microsoft Directory Synchronization Services from the Microsoft Services for NetWare (version 5.0) CD-ROM by double clicking the Msdss.msi file in the Msdss folder on the CD-ROM.
 * 3) Click Next, and if you agree to the license agreement, click Next again.
 * 4) Make sure that Microsoft Directory Synchronization Service is selected, and then click Next.
 * 5) Type your name and organization, and then click Next.
 * 6) Click the Typical installation option (the custom installation option only gives you the option not to install the Help files), click Next, and then click Next.
 * 7) After the installation is finished you can either open the Readme file or click Finish.

back to the top

Performing the One-Way Migration
 Click Start, point to Programs, point to Administrative Tools, and then click Directory Synchronization. In the console tree, right-click MSDSS, and then click New Session to start the New Session Wizard. On the Synchronization and Migration Tasks page, under Select NDS or Bindery, choose whether objects will be copied from NDS or Bindery. Under Select a task, click Migration (from NDS or Bindery to Active Directory), and then click Next.

If files will be migrated with directory objects, you need to click to select the Migrate Files check box. This will create the file migration log that is required by File Migration utility. On the Active Directory Container and Domain Controller page, under Active Directory container, type the path to the container in which you want to copy items, or click Browse to locate the Active Directory container.

Use the syntax in the following example to type the path:

LDAP://OU= ,DC= ,DC= ,DC=com

All subcontainers in the selected containers will be copied.

 Under Domain Controller, 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. On the NDS Container and Password or Bindery Container and Password page, type the appropriate NDS or Bindery syntax as indicated below, or click Browse to locate the container or server:

'''NDS://Tree1/O= /OU=

NWCOMPAT:// '''

</li> Under User name, type the name of the administrative account. In the Password box, type the password for that account, and then click Next.

You must type the NDS administrative account by using the full NDS context, such as &quot;Admin.wingtip&quot;. Do not include the NDS tree name.</li> On the Initial Reverse Synchronization page, click Password Options, and then click one of the following password schemes: <ul> Set passwords to blank</li> Set passwords to the user name</li> Set passwords to a random value</li> Set all passwords to the following value</li></ul>

If you do not select a scheme, the default Set passwords to the user name scheme is applied. After you have selected a password scheme, click OK, click Next, and then click Finish.</li></ol>

NOTE: Whether the migration is successful or errors occur, you can view the logs after the wizard finishes by clicking View Logs. Or, you can view the same logs in the Application log in Event Viewer.

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

back to the top

Troubleshooting

 * MSDSS requires the Novell client and cannot interoperate with solutions that use Gateway Services for NetWare (GSNW).
 * If you install MSDSS on a computer that is not a domain controller and the computer is running Microsoft Windows 2000 Professional or Windows 2000 Server, only the MSDSS console is installed, not the Directory Synchronization service.
 * When you are installing MSDSS on a Windows 2000-based domain controller, Setup detects the domain controller and attempts to update the schema even if you are attempting to install only the MSDSS console. However, when you are installing MSDSS on a Windows 2000 Professional-based or Windows 2000 Server-based computer (that is not a domain controller), you do not need to update the schema as part of the installation process.
 * Quit all programs, including any antivirus software, before you install MSDSS.
 * Active Directory organizational units and NDS containers cannot be created by using this wizard. Use the Windows 2000 Active Directory Users and Computers snap-in to create organizational units; use NetWare administrative tools to create NDS containers.
 * NDS and Bindery do not allow user passwords to be read. Therefore, you need to choose a password assignment scheme to specify how passwords will be assigned in Active Directory after they have been migrated from NDS or Bindery.
 * The wizard displays all NDS trees on the network, even if no common protocol is available between that tree and Windows 2000. For example, a computer that is running Windows 2000 Server with only TCP/IP displays IPX-only trees, but you cannot browse them.

back to the top

<div class="references_section">