Routing Engine: CheckConnectorRestrictions parameter is non-default
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine whether Simple Mail Transfer Protocol (SMTP) connector routing logic has been modified from its default setting:
If the Exchange Server Analyzer finds that the CheckConnectorRestrictions registry key is present and configured with a value greater than 0, a non-default configuration message is displayed.
The CheckConnectorRestrictions registry entry is a custom configuration setting for Exchange Server that enables restriction checking on the Exchange bridgehead server that is the source for the connector that is being checked. By default, connector restriction checking is turned off because it can significantly affect performance, notably in configurations that use many distribution groups. Restrictions will be checked for each message sent to each member of each distribution group that passes through the system. If restrictions are specified but this registry entry does not exist, restriction checking will not be performed.
|This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.|
Open a registry editor, such as Regedit.exe or Regedt32.exe.
Navigate to: HKLM\System\CurrentControlSet\Services\RESvc\Parameters
Delete the CheckConnectorRestrictions registry key.
Close the registry editor.
Restart the IIS Admin Service.
On the connector's Delivery Restrictions tab, re-enable the restriction option.
Before you edit the registry, and for information about how to edit the registry, see Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).
For more information about the CheckConnectorRestrictions registry value, see Knowledge Base article 277872, "XCON: Connector Delivery Restrictions May Not Work Correctly" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=277872).