Description of Update 5 for Intelligent Application Gateway 2007 Service Pack 1

A new update is available for Microsoft Intelligent Application Gateway (IAG) 2007 (version 3.7) Service Pack 1 (SP1).

Fixes and improvements that are included in this update

Fix for download parsing behavior

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: IAG 2007 SP1 Update 4 introduced a new registry entry that was named MaxBodyBufferSize. This registry entry let IAG administrators control the maximum size of downloadable files. After you apply IAG 2007 SP1 Update 4, IAG accumulates and tries to parse all data. Therefore, any file that is larger than the defined maximum size is blocked, regardless of the file types.

After you apply IAG 2007 SP1 Update 5, IAG no longer accumulates and parses data by default. Instead, handling and parsing behavior is based on the settings of the parsing options that are defined on the IAG Configuration console, as follows:

• The Don't parse the bodies of the response to these requests list:
  If the requested URL matches any URL on this list, the response body will not be accumulated for parsing.
• The Search and Replace Response Content list:
  If the requested URL matches any URL on this list, and the requested URL does not match the parameters of the previous rule, the response body will be accumulated for parsing.
• The Search and Replace on Content-Type list:
  If the requested URL does not match the parameters of either of the two previous rules, and the content type matches any content type on this list, the response body will be accumulated for parsing.

Note Assume that for Basic trunks and for Webmail trunks, an IAG administrator wants to revert to the previous parsing or accumulation method. In this case, the IAG administrator must create a new registry entry that is named BasicTrunkAccumulateResData, and the administrator must set the entry's DWORD value to 1. The BasicTrunkAccumulateResData registry entry should be created under the following registry subkey:

New Client Detection API to retrieve data from selected Windows Management Instrumentation (WMI) objects

Update 5 introduces two new client detection APIs that enable the creation of advanced endpoint detection scripts. After you apply this update, administrators can create custom detection scripts to retrieve information about the Windows updates that are applied on a client computer. Because this data can be compared with a list of required updates, it can be used in a detection policy.

Administrators can also create custom detection scripts that retrieve additional client computer information. The types of information that can be retrieved include the following:

• Computer Name
• Computer SID
• Domain Name
• Domain Membership Status
• Workgroup Name

These APIs are implemented by querying WMI on the client computers.

Network Connector can support a larger number of additional networks

Before IAG 2007 SP1 Update 5, Network Connector supported only 7 additional networks. After you apply this update, administrators can define up to 200 additional networks.

Minor fix in the Local Drive Mapping application

Update 5 fixes a bug in the Local Drive Mapping application that occurs when a user's name contains a space character.

Note This fix is intended only for client computers that are running Windows XP or Windows Server 2003. Drive mapping is not supported on Windows Vista-based client computers.

User warning on 64-bit operating system

IAG Client Components are not supported on 64-bit operating systems. If a user connects to an IAG site by using Windows Internet Explorer on a 64-bit operating system after this update is applied, he or she will receive the following warning message on the logon page:

Update information

A supported update is now available from Microsoft. However, it is intended to correct only the problems that this article describes. Apply it only to systems that are experiencing these specific problems.

Contact Microsoft Customer Support Services to obtain the update. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this update, you must have IAG 2007 SP1 (version 3.7.1) installed on the appliance in question.

Restart requirement

You do not have to restart the appliance after you apply this update.

Update replacement information

This update is cumulative. It replaces the following updates that were released for IAG 2007:

• Update 1 for IAG 2007 SP1
• Update 2 for IAG 2007 SP1
• Update 3 for IAG 2007 SP1
• Update 4 for IAG 2007 SP1

Known issues in this update

If the administrator has added more than seven additional networks to Network Connector and then uninstalled IAG 2007 SP1 Update 5, the following error message will be displayed:This issue occurs because the feature that supports more than seven additional networks is also uninstalled.

Known issues in previous updates

• When you use the Sametime plug-in, you may be unable to attend a meeting on the first attempt.
• The Detection Center feature cannot detect Windows Firewall by using WMI detection. Therefore, the existing detection mechanism is used to detect whether Windows Firewall is running and enabled on the client computers.
• You cannot use IP addresses to define a public host name for a trunk. Instead, you must use only host names. On the Trunk Configuration console, the trunk's Public Hostname/IP Address box is replaced by a Public Hostname box. Additionally, host names must be formatted as FQDN, and they must contain at least two periods. For example, host names must reflect the following format:
  iag.contoso.com
• In some cases, the administrator must change the default body size that is defined in the request smuggling protection definitions of e-Gap Appliance or of IAG. For example, for some Web parts on a Windows SharePoint site, the request size is larger than the default size in e-Gap or in IAG. In this situation, you receive the following message in the Web Monitor:
  HTTP Request Smuggling (HRS) attempt detected.
• This update does not support the offline installation of the client components. If an administrator wants to run an offline installation, the IAG 2007 SP1 offline client components must be installed first. Then, the client components will be automatically upgraded the first time that a user accesses an IAG appliance that runs the new update.

For more information about previous updates that were released for e-Gap Appliance 3.6 and for IAG 2007, click the following article numbers to view the articles in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: