Posted on 01-12-2016 12:37 PM
In supervised mode, blocking new profiles from being installed is not working. The VPNs are now setting up under VPN instead of profiles as they formally were. What else can we do. THis is a huge problem and one of the main reason of purchasing the JAMF software. THere has to be a way!
Posted on 01-13-2016 07:30 AM
What did Jamf support say when you contacted them about the issue?
Posted on 01-14-2016 08:18 AM
Yea, I've seen a few threads regarding this type of question with few answers. I would certainly contact JAMF Support. However, I did find a posting at the bottom of this thread
https://jamfnation.jamfsoftware.com/discussion.html?id=13021
which seemed to suggest a possible solution. Unfortunately, I have 0 'real' experience blocking profiles form being loaded onto iPads, in a large scale production.
Anyways, since I'm kind of doing this by posting the thread, I suppose I should call pout @Sandy who posted the possible solution.
Posted on 01-19-2016 01:55 PM
@warrenisd15 and @ooshnoo We also discovered that once this restriction is applied prevent users from "trusting" third party dev like vShare and provisioning profiles
We can temporarily set the Date forward (1 year works well for most) , which then either automatically deletes or allows us to delete all of the now "expired" provisioning profiles.
Sset date back and no new provisioning profiles or third party apps can be downloaded.
This was the easiest way we've found so far to clean this up, as Xcode did not always allow us to remove them.