Pulse Secure has qualified Windows 8.1 and IE 11. Pulse Connect Secure release PSC OS 7.4R7, Pulse Policy Secure release 4.4R7, and Pulse Secure Desktop Client
release 4.0R7 and later support Windows 8.1 and IE 11.
The supported platforms document has been updated to reflect the supported components.
Q: Will IE 11 be supported on Windows 7 as well?
A: Yes, IE 11 will be supported on Windows 7. The supported platforms document has been updated to reflect the supported components.
Q: What Server (PCS and PPS) and Client versions (Pulse Secure Desktop Client) will be supported?
A: If deploying Windows 8.1 or IE 11, we recommend that customers upgrade to Pulse Connect Secure (PCS Series) release 7.4R7, Pulse Policy Secure release 4.4R7, and Pulse Secure Desktop Client release 4.0R7 (or later).
- [Pulse Secure Desktop Client
] Windows 8.1 on Microsoft Surface Pro/Pro2 tablet issues after installing Pulse
Some of the key issues found during the Windows 8.1 qualification process are listed below. These issues are fixed in the above mentioned release versions. Note that most of the issues are related to IE 11 rather than to Windows 8.1.
Host Checker: When using IE 11 to sign-in, host checker client components will log the error message "Host Checker is not supported. Please contact your Administrator." The workaround is to use another supported browser. (907853)
Active-X based client delivery, client install, and client initialization for all client components will fail. The workaround is to use Java-based client delivery and client install. Java fallback is automatically enabled and no additional configuration is required for this workaround. (905511)
For Windows Secure Application Manager (WSAM), Windows Terminal Services (WTS), and Citrix Terminal Services (CTS) client components: When using IE 11, these clients will log the error message
Your browser is not supported for this component. (907855, 921246)
For Java Applet Rewriting and Premier Java Remote Desktop Protocol (RDP) applet: When using IE 11, the Java applets used by these access mechanisms will not launch. (916815, 914012)
The Auto Launch feature for client components may not work when using IE 11. The workaround calls for the user to manually launch the client component after signing-in. (916984)
IE 11 will not use the Proxy Auto Configuration file set by Network Connect (NC) or Pulse Secure Desktop Client. (949997, KB28589)
This article does not apply to the Windows 8.1 RT edition. For details about the Pulse Secure In-Box application supported on Windows 8.1 RT, see the Windows In-Box Pulse Secure client Guide.
Note: To submit feedback on this article, fill out the ‘Article Feedback’ form in the right column. If you do not see the ‘Article Feedback’ form, then log in with your user account, and the form will be displayed. If you do not have a user account, you may also submit feedback here.