ISA Server Configuration Changes Are Not Instantaneous

When you make changes to Internet Security and Acceleration (ISA) Server 2000, there is a delay before these changes take effect. This article describes the two registry keys that you can modify to control this behavior.

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.

When you apply the Deny Anyone or Deny Any Destination rule, this can take about fifteen seconds before it the rule is applied on a stand-alone server; on an array it can take up to one minute. ISA administrative services aggregates changes before it writes them to storage. You can control this behavior through the following two registry values: ISA Server notifies its services of changes to objects in storage only after no more changes are being made to the specific object for a length of time that is specified by the NotifyAfterIdlePeriod registry entry. You can configure this entry, which is initially set to five seconds (5000 milliseconds), in the following registry key: The NotifyIfNotIdlePeriod registry entry determines when ISA Server should notify its services, even if modifications are still being made to the object. You can configure this entry, which is initially set to 60 seconds (60,000 milliseconds), in the following registry key: