Microsoft KB Archive/313645

= How to Reduce Instances of Push with Propagation =

PSS ID Number: 313645

Article Last Modified on 4/28/2003

-

The information in this article applies to:


 * Microsoft Windows 2000 Advanced Server

-



This article was previously published under Q313645



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
This article describes how to reduce the incidences of &quot;Push with Propagation&quot; that may occur on a WINS server in a PUSH/PULL relationship.



MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. By default, a WINS server sends Push notifications to its replication partners when changes are received from one or more of the replication partners, or when the number of changes in the version numbers of locally-owned records reach the UpdateCount threshold for that partner.

A WINS server propagates changes that are received through a Push notification from its Pull partners by sending push notifications to its Push partners. This means that a WINS server with many Pull partners may send frequent push notifications. This behavior is named &quot;Push with Propagation.&quot;

Because of this, WINS replication with a Push partner may occur more frequently than you expect. Setting a high UpdateCount for a Push partner does not prevent Push notifications from being sent. If you want to use this value to control replication with a partner, you may find that replication occurs more frequently than you expect. You can turn off push with propagation by setting the following registry value:

Registry key:  

Value name:  

Data type: REG_DWORD

Possible values: 0 or 1

Default value: 1

Description: Determines if the Windows Internet Name Service (WINS) server propagates push notices it receives from push partners to its pull partners.

Value descriptions:

0: Push notices are not sent to pull partners.

1: Push notices are sent to pull partners. This parameter is a global setting effecting all configured Push partners, it is not a per partner setting.

Note In a hub and spoke WINS topology, disabling propagation on the hub server causes it to send push notifications only when the number of changes to the records that it owns reaches the threshold that is set for each push partner. In this example, a hub server with very few clients would not send push notifications very frequently. The number of changes is governed by the number of registrations on that server. If the push counter for a specific replication partner is very high (10,000 or more), changes are rarely pushed to that partner. Replication will be governed by the pull settings on the remote server. However, this configuration also affects the hub server's other replication partners. Their push counters on the hub server must be set very low for them to receive push notifications. Turning off push with propagation may affect the whole of your WINS replication topology. Changing the setting affects the server's replication with all its partners.

Keywords: kbinfo KB313645

Technology: kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000Search kbWinAdvServSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.