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. Rollup 5 for Forefront Threat Management Gateway 2010 Service Pack 2

Rollup 5 for Forefront Threat Management Gateway 2010 Service Pack 2

View products that this article applies to.

Summary

This article discusses Rollup 5 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2 (SP2). This article also lists the Microsoft Knowledge Base articles that discuss the issues that are fixed in this update rollup.

Issues that are fixed in this rollup package

The issues that are fixed in this update rollup package are listed in the following Microsoft Knowledge Base articles. To review the issues, click the article numbers to go to the articles.

ArticleTitle
2963805 FIX: Account lockout alerts are not logged after you install Rollup 4 for TMG 2010 SP2
2963811 FIX: The TMG Firewall service (wspsrv.exe) may crash when the DiffServ filter is enabled
2963823 FIX: "1413 Invalid Index" after you enable cookie sharing across array members
2963834 FIX: HTTPS traffic may not be inspected when a user accesses a site
2967726 FIX: New connections are not accepted on a specific web proxy or web listener in Threat Management Gateway 2010
2965004 FIX: EnableSharedCookie option doesn't work if the Forefront TMG service runs under a specific account
2932469 FIX: An incorrect value is used for IPsec Main Mode key lifetime in Threat Management Gateway 2010
2966284 FIX: A zero value is always returned when an average counter of the "Forefront TMG Web Proxy" object is queried from the .NET Framework
2967763 FIX: The "Const SE_VPS_VALUE = 2" setting does not work for users if the UPN is not associated with a real domain
2973749 FIX: HTTP Connectivity verifiers return unexpected failures in TMG 2010
2700248 FIX: Server that's running Forefront Threat Management Gateway 2010 stops accepting all new connections and becomes unresponsive

Note Although this issue was initially fixed in Rollup 3 for Forefront Threat Management Gateway (TMG) 2010 SP2, we have identified additional conditions that may trigger it.

↑ Back to the top

More Information

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing these specific problems.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this update, you must have Service Pack 2 for Microsoft Forefront Threat Management Gateway (TMG) 2010 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTimePlatform
Authdflt.dll7.0.9193.644252,76816-Jun-201421:55x64
Comphp.dll7.0.9193.644257,91216-Jun-201421:54x64
Complp.dll7.0.9193.644108,03216-Jun-201421:55x64
Cookieauthfilter.dll7.0.9193.644682,76016-Jun-201421:55x64
Dailysum.exe7.0.9193.644186,28816-Jun-201421:55x64
Diffserv.dll7.0.9193.644162,61616-Jun-201421:55x64
Diffservadmin.dll7.0.9193.644310,40016-Jun-201421:55x64
Empfilter.dll7.0.9193.644711,08816-Jun-201421:55x64
Empscan.dll7.0.9193.644267,66416-Jun-201421:55x64
Fpcsqmconfig.com.xmlNot Applicable137,10313-Feb-201214:24Not applicable
Fweng.sys7.0.9193.572845,44012-Dec-201215:31x64
Fwengnotify.dll7.0.9193.572154,28012-Dec-201215:31x64
Gwpafltr.dll7.0.9193.644191,45616-Jun-201421:55x64
Httpadmin.dll7.0.9193.644242,94416-Jun-201421:55x64
Httpfilter.dll7.0.9193.644251,20816-Jun-201421:55x64
Isarepgen.exe7.0.9193.64479,70416-Jun-201421:55x64
Ldapfilter.dll7.0.9193.644189,89616-Jun-201421:55x64
Linktranslation.dll7.0.9193.644418,59216-Jun-201421:55x64
Managedapi.dll7.0.9193.64480,75216-Jun-201421:55x64
Microsoft.isa.reportingservices.dll7.0.9193.644876,32816-Jun-201421:55x64
Microsoft.isa.rpc.managedrpcserver.dll7.0.9193.644172,44016-Jun-201421:55x64
Microsoft.isa.rpc.rwsapi.dll7.0.9193.644136,92016-Jun-201421:55x64
Mpclient.dll7.0.9193.644128,63216-Jun-201421:55x64
Msfpc.dll7.0.9193.6441,079,30416-Jun-201421:55x64
Msfpccom.dll7.0.9193.64413,446,02416-Jun-201421:55x64
Msfpcmix.dll7.0.9193.644569,44816-Jun-201421:55x64
Msfpcsec.dll7.0.9193.644386,65616-Jun-201421:55x64
Msfpcsnp.dll7.0.9193.64417,112,84816-Jun-201421:55x64
Mspadmin.exe7.0.9193.6441,121,55216-Jun-201421:55x64
Mspapi.dll7.0.9193.644130,68016-Jun-201421:55x64
Msphlpr.dll7.0.9193.6441,279,13616-Jun-201421:55x64
Mspmon.dll7.0.9193.644150,23216-Jun-201421:55x64
Mspsec.dll7.0.9193.64484,87216-Jun-201421:55x64
Preapi.dll7.0.9193.64421,53616-Jun-201421:55x64
Radiusauth.dll7.0.9193.644138,40816-Jun-201421:55x64
Ratlib.dll7.0.9193.644148,18416-Jun-201421:55x64
Reportadapter.dll7.0.9193.644723,88816-Jun-201421:55x86
Reportdatacollector.dll7.0.9193.6441,127,64816-Jun-201421:55x86
Softblockfltr.dll7.0.9193.644143,55216-Jun-201421:55x64
Updateagent.exe7.0.9193.644211,52016-Jun-201421:55x64
W3filter.dll7.0.9193.6441,409,41616-Jun-201421:55x64
W3papi.dll7.0.9193.64421,02416-Jun-201421:55x64
W3pinet.dll7.0.9193.64435,43216-Jun-201421:55x64
W3prefch.exe7.0.9193.644341,31216-Jun-201421:55x64
Webobjectsfltr.dll7.0.9193.644170,32016-Jun-201421:55x64
Wploadbalancer.dll7.0.9193.644203,84016-Jun-201421:55x64
Wspapi.dll7.0.9193.64449,84016-Jun-201421:55x64
Wspperf.dll7.0.9193.644131,19216-Jun-201421:55x64
Wspsrv.exe7.0.9193.6442,464,13616-Jun-201421:55x64

↑ Back to the top

Status

Microsoft has confirmed that these are issues in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

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

↑ Back to the top

Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug, kb

↑ Back to the top

Article Info
Article ID : 2954173
Revision : 1
Created on : 1/7/2017
Published on : 7/8/2014
Exists online : False
Views : 479