About NIS servers

The NIS server provides the capability to act as the primary NIS server for one or more NIS domains for the Windows-based Active Directory domain service (ad ds) domain controller, integrates Windows networks and Network Information Service (NIS) networks. The NIS server stores both standard and non-standard NIS ing data in ad ds. Standard ing consists of aliases, bootparams, ethers, hosts, group, netgroup, netid, netmasks, networks, passwd, protocols, rpc, services, pservers, and shadow; all other mappings are non-standard mappings .)

Therefore, the NIS Server creates a namespace for the Windows domain and the NIS domain, which can be managed by the Windows Administrator using a set of tools. Administrators can easily create, modify, and delete user accounts for both Windows and UNIX domains. Users with accounts in both Windows and UNIX environments can use ad ds to manage all the attributes required by their respective domains and namespaces.

Master server and slave server running NIS Server
The NIS server can also be installed on other domain controllers in the same domain as the primary NIS server, so that these domain controllers can act as NIS slave servers. In this case, the NIS data in ad ds is automatically copied between Windows Domain Controllers Running the "NIS server. UNIX-based computers can continue to act as slave servers in the NIS domain, because the NIS server uses yppush to disseminate changes to NIS data to UNIX-based NIS servers, just like a UNIX-based master NIS server.

Migration Process

After the NIS server is installed, the first task is to migrate the NIS ing from the UNIX-based NIS server to the computer running the NIS server. You can use the Windows-based migration wizard that comes with the NIS server, or use the command line utility to complete this task. After the NIS ing is migrated, the NIS server can act as the master server of the NIS domain. You can migrate multiple NIS domains to the same Windows-based Active Directory domain controller. The domain can be merged or exists independently. You can migrate an NIS ing at a time to migrate the NIS ing data in stages.

The NIS Server supports multiple NIS domains at the same time. Ing of multiple domains can reside in ad ds at the same time. Requests from clients or other servers in the domain receive data from mappings in the same domain.

NIS Server Management
You can use Windows-based UNIX identification management to manage the NIS server. You can use a Windows-based tool such as "Active Directory users and computers" to manage the passwd, group, and hosts mappings that have been migrated to ad ds. You can also use the command line tool nismap and nisadmin to manage all standard and non-standard mappings and NIS servers. You can use Windows administrative tools to monitor NIS servers, including using event viewer to review important events and errors recorded by NIS servers.

In addition to the management tools provided by Windows, you can also use the Active Directory Service Interface (ADSI) or Lightweight Directory Access Protocol (LDAP) to create other management tools.

The NIS server implements the required NIS remote process call to process requests from UNIX-based NIS clients, Windows-based NIS clients, and other subordinate NIS servers. The NIS Server supports broadcast and normal binding modes.