Share via

Server for NIS Functionality -- Push Service

  • Article

Applies To: Windows Server 2008 R2

Server for NIS synchronizes and propagates NIS map changes to UNIX-based NIS subordinate (also known as slave) servers. The NIS master server supports the following transfer modes:

  • Periodic transfer of NIS maps
  • On-demand transfer of NIS maps to subordinate servers

Typically, NIS maps are transferred to subordinate servers upon change by using the make utility. The Windows-based NIS server does not use make; instead, the server pushes immediately.

Subordinate NIS servers can request transfer of maps at any time. Server for NIS Server Functionality -- Push Service provides information to help you interpret system messages indicating the functional state of the NIS map push service.

Events

Event ID Source Message

4097

Microsoft-Windows-IDMU-ServerForNIS

 Map propagation (yppush) succeeded. Domain: %1, Map Name: %2, Server: %3.

8198

Microsoft-Windows-IDMU-ServerForNIS

 Server for NIS yppush service has stopped.

8241

Microsoft-Windows-IDMU-ServerForNIS

 Failed to create an event: %1.

8242

Microsoft-Windows-IDMU-ServerForNIS

 An error occurred during notification of a registry key change: %1.

8243

Microsoft-Windows-IDMU-ServerForNIS

 An error occurred while creating a waitable timer: %1.

8244

Microsoft-Windows-IDMU-ServerForNIS

 An error occurred while setting a waitable timer: %1.

12288

Microsoft-Windows-IDMU-ServerForNIS

 Warning: yppush failure. Domain: %1, Map Name: %2, Server: %3, Status: %4.

12289

Microsoft-Windows-IDMU-ServerForNIS

 Warning: yppush failure in sending yp_xfr request. Server: %1, Domain: %2, Map Name: %3.

Server for NIS

Identity Management for UNIX