NIS Migration Wizard Prevents Multiple Migrations to a Non-Standard Container (322869)

The information in this article applies to:

Microsoft Windows Services for UNIX 3.0

This article was previously published under Q322869

SYMPTOMS

After you migrate a Network Information Service (NIS) map to a non-standard container, the NIS Migration Wizard does not allow future attempts to migrate maps for the same domain to a non-standard container.

RESOLUTION

Use the command-line migration tool to migrate subsequent NIS maps to the non-standard container.

The following is a syntax example:

nis2ad -a <migrated domain name in AD> -y <domain name in 
NIS> -t <non-default container specified earlier> -m 
<map>

In the following example, the group map from the NISDomain domain is being migrated into the uk/co/bbc/mags5/Magazines/NISMigration Active Directory container:

nis2ad -a MigratedDomain -y NISDomain -t "CN=NISMigration,CN=Magazines,DC=mags5,DC=bbc,DC=co,DC=uk" -m 
group

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Server for NIS allows NIS map data to be migrated to Active Directory. During installation, Server for NIS extends the Active Directory schema. After the migration, and upon receiving NIS requests from clients or other servers, Server for NIS searches Active Directory to reply to NIS queries.

The Migration Wizard and nis2ad read map data from NIS map source files, the plain text files from which the NIS map databases are compiled. These source files must be located where they can be accessed by the domain controller during migration, such as on a disk on the domain controller or in a shared directory that is accessible by the domain controller.

Modification Type:	Major	Last Reviewed:	6/3/2002
Keywords:	kbenv kbprb KB322869