Consider the following scenario:

  • You enable Microsoft Forefront Threat Management Gateway (TMG) 2010 functionality to specify exact domains for HTTPS inspection, as is documented in update 2619986.

  • You specify a domain name set on which you want Forefront TMG 2010 to apply HTTPS inspection. For example, you specify

  • A user accesses a site that is in the domain name set.

In this scenario, HTTPS traffic may not be inspected.


This problem may occur if the destination site uses a server certificate that has subject alternative names (SANs). If any of the Domain Name System (DNS) names in the SAN list are not in the inclusion domain name set that is specified for HTTPS inspection, HTTPS traffic will not be inspected.


To resolve this problem, install Rollup 5 for Forefront Threat Management Gateway 2010 Service Pack 2.


To work around this problem, make sure that all the DNS names in the SAN list are included in the domain name set that is used for the inclusion domains. You can inspect these names by viewing the server certificate and then inspecting the Subject Alternative Name field.


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


Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!