How does this update affect Pulse Secure's ActiveX control?
Microsoft's update will only affect out-of-date Oracle Java ActiveX controls. Pulse Secure's ActiveX control is not affected by this update.
Will this update cause any issues for my end users?
By default, we will use Pulse Secure's
ActiveX control to deliver and launch all Pulse Secure
components except the following Java deployments:
- Java Secure Application Manager (JSAM)
- Premier HOB applet
- Applets through the rewrite engine
If Pulse Secure's
ActiveX control are successful, this update will not affect end users. If Pulse Secure's
ActiveX control fails to install or is disabled, Java is the fallback option and the update will affect end users with outdated Java ActiveX controls. To avoid or resolve this issue, end users should update to the latest Java version.
The blocked JRE versions are:
JRE < 1.4 Update 3
JRE < 1.5 Update 71
JRE < 1.6 Update 81
JRE < 1.7 Update 65
JRE < 1.8 Update 11
If it is necessary to use an older Java version, add the Pulse Connect Secure URL to the Trusted or Intranet Zone in the Internet Explorer settings. Microsoft confirmed that this change will only be applied to the Internet zone.
For more information, please see the Microsoft announcement at http://blogs.msdn.com/b/ie/archive/2014/08/06/internet-explorer-begins-blocking-out-of-date-activex-controls.aspx