Skip to main content

Exchange Development Kit (EDK) connector 'Text Messaging Delivery Agent Connector' was found in the organization. Exchange Server 2010 does not support EDK connectors. This connector will need to remain on existing Exchange 2003 servers.

When running Microsoft Exchange Pre-Deployment Analyzer before installing Exchange 2010 into environment with Exchange 2007 installed, an informational error is shown saying that some legacy connector, you probably never heard of, exists. In my case the environment was Exchange 2007 and the connector was found in Exchange Administrative group (FYDIBOHF23SPDLT) using following steps:
  1. Connect to your DC
  2. In the Active Directory Sites and Services Microsoft Management Console (MMC), double-click Active Directory Sites and Services.
  3. Click on top level in the hierarchy tree aka Active Directory Sites and Services (
  4. On the View menu, click Show Services Node.
  5. Double-click Services, double-click Microsoft Exchange, and then double-click the Exchange Organization name.
  6. Double-click Administrative Groups, and then double-click the administrative group - OLD one (Exchange 5.5 or 2003) OR Exchange Administrative group (FYDIBOHF23SPDLT) – This connector can be found in different groups according to the information on the Internet.
  7. Double-click Routing Groups, and then double-click the routing group. For example, double-click Exchange Routing Group (DWBGZMFD01QNBJR).
  8. Double-click Connections.
    On the right side of the MMC, you can see the Text Messaging Delivery Agent Connector.
  9. Delete the unnecessary connector

Popular posts from this blog

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 

Ports that need to be open on Firewall for Edge Transport servers

Ports that need to be open on firewall for Edge Server subscription with Hub Server to function properly: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server) Since Edge server needs to communicate with Hub server it is important that it can resolve Hub transport servers by FQDN and Hub transport servers must be able to resolve Edge servers by its FQDNs. To accomplish this you need to either open 53 (DNS) port and configure internal network adapter to use internal DNS but as a security precaution I would suggest to enter DNS records for Edge servers on local DNS manually and to fill hosts file on Edge servers with FQDNs for Hub transport servers.