Bug ID 689826: Proxy/PAC file generated during VPN tunnel is not updated for Windows 10 (unicode languages like: Japanese/Korean/Chinese)

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
APM-Clients APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3

Fixed In:
13.0.1, 12.1.3.2, 11.5.6

Opened: Oct 20, 2017
Severity: 3-Major
Related AskF5 Article:
K95422068

Symptoms

On a Microsoft Windows 10 system configured for a Unicode language (Japanese, Korean, or Chinese, for example) the client proxy autoconfig file is not assigned in the Microsoft Internet Explorer browser after the VPN connection is established.

Impact

Proxy settings are not applied on client side after VPN is established.

Conditions

- Client proxy settings provided in Network Access settings, or client is configured with proxy prior to establishing VPN tunnel. - Windows 10 configured for a unicode-language (Japanese/Korean/Chinese/etc.). - VPN tunnel is established using either a browser or the Edge Client.

Workaround

There are two possible workarounds: Workaround A ============ -- Change the language to English from Control panel :: Region :: Administrative :: Language for non-Unicode programs :: Change System locale. Workaround B ============ -- Add a variable assign agent in the access policy, after the logon item and before the resource is assigned. To do so, follow this procedure: 1. Set the custom variable name to the following value: config.connectivity_resource_network_access./Common/<network_access_resource_name>.client.ConnectionTrayIcon Note: <network access resource name> is the name of the network access resource. 2. Set the value to be of the type 'custom expression' and populate it with the following value (including the quotation marks): return "</ConnectionTrayIcon><connection_name_txt>F5VPN</connection_name_txt><ConnectionTrayIcon>" Note: The <connection_name_txt> tag contains the name of the adapter that the client will create. 3. After making these two changes, apply the access policy. The next time the VPN is established, a new virtual adapter entry will be created with the name provided in <connection_name_txt> tag.

Fix Information

Previously, on a Windows 10 system configured for a Unicode language (for example, Japanese, Korean, or Chinese) the client proxy autoconfig file was not assigned with Internet Explorer after the VPN connection was established. This issue has been fixed.

Behavior Change