< Junos Pulse Release Notes >
© Juniper Networks, Inc.
9
patch remediation may succeed if the Kaspersky Antivirus software is turned off. (573973)
•
When using Patch Remediation, the patch installation count may exceed the missing patch count. This may
occur when the same patch is attempted to be installed twice. The result will be a failure during the second
attempt, which should be ignored. Two known patches that can exhibit this issue, WindowsXP-KB954459.exe
on Windows XP and msxml6-KB954459.exe. (561392)
•
During patch remediation after auto remediation complete, the user may be prompted to reboot the system. If
the user attempts to connect prior to rebooting, the connection may pass the compliance check. An example of
such a patch is the WindowsXP-KB953155.exe. (575714)
•
When a Shavlik policy is configured and a browser is used to login and launch Junos Pulse, high CPU
utilization may be observed. To avoid this issue, the user should login directly using Junos Pulse. (565692)
•
During patch installation, some anti-malware solutions may report a risk warning on stdeploy.exe. To avoid the
warning, add Hostcheckpluginhost.exe to the anti-malware exceptions list; otherwise user’s can safely ignore
the warning to continue. (573970)
•
When Enhanced Endpoint Security (EES) is enabled and the user installs Junos Pulse via a browser, the
upgrade prompt may be shown immediately after connecting to the Junos Secure Access Gateway. (574762)
•
When using Shavlik Remediation with proxy credentials, Junos Pulse may stay in the connecting state. To
workaround this issue, wait a few seconds before entering the proxy credentials (523146).
•
In the Junos Pulse 2.0, the Shavlik remediation dialog prompt may flash when transitioning from the certificate
to credentials dialog. (544665).
•
For testing Patch Remediation feature for restricted user account, the machine should be rebooted after Pulse
installation in admin account. If user switches to restricted user without rebooting then Patch Installation
Progress dialog does not appear. (560962)
SRX
•
Installing Junos Pulse 1.0 after installing JAM 1.0 is not supported.
•
When using SecurID to authenticate, Junos Pulse 2.0 does not request a new passcode when reconnecting.
(570033)
•
When using SecurID to authenticate, Junos Pulse 2.0 requests user to enter the password instead of token
information. (570037)
•
When using Dynamic-VPN with the SRX-240 configured to use xauth authentication through the radius server,
the IPSec tunnel may not get established when the virtual adapter is created.( 576246)
•
Save credentials in the Junos Pulse credential dialog is not working correctly for SRX connections. (490482)
•
For firewall connections, the "Forget saved settings" option may not clear all saved data. (492880)
802.1x
•
Junos Pulse doesn't show authentication failure when using 802.1x connections and an expired client
certificate is used. (487727)
•
When using Junos Pulse 802.1x connections on Windows XP with Odyssey Access Client installed, you will
have to check the check box, "use windows to configure my wireless network settings", manually after you
uncheck "use Odyssey to operate this adapter" in Odyssey Access Client. (504701)
•
Pre-configuration of 802.1x settings is required in order for the 802.1x feature to work correctly if users cannot
log-in to the IC via the web browser to dynamically deploy the configuration. (526341)
Application Acceleration
•
When Junos Pulse Application Acceleration is enabled while connected to a Local Area Network, network
access may slow down. (523789)
•
The Junos Pulse Application Acceleration component may cause disruptions with some types of network
connections on systems with multiple network interfaces that are connected simultaneously. (504692)
•
Deploying the Junos Pulse WAN Application Acceleration package via Host Checker is not supported when
