Understanding about NIS data migration

The NIS server can migrate the Network Information Service (NIS) ing data to Active Directory domain service (ad ds ).

After the migration, when the NIS request from the client or other servers is received, the NIS Server searches for ad ds to reply to the NIS query.

Migration consists of the following three steps:

Migrate the NIS ing to a Windows-based server.

Use command line

UNIX Identity Management contains a command line tool called nis2ad, which is used to migrate the NIS ing from the UNIX-based NIS server to the ad ds-based NIS server.

Use migration wizard

The NIS data migration wizard in UNIX identity management extracts the information required for migration. However, even when using the migration wizard, you must complete steps 2 and 3 as described below.

The migration wizard and the nis2ad command read the ing data from the NIS ing source file from the plain text file of its compiled NIS ing database. The location of these source files must allow access by the domain controller during migration, such as the shared directory accessible by the disk or domain controller on the domain controller.

To the existing slave NIS server, also known as the secondary NIS Server) to notify the new master NIS server.

After the migration, the original UNIX-based NIS server must send the ing update to all the subordinate NIS servers whose ing contains the new master server name.

Disable the old NIS server.

UNIX-based subordinate NIS servers can continue to work as before; however, they will receive ing updates from Windows-based computers instead of UNIX-based ones. The client computer continues to obtain the NIS ing or data from the new master server.