Microsoft KB Archive/176199

{| The information in this article applies to:
 * width="100%"|
 * Microsoft Windows NT Server versions 3.51 4.0

SYMPTOMS
After you perform a trial migration by migrating from a NetWare 4.10 or 4.11 Server using the Migration Tool for NetWare, the Migration Summary Window displays the following information:

Transfer Completed Totals Migrations Completed  1 Groups Transferred:   0 Users Transferred:    0 Files Transferred:    xxxxxx Errors:               2 The Error Log displays the following information: [NWServer Name -> NT Server Name] Error:  Getting Groups on Server: NWServer Name Error:  Getting Users on Server:  NWServer Name

CAUSE
This behavior can occur because the Nwconve.exe program (the Migration Tool for NetWare) does not support the NetWare Directory Services (NDS) service type of login on Windows NT 4.0. You must have bindery emulation configured on the NetWare server in order to be migrated properly.

RESOLUTION
To resolve this issue, enable bindery emulation on the NetWare server. To do so, use the following steps:

  Check to determine if Bindery Emulation has been configured on the NetWare Server you want to be migrated. To do so, use the following steps: a. Load Servman at the NetWare Server Console. b. Click [Server Parameters] from the menu options. c. Click [Directory Services] from the menu options. d. Scroll through Directory Service Parameters to the [Bindery Emulation] section. If there is no SET statement to the right of     this entry, than bindery emulation has not been enabled. NOTE: You can also type the CONFIG command at the NetWare server console to determine if a bindery context has been set.   Enable bindery emulation. To do so, use the following steps: a. While in Servman under the proper menu selection (Server      Parameters/Directory Services/Bindery Emulation), press ENTER. A     text entry box appears where you can type in a set statement similar to the following SET BINDERY CONTEXT = =USERS.=TREE

where  is the name of the Organizational Unit users are pulled from, and  is the name of the Organization (TREE) where the OU     resides.  Log off of the Windows NT Server, and then log back on. Trial Migration should proceed normally.

MORE INFORMATION
With bindery services, NDS imitates a flat structure for leaf objects within a set of Organization (O) and Organizational Unit (OU) objects. Thus, when bindery services are enabled, all objects within the specified container's bindery context can be accessed by NDS objects and by bindery-based servers and client workstations.

The container object where bindery services is set is called the bindery context. You can change the bindery context by using the appropriate parameters with the SET or SERVMAN server utility.

Specify one or more containers to be used by NetWare Directory Services when it provides bindery services. Maximum: 256 characters. Up to 16 contexts. Multiple contexts are separated by semicolons.

Examples
SET BINDERY CONTEXT=ACCT.HQ.ACME SET BINDERY CONTEXT=OU=SALES.O=COMPANY;OU=AR.OU=ACCOUNTING.O=COMPANY
 * }

-

Last reviewed: July 16, 1998

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.