Symptoms
Consider the following scenario:
-
You deploy a Microsoft Exchange Server 2010 Edge Transport server and subscribe it to an Exchange Server 2010 Hub Transport server.
-
You change the SmtpMaxMessagesPerConnection property of a send connector on the Exchange Server 2010 Hub Transport server.
-
You perform EdgeSync synchronization.
In this scenario, the SmtpMaxMessagesPerConnection property is still set to the old or default value on the subscribed Edge Transport server. Additionally, the message delivery process might be delayed.
Cause
This issue occurs because the attributes list of a send connector for synchronization does not include the SmtpMaxMessagesPerConnection property.
When the attributes list does not include the SmtpMaxMessagesPerConnection property, the Microsoft Exchange EdgeSync service does not replicate the property from Active Directory Domain Services (AD DS) to Active Directory Lightweight Directory Services (AD LDS).
Note The Exchange EdgeSync service is running on the on the Hub Transport server.
Resolution
To resolve this issue, install the following update rollup package:
2608646 Description of Update Rollup 6 for Exchange Server 2010 Service Pack 1
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about Edge Subscriptions, visit the following Microsoft website:
General information about Edge SubscriptionsFor more information about the Set-SendConnector cmdlet, visit the following Microsoft website:
General information about the Set-SendConnector cmdletFor more information about the Get-SendConnector cmdlet, visit the following Microsoft website:
General information about the Get-SendConnector cmdletFor more information about the SmtpSendConnectorConfig.SmtpMaxMessagesPerConnection property, visit the following Microsoft website:
General information about the SmtpSendConnectorConfig.SmtpMaxMessagesPerConnection property
