08-03-2012 07:53 AM
I have this same exact problem.
In looking at the logs it seems that the Junos Pulse Client does not have the proper Entitlement priviledges that are required in Mountain Lion...
08-03-2012 08:07 AM - edited 08-03-2012 08:08 AM
Interesting. I'm curious if the certificate that is used to sign the applets is related to the ports that you are presenting your signed SSL certs on. I'm assuming that you are using a real (public) SSL cert on the site that users connect to. Here's what I'm getting at. Are you still presenting the default, self-signed certificate that the SA creates during setup on your outside interface? Under the 6.x IVE, it would create a "secure.companyname.com" self-signed cert.
08-07-2012 02:44 PM
We have host checker disabled, but on two systems we are experiencing the issue. On two other systems we are not having the issue. All systems involved were upgraded from Lion. Nothing we can find distinguishes the affected systems.
08-08-2012 03:20 AM
We are also facing the same Pulse uninstall issue on our current OSX Mountain Lion ... Digital Marketing people in our company is using only Apple solutions and OSX Mountain Lion has been deployed on their platform ... they are not anymore able to gain VPN SSL access in our telecom infrastructure ... is there any news from Juniper to solve this major issue ? We have open in parrallel a case with Juniper ... let's see ...
08-08-2012 05:17 AM
With the Junos install package still needing an adjustment to prevent it from uninstalling on Mountain Lion after a reboot, we have found a way to fix it locally.
The uninstall is caused by a script being executed at startup. It is located in /Library/LaunchDaemons. It is called "net.juniper.UninstallPulse.plist"
Just delete it and the problem is gone.
Would be good if Juniper can confirm this is a proper workaround, while we are all waiting for a new release....
08-15-2012 05:15 PM
We are working on getting an update out by the end of the month, possibly next week if all goes well. As a Mac user myself, I'm right there with the rest of you and not really satisfied having to go back to Network Connect.
Kevin Peterson, CISSP
Sr. Product Manager
08-16-2012 12:55 PM
Upgraded our SA2500 to 7.2 R2 from 7.1 and can't get past host checker on my 10.8 Mac.
I'm seeing this in syslog:
<Notice>: killed JuniperSetupClientInstaller.osx[pid 11055] because its use of the version entitlement is not allowed
I guess there are still no workarounds other than disabling host checker?
Can the IVE safely be rolled back to the latest 7.1 code?
When is a fix planned please?
09-13-2012 08:14 AM
I don't see 7.2R4 on the downloads of Junipers website just 7.2R3
Did you get that version from tech support? I need to do an upgrade this weekend for security however I don't want to do another next week just to add Mountain Lion support.
Juniper Networks Certified
Internet Associate - FWV
09-20-2012 12:53 PM - edited 09-20-2012 01:07 PM
I have 7.2R4 installed in my lab. I successfully tested host checker and the premier java RDP client on a Mac running OS X 10.7.4, Safari 5.7 and Java 1.6.0.
When I attempt to connect with a Mac running OS X 10.8.2, Safari 6.0.1 and Java 1.6.0, I am able to install Host Checker, but I am unable to load the Premier Java RDP client. The error is as follows:
"The digital signature is not trusted. Java will not allow any access to this applet."
I'm glad that Host Checker is working though.
10-02-2012 08:37 AM - edited 10-02-2012 08:53 AM
Sorry; fat-fingered the navigation menu and posted without getting anything typed.
Have you uninstalled the existing setup client from the system that was in place prior to the upgrade to Mountain Lion?
sudo rm -rf ~/Library/Application\ Support/Juniper\ Networks/SetupClient
Reboot after this is complete.
10-02-2012 08:54 AM
sorry about that; hit submit before anything was typed.
I have corrected that error and am replying here as well: does the problem exist even after removing the existing setup client from before the upgrade to Mountain Lion (
sudo rm -rf ~/Library/Application\ Support/Juniper\ Networks/SetupClient; reboot)?