Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: The Exchange Edge default Receive connector is disabled unexpectedly when the "Email policy integration" feature is not configured in Forefront Threat Management Gateway 2010

FIX: The Exchange Edge default Receive connector is disabled unexpectedly when the "Email policy integration" feature is not configured in Forefront Threat Management Gateway 2010

View products that this article applies to.

Symptoms

Consider the following scenario. You install the following on the same server:
  • Microsoft Forefront Threat Management Gateway (TMG) 2010
  • Microsoft Exchange Server 2010 Edge Transport Server role
  • Microsoft Forefront Protection 2010 for Exchange Server (FPE).

You do not want to use the Email policy integration feature in TMG. When you do not use this feature, TMG does not manage the Exchange Edge and FPE settings. Therefore, you do not execute the Configure Email Policy Wizard in the TMG Management console.

In this scenario, you notice that the default Receive Connector for Exchange Edge is automatically disabled.

Even though you enable the connector again from the Exchange Management console or by using a Windows PowerShell cmdlet, you notice that the connector is automatically disabled again one minute later.

↑ Back to the top

Cause

This problem occurs because the IntegrationEnabled property of the SmtpProtectionConfiguration COM object is set incorrectly to True during TMG setup. When the SMTP Protection feature is not configured, TMG tracks the Exchange configuration and disables all receive connectors.

↑ Back to the top

Resolution

To resolve this problem, install the service pack that is described in the following Microsoft Knowledge Base article:
2555840  Microsoft Forefront Threat Management Gateway 2010 Service Pack 2

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Workaround

To work around this problem if you do not want to use the Email policy integration mode, or you cannot install TMG Service Pack 2, set the Email Policy Integration mode to Disabled. To do this, follow these steps:
  1. Start the TMG Management console, and then click Troubleshooting.
  2. Set the Control Email Policy configuration integration task to Disabled, and then click Apply.
Note This procedure sets the IntegrationEnabled property for the COM object to False.

↑ Back to the top

More Information

When Exchange Edge and FPE are running on the TMG server, we recommend that you enable the Email Policy integration mode so that TMG manages the Exchange Edge and FPE configuration. When TMG performs this management, Exchange and FPE settings are exposed in the TMG Management console. By default, when you use this integration feature, you do not experience this problem because TMG automatically manages the SMTP connectors that are defined in Exchange Edge.

↑ Back to the top

References

For more information about the IntegrationEnabled property, visit the following Microsoft Developer Network (MSDN) website:
IFPCSmtpProtectionConfiguration::IntegrationEnabled Property
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbfix, kbbug, kbexpertiseinter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2591729
Revision : 1
Created on : 1/7/2017
Published on : 10/31/2011
Exists online : False
Views : 360