Just received the notification of the removal of the Junos Pulse Mobile Client from App stores at the end of Q2-2015 (TSB16705). This TSB includes links to documents with basic instructions on how to deploy the Pulse Secure version with AirWatch or MobileIron with Per App VPN but the release notes for the Pulse Secure Version lists the following as the first two open issues:
PRS-319284: Air Watch MDM VPN profiles are not getting pushed to the Pulse Secure client.
PRS-319282: Mobile Iron MDM VPN profiles are not getting pushed to the Pulse Secure client.
Firstly just over a months notice is not enough when you are looking at enterprise deployments.
Secondaly is a new version iOS with a fix due out that will support VPN on demand profiles? I seen the new Android version still has the issue.
What issues are we seeing with VOD? These should be working with the new Pulse Secure client.
Because the release notes state the is an issue with deploying profiles to the new client with AirWatch I did not want to waste the time of the AirWatch team until the issue was fixed. The workaround only references how to configure AirWatch to deploy a profile with Per App VPN. So the question is does a simialr workaournd exist for a VPN on Demand profile or could we adapt this workaournd?
I guess the other question is, what exactly is the issue refered to in the release notes and how does it manisfest itself?
We have a very lean IT organisation and don't have the resources to double checked every known issue. If the release notes say there is an issue we're going to take the vendors word for it and if possible wait for the fix.
The workaround remains the same for both Per-App and VPN On Demand.