Issues Fixed in this Release
Access Gateway Enterprise
Product: Access Gateway Enterprise Current Product Version: 4.0
Previous Product: MetaFrame Secure Access Manager
Previous Product Version: 2.0 with Service Pack 1
Language: English (EN)
Fixed Issues List: 1.0
The following issues have been fixed since the previous release of this product. For information about new features and system requirements, see the product administration guides.
1. When the Alert Broadcaster CDA queried the database and the connection was null, the agent server trapped.
This fix corrects the issue.
[#68883]
2. Note: This fix is for the Win32 ICA Web Client.
By default, Secure Access Manager overrode the window settings from the server farm, forcing all published resources to open in seamless windows. The published desktop opened on your local workstation in full-screen mode and did not honor the window settings from the server farm.
This fix applies the window settings configured in the server farm to all published server desktops.
[#74473]
3. The Secure Gateway client was attempting to reach the Secure Gateway server through the Internet rather than through the Intranet. The client was not comparing the target address with the exception list and the Secure Gateway was trying to access all target addresses through the proxy server.
The client now compares the address with the exception list and no longer goes through the proxy server.
[#82974]
4. The Program Neighborhood CDA displayed a script error message when it finished loading. The issue occurred because of differences between .NET Framework 1.0 and .NET Framework 1.0 with Service Pack 3, which caused the Resource Aggregation Service to malfunction.
This fix corrects the issue.
[#96235]
5. If you selected "Alternative User Input" and enabled the Speech and Handwriting features during installation of Microsoft Office XP, Internet Explorer did not exit properly if you were using the Secure Gateway client. The issue occurred because the dll detach code in one of the loaded dlls invoked a deadlock.
This fix corrects the issue.
[#101232]
6. After upgrading to Windows Server 2003, some users received an error message stating “The header cannot exceed a 1000 characters.”
This fix corrects the issue.
[#104281]
7. When using a client side proxy server to connect to the Secure Gateway using the Gateway client, the Web page failed to load and displayed the following error message: "Error: The Page cannot be displayed.” The issue occurred because when the client attempted to connect to the proxy server to establish SSL tunneling for Secure Gateway traffic, the client missed a field that is required for any "Http 1.1" request. Therefore, the proxy server returned a failure for this request and the connection could not be established.
[#106329]
8. On devices running Windows XP with Service Pack 2, if the "Automatic prompting for ActiveX controls" security setting was disabled for the current zone, Internet Explorer displayed an information bar below the address bar to indicate an ActiveX component needed to be installed. If you clicked the information bar to install the ActiveX control, the ActiveX control was not installed, and the IFrame was used instead.
This fix corrects the issue.
[#106891]
9. The value for the attribute addresstype of the ServerAddress field of the ResAggSvc.exe.config file could only follow the format of <IP_address:port_number>, for example, <10.70.1.79:1494>. You were not able to use a fully qualified domain name (FQDN) in place of the server IP address, for example, <widgets.us.company.com:1494>. The issue occurred because the “dot-port” attribute value was hard-coded in the code; as a result, ICA files did not support “dns-port” or other attribute values.
This fix adds support for the attribute value “dns-port,” which allows you to use FQDNs for server address types.
Note: To enable this functionality, you must also select the Enable XML Service DNS address resolution option under MetaFrame Settings on the farm properties page of the Presentation Server Console.
[#113472]
10. When the window size was set to "Server default" in the Access Management Console, published applications always launched at 640x480 resolutions, regardless of the resolution values set for the applications on the server. The issue occurred because of a missing test condition in the code.
This fix corrects the issue.
[#116308]
