< Junos Pulse Release Notes >
© Juniper Networks, Inc.
7
Internet Explorer’s default security settings. The workaround is to add the IC or SA Series device IP address to
the trusted site list under Tools->Internet Options->Security->Trusted Sites. (581648)
•
Once Junos Pulse 2.0 is installed, it is not advisable to use the standalone Pulse 1.0 installer. This may result
in failures to uninstall any Junos Pulse 1.0 components. (575731)
•
When upgrading to Junos Pulse 2.0 using the MSI installer package, it may take several minutes to remove
the previous version of Junos Pulse and appear hung. This issue is caused by the Windows Installer doing
verbose logging. The issue is documented and discussed in Microsoft KB article
http://support.microsoft.com/kb/971133
. (559861)
•
If the RSA Soft Token application (RSA 4.1.0.458) is installed after the Junos Pulse 2.0 is installed, you must
reboot the system in order for Junos Pulse to detect the presence of the soft token application. (543379)
•
Canceling the Junos Pulse client installation is currently not supported. (492565)
•
Pulse deployed via dynamic deployment from an SA or IC Series device cannot be upgraded using the full
installer package. (513007)
•
Some users may experience extended install times for Juniper's network driver component. (494736)
•
Some versions of Windows XP contain a known issue that causes extended install times for Pulse. Please
refer to MS Incident KB949900 for a patch that should resolve the issue
(
http://support.microsoft.com/default.aspx/kb/949900
). (519639)
•
Pulse installation on Vista x64 may not pre-install Juniper Networks Virtual Adapter instances. The first time a
Pulse connection is established that requires a Juniper Networks Virtual Adapter instance the adapter will be
installed resulting in a slight delay during the first connection. (521929)
•
If the user receives the error message “error provisioning access method connection” when attempting to
establish a connection, it is possible that a third party USB device is interfering with the Juniper Networks
Virtual Adapter. (527406)
•
When attempting to establish connections, Pulse may prompt you multiple times to upgrade 'missing
components'. (529409)
•
Configuration changes to SA or IC Series devices that result in deploying new Firewall, 802.1x, or WX
connections may require end users to re-login to the device via the web browser. (523193)
•
The SA or IC administrator must associate a connection set with Pulse enabled user roles in order for Pulse to
be properly deployed to endpoints. Pulse will not be installed or upgraded if the Pulse role references an
empty connection set. (525667)
•
Pulse pre-configured installers can not re-bind the endpoint when it is already bound to a server. (524357)
•
If Junos Pulse and Kaspersky AntiVirus are installed and you attempt to uninstall Pulse, the popup message
"Error!Can't initialize plug-ins directory.please try again later.." may be displayed. If this occurs, try uninstalling
Pulse again. (528694)
Unified Access Control
•
Junos Pulse 1.0 should not be installed with the Odyssey Access Client 5.3. (545524)
•
After changing an IPSec Policy on an IC Series device to 'force VA', Pulse may not configure the IPSec Virtual
Adapter for the active user. (492887)
•
If you are using UAC IPSec Enforcement using Junos Pulse, applications might experience a slight delay in
being able to establish network connections. (491848)
•
When you configure Junos Pulse to make 802.1x based connections, a reboot may be required on Windows
XP the next time Junos Pulse is upgraded. (492843)
•
When you create a preconfigured installer, you download and run the pre-configuration utility on a Windows
machine. The operating system (32- or 64-bit) on which you generate a preconfigured installer determines the
machines on which the installed Pulse client will run. If you generate the preconfigured installer on a 64-bit
machine, the Pulse client installed by that installer will run only on 64-bit machines. If you generate the
preconfigured installer on a 32-bit machine, the Pulse client installed by that installer will run only on 32-bit
machines. (498503)
