Previously, in some instances, the Edge Client on Windows would crash when the user signed out of Windows. Previously the incorrect language text was displayed in the main window of the Edge Client for macOS when the Disconnected button was clicked.
F5 EDGE CLIENT WINDOWS 10 DESKTOP VERSION UPGRADE
Previously, after the client upgrade from 13.0.0 to a later version, all users running FireFox or Chrome browsers on Windows were asked to re-install the Endpoint Inspector Application. Previously a user with Firefox 54 or 55 on Fedora 24 or 25 could not establish a session to APM if endpoint checks were configured. Now, the Machine Certificate is used even when UAC is disabled.
Previously, on Windows, the Machine Certificate service was not used when UAC was disabled. Previously, the F5 VPN and F5 EPI apps would quit on Linux distributions with Qt version 5.10.1 or higher. Previously, a Network Access connection could not be established on Windows 10 RS4. Now, Edge Client can now successfully establish a VPN connection after SAML authentication. Previously, Edge Client on Windows was unable to establish a VPN connection after SAML authentication. Because earlier versions of F5 VPN or F5 EPI do not work properly with Chrome 64+ browser, you must launch applications out-of-band (by standalone installer), or by launching F5 VPN/F5 EPI from another browser (such as Firefox or Edge).
F5 EDGE CLIENT WINDOWS 10 DESKTOP VERSION FULL
Now, the Machine Cert check checks the full strings.į5 VPN and F5 EPI now properly consume data processed by Chrome 64+. On MacOS, the Machine Cert check previously checked only the beginnings of the client hostname and cert SAN. To disable the default Microsoft Credentials Provider see. One duplicate comes from the Microsoft Credentials Provider. As a side effect of the fix, the Logon screen now shows duplicates of the pre-logon VPN Entries, which might be confusing for users. Previously, the Windows Logon Integration feature sometimes caused the Windows Logon screen to freeze. The tunnel adapter is now closed on VPN termination, even when Application launch is configured. Previously, in some cases the VPN tunnel adapter created by the VPN client stayed up even when the tunnel was disconnected. Now, configured applications launch with user privileges.
Previously, on Linux, configured applications launched with root permissions when the VPN connection was established. Also, this mode works even when the user is not logged onto the machine.Ĭonnection Startup Time: Initial loading and connection time for Edge Client connections with limited bandwidth has been significantly improved, by reducing the number of pre-connection resource requests (691777). Now a running instance of Edge client is not required. Previously, a running instance of Edge Client was required for the network location to be detected. Network Location Awareness: The usability of the Network Location Awareness feature has been improved in an Always Connected configuration, Network connectivity is enabled only when the user is connected to the Enterprise LAN, either directly or through the VPN. This version of the Client Troubleshooting Utility prompts the user to escalate privileges and collects all the logs in a single run. Previously, to collect troubleshooting logs, the user had to run the utility twice, once as a user, and the second time as an administrator. Client Troubleshooting Utility logging: The Client Troubleshooting Utility can now collect all service and user logs in a single run.
0 kommentar(er)
