@gachowski thanks a lot for your reply !

Much helpful :)

we do what @gachowski describes

@gachowski Do you have a link to 9.1?

@Winterpil

Sorry, you need an Pulse Secure account and then that account has to be linked to "your products" in their downloads section. Short version you still need to work with your network team.

: )

C

gachowski, the workflow you provide does not work if you have multiple connections with DUO authentication.

We need to create a separate package Pulse Secure settings /connections/ and push first the settings and second package with the Pulse Secure.pkg file on the same Policy. That works with 9.0.3 version but not with 9.1.2 (901) unless you do not go as an update with Self Service. Do not forget the Team ID and kext. configuration profile Now we are looking for 9.1.2 solutions.

@nikjamf f]

Sorry, I'm lost ... We have locations all over the globe and they all require Duo. We only have one components.jnprpreconfig. and that list all the endpoints that user can remote to. USA west coast, USA East Coast UK, India.................

C

Same as above ^^^
One file, I build a pkg to drop the config file into /tmp (or other place) and then the installer runs.
Postinstall .sh to import the config file and boom, yer done.

@nikjamf could you elaborate on this?

gachowski, the workflow you provide does not work if you have multiple connections with DUO authentication. We need to create a separate package Pulse Secure settings /connections/ and push first the settings and second package with the Pulse Secure.pkg file on the same Policy. That works with 9.0.3 version but not with 9.1.2 (901) unless you do not go as an update with Self Service. Do not forget the Team ID and kext. configuration profile Now we are looking for 9.1.2 solutions.

I am having some trouble with 9.1.2 where the config isnt working (we use multiple connections).

Still the best guide. https://derflounder.wordpress.com/2015/03/13/deploying-a-pre-configured-junos-pulse-vpn-client-on-os-x/