usr/bin/osascript -e 'tell application 'Junos Pulse' to quit' Applications/Junos Pulse.app/Contents/Plugins/JamUI/jamCommand -importFile Company_VPN_Servers.jnprpreconfig usr/bin/osascript -e 'tell application 'System Events' to set visible of application process 'Junos Pulse' to false' usr/bin/open -background -a '/Applications/Junos Pulse.app/Contents/MacOS/Junos Pulse' # Open Junos Pulse in the background and then hide the app usr/bin/open -a '/Applications/Junos Pulse.app/Contents/Plugins/JamUI/PulseTray.app/Contents/MacOS/PulseTray' bin/chmod +x /Applications/Junos Pulse.app/Contents/Plugins/JamUI/jamCommand bin/chmod +x /Applications/Junos Pulse.app/Contents/MacOS/Junos Pulse bin/chmod +x /Applications/Junos Pulse.app/Contents/Plugins/JamUI/PulseTray.app/Contents/MacOS/PulseTray usr/sbin/installer -pkg JunosPulse.mpkg -target / I can post the script if you'd like but I'd also advise to upgrade to the v4 client as none of this is necessary with it. For some reason that would get the settings to stick as well as allow for subsequent connections to the Junos Pulse endpoint. We found that the application would not work properly until it was launched a second time and quit.

If it sounds convoluted that's because it is. opened and hid the Junos Pulse app via /usr/bin/open and some applescript opened the Junos Pulse Tray (menu icon) via /usr/bin/open called /usr/sbin/installer to install the junos.pkg Call the installer script with the 'run command' setting in Advanced.Īs for the installer script, it did this: Create a package with the stock junos.pkg, an installer script, and the junos pre-config file. Eventually, we were able to put together an installer script for the v3.x client. We struggled with the same thing at my company.

Junos pulse mac