When it gets to the step of installing additional software, however, things go wrong:
Microsoft SQL Express 2008 (logging instance) could not be installed. As a result, Forefront TMG installation cannot be completed.
To be not entirely correct solution:
Browse to the FPC folder on media. Run MS_FPC_Server.msi.
Once you’ve got TMG installed, open it up, and select the Logs & Reports list item.
Change your selection from the embedded SQL database to a local file destination, or a standalone SQL instance if you’re into that sort of thing.
||FIX: A client may be unsuccessful in accessing a Java SSO application published to the web in a Threat Management Gateway 2010 environment
||FIX: You receive an “Error: Subreport could not be shown” error message in the User Activity or Site Activity report in a Forefront Threat Management Gateway 2010 environment
||FIX: UDP packets may become backlogged when you increase the “Maximum concurrent UDP sessions per IP address” setting in a Forefront Threat Management Gateway 2010 environment
||FIX: Threat Management Gateway 2010 administrators may be unable to generate reports
||FIX: Both sides of a TCP connection are closed when the client or remote application half-closes the TCP connection in a Forefront Threat Management Gateway 2010 environment
||FIX: Summary information for the Top Overridden URLs table and for the Top Rule Override Users table display incorrect information in a Forefront Threat Management Gateway 2010 environment
||Forefront TMG 2010 enables L2TP site-to-site connections in RRAS
||FIX: Japanese characters in the subject line of an Alert email message are not readable in the Japanese version of Forefront Threat Management Gateway 2010
||FIX: “The Web Listener is not configured to use SSL” warning message may occur when you configure a Web Listener to use a valid SSL certificate in a Forefront Threat Management Gateway 2010 environment
||FIX: You receive a “Bad Request” error message when you try to access Outlook Web App in a Forefront Threat Management Gateway 2010 environment
||FIX: String comparison may become case-sensitive when you publish a website by using Forefront Threat Management Gateway 2010
||FIX: The Forefront Threat Management Gateway Firewall service (Wspsrv.exe) may crash frequently for a published website secured by SSL after you install Service Pack 2
The most common cause for this error while accessing all HTTPS web sites is because the client workstation doesn’t trust the certificate that TMG is using. The CA certificate (e.g. self signed certificate) used by TMG must be deployed on the client, otherwise the client won’t trust the certificate issued by TMG on behalf of the web server. Read Deploying the HTTPS inspection trusted root CA certificate to client computers from TMG Documentation on TechNet for more information on how to deploy the CA certificate to the clients.
Microsoft® Forefront Threat Management Gateway (TMG) 2010 Service Pack 2 (SP2) introduces new functionality to Forefront TMG 2010 Standard and Enterprise Editions.
The service pack includes the following new functionality and feature improvements:
• The new Site Activity report displays a report showing the data transfer between users and specific websites for any user.
• A new look and feel has been created for error pages.
• Error pages can be more easily customized and can include embedded objects.
• You can now use Kerberos authentication when you deploy an array using network load balancing (NLB).