Pulse client doesn't prompt to upgrade after IVE update

[SF_Dan_]

I am running a cluster of SA6500 appliances. I upgraded from 7.2R4 to 8.0R4.1 and had lots of issues with the Pulse clients. I do have "Enable web installation and automatic upgrade of Junos Pulse Clients" under System -> Options but 90% of my users were never prompted to upgrade their client. Is this normal behavior? The only thing I can think of is that I deployed most of those clients using SCCM so if you deploy using a tool like SCCM does the pulse client ignore the auto upgrade option on the IVE? If that is the case is there a flag you can set in the install to allow the auto upgrade from the appliance?

[flip_pipe_]

Hi,

I think the answer for you it is in the KB28892.

quote:

"However, for Junos Pulse 5.0r3 upgrade, one should use the same method of deployment as used during prior installation."

[Kita_]

Upgrade prompt is determined if the Pulse version existing on the client's machine is older than the active version on the SA device.  What is the active version of Pulse on the SA device and what version do the clients have installed?

[SF_Dan_]

Pulse on the SA is 5.0.4.47117 Clients previously had 3.0.

[Kita_]

I ran a few tests in the lab and could always see the prompt to upgrade when the "Enable web installation and automatic upgrade of Junos Pulse Clients" is enabled.

I would need to review the Pulse logs to see if the client is even checking the version.  My assumption is Yes, but the SA is not pushing the update.  Could you please open a case and provide the Pulse logs from a problematic user?

[SF_Dan_]

How did you test the upgrade? I tested numerous times on my lab appliance and if I install the 3.0 pulse client using the web install it then upgrades to 5.0 fine, it is when I install the client with SCCM that it will not upgrade.

[zanyterp_]

I believe that is correct for 3.0 and it cannot be changed until you uninstall and re-install a newer client version. I will have to try and test to confirm my suspicion; but as kita indicated, we are guessing right now. I seem to recall some upgrade failures with 3.0 if it was installed via SCCM that it would not accept the prompt to download the install (but I can't find anything right now).

Do you have a test machine you can install 5.0R3.1 via SCCM and then connect to see if the upgrade prompt comes for 5.0R4.1?

[SF_Dan_]

yes, I have a lab SA2500 I can test with. I see that 5.0R5 just came out so I am going to try and test going from 5.0R4.1 to 5.0R5. I will install the 5.0R4.1 client with SCCM and see if the web upgrade works

[Kita_]

I did the initial testing by manually running the MSI (similiar to the SCCM deployment), then connecting to the SA via the web.  I did see the upgrade process under this scenario upgrading to 5.0 with 4.0 and 3.0.

We'll need to dig into the logs to get a better idea why this is not occurring in your environment