This step-by-step article describes how to migrate existing Network Information System (NIS) Maps to Server for NIS in a UNIX-to-Windows migration. Server for NIS integrates the NIS master role into the Active Directory. With this integration you can migrate an existing NIS domain to Active Directory. You do this to allow administration of the NIS domain by using either the Microsoft Management Console (MMC) interface or commands that are run from the command line with the Nisadmin.exe utility and the Nismap.exe utility.
Server for NIS includes a utility with which you can migrate an existing NIS domain to Active Directory. With this utility, you can run a "test" migration. The test migration checks all of the available NIS maps and then writes to a file information about the conflicts that are found without actually performing the migration. You can test the migration and make any adjustments that are indicated before you actually perform the migration.
To migrate existing maps to Server for NIS:
Log on to the Server for NIS computer with an administrator-level account.
Click Start, click Run, type cmd, and then click OK.
To run a test migration on the current server, type nis2ad -y UNIX NIS domain name -a Active Directory NIS domain name -c c:\temp\nismapconflicts.txt \ -t container name -f c:\temp\nismap.log at the command prompt, and then press ENTER.
Check the contents of the c:\temp\nismapconflicts.txt conflicts file and the c:\Temp\Nismaps.log log file.
If you are satisfied with the results, run the actual migration. At the command prompt, type nis2ad -y UNIX NIS domain name -a Active Directory NIS domain name -c c:\temp\nismapconflicts_real.txt -m \ -t container name -f c:\temp\nismap_real.log, and then press ENTER.
To view the full syntax of the Nis2ad utility, type nis2ad -? at a command prompt, and then press ENTER.
NOTE: The following information applies to the migration of existing NIS maps to Server for NIS:
Only a single map at a time can be migrated by using the Nis2ad utility.
Password file entries with a user name that is longer than eight characters are not migrated.
Windows user accounts that are created by the migration are created with a random password. You must change the password to a known value, and then force users to change their password at the next logon.