Главная > ForeFront Threat Management Gateway > Проблемы, которые решает установка SP2 для Microsoft Forefront Threat Management Gateway 2010

Проблемы, которые решает установка SP2 для Microsoft Forefront Threat Management Gateway 2010


TMG2010

Как я уже отметил в моем предыдущем посте установка второго пакета обновления для Microsoft Forefront Threat Management Gateway 2010 не только вносит новшества, но исправляет ряд ошибок, которые создают проблемы в работе этого продукта. В этом посте я привожу без перевода полный перечень ошибок, которые исправляет установка SP2 для Microsoft Forefront Threat Management Gateway 2010:

Номер статьи (KB Number)

Пояснение

2529292

FIX: The default local IP address is used to access an FTP site when you use Forefront Threat Management Gateway 2010 as a proxy server

2557116

FIX: «Check for relevant alerts» message for servers that are listed in the «Servers with incomplete report data» field of the «User activities» report, and no alerts are found in Forefront Threat Management Gateway 2010

2558387

FIX: Firewall service crashes after you configure a web access rule to use a custom schedule on a server that is running Forefront Threat Management Gateway 2010

2562550

FIX: The TMGEMS role is not detected when you run the Security Configuration Wizard on a server that is running Forefront Threat Management Gateway 2010

2578466

FIX: Threat Management Gateway 2010 may crash with Stop error «DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)»

2579940

FIX: «You could not be logged on to Forefront TMG» error message when you try to log on to a published website after a domain name is not provided in the authentication settings for LDAP servers in the New Web Publishing Rule Wizard

2589739

FIX: Report logs and historical logs are not correctly created on non-English Threat Management Gateway 2010 installations after you install Threat Management Gateway 2010 Service Pack 1 Update 1

2591269

FIX: Network Load Balancing hook rules are not created correctly when the name on the To tab of the Web Publishing rule does not resolve to a published web server in Forefront Threat Management Gateway 2010

2591272

FIX: «0x80040e4d» error when Forefront TMG 2010 is configured to generate the daily summary data overnight on a computer that has SP1 preinstalled

2591274

FIX: The connection owner for a VPN site-to-site connection is lost when you join an EMS by using an imported configuration in Forefront Threat Management Gateway 2010 Service Pack 1

2591275

FIX: «Access to the file is blocked» error message when the ScanStorage folder on a Forefront Threat Management Gateway 2010 client exceeds the maximum storage limit

2591278

FIX: The SIP filter in Forefront Threat Management Gateway 2010 may prevent an internal client from hanging up a call

2591279

FIX: You may be redirected to the password change page when your password has not expired or is not near expiration when you use Forms Based Authentication in Forefront Threat Management Gateway 2010

2591719

FIX: «0x80070057 (The parameter is incorrect)» error message is logged, and the Forefront TMG Managed Control service cannot start, when you enable and configure the «Email Policy» feature for Forefront Threat Management Gateway 2010

2591729

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

2591744

FIX: The Email Policy Integration feature that redirects spam email messages to a quarantine mailbox address does not work when Forefront Protection for Exchange 2010 is installed on Forefront Threat Management Gateway 2010

2591803

FIX: Forefront Threat Management Gateway 2010 prematurely closes the connection to the web server when a web proxy client uploads data by using an SSL tunnel

2591837

FIX: Stop error on a server that is running Forefront Threat Management Gateway 2010: «IRQL_NOT_LESS_OR_EQUAL (a)»

2592447

FIX: Threat Management Gateway 2010 Enterprise edition may be displayed as the Standard edition

2592454 FIX: «HRESULT=80040E57 DB_E_DATAOVERFLOW» error message when you try to run a report after you install hotfix 980311 on a server that is running Forefront Threat Management Gateway 2010
2592455

FIX: Client computers cannot access an L2TP server or an IPSec endpoint through a Threat Management Gateway 2010 server array that uses network load balancing

2592456

FIX: The Google Chrome web browser times out when it tries to use an SSL connection to access a published web server in a TMG 2010 environment

2592929

FIX: You cannot track the source of failed logon attempts that are made through Threat Management Gateway 2010

2592933

FIX: Support for Threat Management Gateway 2010 Forms-based authentication cookie sharing across array members

2592957

FIX: Client traffic is blocked as «spoofed» for an IP address where the end octet is .255 in a Forefront Threat Management Gateway 2010 environment

2593376

FIX: A VPN client cannot perform name resolution queries immediately after the client connects to a server that is running Forefront Threat Management Gateway 2010

2595975

FIX: A Threat Management Gateway 2010 Forms-based authentication password change may fail because of multiple favicon.ico requests from the client browser

2595999

FIX: «0x80070002» error in Forefront Threat Management Gateway 2010 when an array join operation fails because the Built-in\Administrators group is removed from TMG Enterprise Administrators role

2596034

FIX: A SIP client cannot register with an external SIP server when you access the server through Forefront Threat Management Gateway 2010

2596065

FIX: Outgoing connections from SecureNAT clients may intermittently fail because of how Forefront Threat Management Gateway 2010 manages NAT source port pools

2596388

FIX: SecureNAT clients receive a «404 Page Cannot Be Found» error page when the clients try to access the Internet through a Threat Management Gateway 2010 server

2596444

FIX: POST requests to a web server that is running Forefront Threat Management Gateway 2010 may fail

2599064

FIX: Threat Management Gateway 2010: A Windows Server 2008 R2-based computer stops responding at startup, or no Automatic services start after the computer restarts

2599065

FIX: You cannot discard the changes after you provide the product key and then click OK when you upgrade to Enterprise edition of Forefront Threat Management Gateway 2010

2599066

FIX: Stop error on a server that is running Forefront Threat Management Gateway 2010: «DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)»

2599067

FIX: The Forefront Threat Management Gateway 2010 management tools such as the TMG Management console do not function after you install Internet Explorer 9

2606839

FIX: You may be unable to select the correct category item in the «Filter by category» list in the Japanese version of Forefront Threat Management Gateway 2010

2608155

FIX: The value of the «Bytes received» logging field is incorrect when a request is denied by the HTTP Filter

2619986

FIX: You cannot specify exact domains for HTTPS inspection in Threat Management Gateway 2010

2619987

Update adds feature to lock out service accounts that use FBA with Active Directory or with LDAP authentication in a Forefront Threat Management Gateway 2010 environment

2619989

FIX: Microsoft Forefront Threat Management Gateway 2010 does not support HTTPS caching for outgoing traffic

2619990

FIX: The server start time may take 20 minutes or more when you have a complex policy that contains many publishing rules on a server that is running Forefront Threat Management Gateway 2010

2619991

FIX: An application that uses port 443 to connect to a remote web server no longer works after HTTPSi is enabled in a Forefront Threat Management Gateway 2010 environment

2619992

FIX: The email policy configuration is reapplied when you configure email policy settings in Forefront Protection for Exchange that are not configured in a Forefront Threat Management Gateway 2010 environment

Детальную информацию о каждой проблеме и ошибке можно просмотреть щелкнув на номер статьи.

  1. 19.10.2011 в 20:46

    Спасибо. Хоть кто-то расписал более чем «стало ощутимо круче».

  1. No trackbacks yet.

Добавить комментарий

Please log in using one of these methods to post your comment:

Логотип WordPress.com

Для комментария используется ваша учётная запись WordPress.com. Выход / Изменить )

Фотография Twitter

Для комментария используется ваша учётная запись Twitter. Выход / Изменить )

Фотография Facebook

Для комментария используется ваша учётная запись Facebook. Выход / Изменить )

Google+ photo

Для комментария используется ваша учётная запись Google+. Выход / Изменить )

Connecting to %s

%d такие блоггеры, как: