< Junos Pulse Release Notes >
© Juniper Networks, Inc.
8
•
Establishing a connection to an IC Series device via the Pulse client is not supported when there is an existing
active connection to the IC Series device with Odyssey Access Client. (509095)
•
NAP Host Checker Policies will not work with Pulse if Odyssey Access Client is installed and also evaluating
NAP Host Checker Policies. (512884)
•
Certain client firewalls may make the Pulse connection on the IC appear as if it is located behind a NAT device
when it is not. (519630)
•
If connected to a SA Series device and an IC Series device, then disconnect from the SA Series device, other
Pulse clients may receive the error "Too many connections from the same endpoint" error while attempting to
connect to the IC Series device. (528650)
•
When both Pulse and the Odyssey Access Client are installed on the same machine, it is advisable that only
one client be used when establishing connections to the same IC Series device. (526333)
•
While Pulse is connected to an IC Series device and the user initiates a connection to a Firewall, the IC Series
device connection may get disconnected. (524075)
•
When Pulse has connections to both an IC Series and SA Series Access and the user disconnects from the IC
Series device, the Active Users page may shows that the user session is still active. (523750).
Secure Access
•
When using a USB EVDO modem to connect to a SA Series device, Junos Pulse 2.0 may not provide network
access after connecting successfully. (583893)
•
Junos Pulse connections may toggle between connecting and connected when Kaspersky Internet Security is
active on the endpoint and Route Monitoring is enabled at the role-level. To workaround this issue, disable
Route Monitoring on the SA Series device. (562789)
•
To connect to a SA series device with Junos Pulse and Kaspersky anti-virus installed, split tunneling must be
enabled. (557069)
•
Multiple simultaneously connected SA Series device connections are not supported in Junos Pulse.
•
Changes made to Junos Pulse configuration on SA Series and IC Series devices are not showing up in the
Admin Access Logs. (475507)
•
It is currently not possible to provide Junos Pulse access for the delegated admin role on SA/IC Series
devices. (477822)
•
When running Junos Pulse within Secure Virtual Workspace, the Pulse user interface will not launch correctly
if it is also running on the base desktop. (483290)
•
When using the Firefox browser to deploy Pulse from a SA Series or IC Series device, please be sure that
"Enable the next generation Java Plugin" is enabled in the Java console. (498586)
•
Please be sure to install 32-bit version of Java runtime on 64-bit windows versions when deploying pulse via
the Firefox browser. (502486)
•
SAML OAAM authentication is not supported with the Pulse client. (505578)
•
XML Export of the Pulse Configuration from a SA Series or IC Series device is exporting connection type as
802.1x for WX connection in Junos Pulse connection sets. (513816)
•
Junos Pulse may not be able to connect correctly to an SA Series device configured for secondary
authentication when certificate authentication and local authentication are configured as primary/secondary
authentication servers. (489989)
•
When client proxy or server proxy is configured, if a user clicks on Sign out from the browser while Pulse NC is
connected or if the Pulse NC user is timed out, Pulse may go into an infinite reconnect loop. This is because
the proxy PAC file set by NC AM is not reverted in this situation, thus blocking Pulse from reconnecting. To
come out of this situation, the end user must click disconnect on the Pulse UI and try to connect again.
(521906)
Endpoint Security
•
Shavlik Remediation may fail on endpoints running Kaspersky Antivirus 6.0 for Windows workstations. The
