HI Jamf Nation,
I am running into a weird issue in which installing Junos Pulse when installed manually is able to start and add connections just fine. However, when packaging the app in Composer using the normal snapshot method, and packaged as a DMG. Has anyone experienced this or know of a fix? I have attached screenshots below. Thanks!
I get the following error:
Failed to connect to the Pulse Secure service.
This is what it should look like, done with normal install
This is after packaging with composer as a DMG using the snapshot method, Pulse Secure is turned off.
This is the error I receive when trying to add a connection from the DMG that was packaged.
@rastogisagar The Mac compliance settings for Pulse Secure are completely independent of Jamf Pro, but will likely utilize the presence of the Jamf software on your Mac as a compliance item. Unfortunately I do not have any documentation I can share with you on the subject. You really need to work with your Pulse Secure team, and probably Pulse Secure's technical support, to get the compliance check appropriate for your environment configured.
@rastogisagar Other than saying you should complete the online Jamf 100 course before taking the Jamf 200 course I don't have any specific advice on pre-course prep resources. Having completed your Jump Start, and having some hands on time with Jamf Pro would definitely help. I thought there were course specific resource references listed on the course description pages on the Jamf site, but I don't see those now, but they may be provided after you register. Take notes during the course, testing is (or at least used to be) open book, and for the 200 testing will pretty much be specific to material covered in the class. The 300 and 400 courses require deeper Mac knowledge and/or good search foo for Jamf Nation posts and Rich Trouton's blog on the subject in question.
While I don't know all the details of the Cisco ISE integration, that is the "general" idea I tried to "sell" to Pulse Secure and was trying to get re-started again now. I don't think the server folks have to cede Mac compliance controls to Jamf... I just more controls than the Pulse offers, I am sort of sure that Pulse doesn't even do the checking I think it's a third party app that Pulse Secure runs inside Pulse. A true win would be the current Pulse checks plus Jamf Pro smart groups that way I can use EAs for even more checks.
Hi, The above scripts are not working with new Pulse Secure 9.0.3 and we really do not need to copy the config file when we use DUO authentication when you log in to the VPN. I'll appreciate if anybody has a new workflow building the package and post-install script for the new version. Also, we need the kext and Team ID.
The MDM protocol specifies a kernel extension policy:
To approve Pulse Secure kernel extension thru MDM and without user consent, please add the following keys to the MDM kernel extension policy described above:
Team Identifier = 3M2L5SNZL8
Bundle Identifier of kext = net.pulsesecure.PulseSecureFirewall Thanks in an advance!
We are still using
/Applications/Pulse Secure.app/Contents/Plugins/JamUI/jamCommand -importfile /temp location
And the same process as my 2016 post in this thread...
I just tested mins ago with yesterdays released Pulse 9.0r3.2-b1667 in our dev environment worked as it should...
Could you help me do this step by step to install pulse secure on mac devices from jamf . I really need help on this .
When i try to install manually on mac , it works without any issues and creates pulse secure folder in /Library/application support .
when uploading the same pkg to jamf, creating policy to make the pkg available in self service .
Trying to install the pkg its installing , but not working :(
There is only one log file inside Library/application support .
When opening pulse secure its throwing error as 'failed to connect to pulse secure service'
No promises but this is what we do...
Using a 3rd script before you launch Pulse run /Applications/Pulse Secure.app/Contents/Plugins/JamUI/jamCommand -importfile / "temp location of your components.jnprpreconfig"
Delete the components.jnprpreconfig file as it's plain text and has all your wifi info..
Old but still current I think..
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 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).